Leaderboard

Six months has passed. Development of stevenlauBot did not stop, but I have been dealing with a really difficult problem - optimal field placement around CC. The algorithm improved over and over, and now reaches an optimal solution worth sharing. Before I go into technical details, here are some screenshots of optimal placements in random Mainland. Pink represents the region where we can place field freely, and blues are the fields. Now I am writing some technical details. I first define Gap and Hang. Gap Ideally we want to let a field to touch (snap) the CC (or actually any dropsite), so that farmers can efficiently drop resources without walking. However, since farmers have a size and dropping range, we can actually leave a gap (around 5.6m) between field and CC and the farmer can still drop resources without walking. Leaving such a gap might allow more fields to be placed. Hang In games, we often see players put field snapping at the corner of CC. This is not ideal, because farmers will have a walk a bit to drop resources. We name this case "hanging" entirely outside of CC. If we now shift that field a little inward toward the CC, it is still hanging, but only part of it is hanging. Then farmers can farm in the part where the field is not hanging, and they can drop resources without walking. That non-hanging part is around 8m. Now to state our problem more precisely, we want to place maximum number of fields around CC, allowing gap between CC, but keep certain non-hanging part. We disallow rotation. Although rotation might give better arrangement, the problem will become too difficult. In fact, disallowing rotation is the sole assumption of our algorithm. Under such assumption, our algorithm gives optimal placement. I also claim that if we allow rotation, no efficient algorithm exists. People who are familiar with algorithm, especially computational geometry, should realise this is a very difficult problem. This is shape arrangement in continuous 2D space, and deterministic algorithm might not even exist. Scientists usually do heuristics to find good-enough (but not optimal) solution in these problems. I had also been working on heuristics, but as I keep improving my heuristics, I found that our problem is quite special and is much simplified. It turned out that we can work out a combinatorial algorithm to really find the optimal placement. We basically do trapezoidal decomposition of the region, that we do sweep line algorithm over all such trapeziums, exhaust all combinations, and merge linearly related constraints. The algorithm is super complicated, but I think I made it. Do you like it?

So I am trying to make certain structures "invisible" to bot players. My idea is to change the code in the file that checks for the nearest structure, and make it so it only sets that as attack point if the structure is not a certain class. I don't know if that would be easy, I think it would be somewhat easy. If someone could point me to where the file is and where in the file that would be, that would be helpful. I may also need help with the coding, if anybody would want to help. Thanks!

Good morning, I tried hosting a game on Migration with relics, however relics keep spawning on the player's island, thus giving a certain advantage for certain players and negating the incentives to go and fight on the main island. Is there a way to restrict the spawn area of relics so they all spawn on the main island ? ps : i might be on the wrong forum section, should i repost in map making subforums ?

It can be implemented progressively, starting with a non-editable version generated by a script.

Thanks for feedback Guerringurrien, I too noticied sometimes loading stops at 6% especially when 11+ users are in game but rarely. Need to check with group placements and other maps.

played multiple 5v5, one 6v6 with others here, and I can say its pretty darn smooth than expected! quite good compared to what everyone would assume it to be... and @kheeva I had the mod installed and I also could not join his 1v1.. it seems to be problem of him.. I am currently in the game you are playing haha even though its without the mod

@Asura, thanks for the mod! We played several matches yesterday, and it ran with no noticeable performance differences. We did notice that River and Random Group Placement weren't working properly. River crash on loading, and Random Group Placement got stuck at 6% loading.

@Asura, if you add this line "ignoreInCompatibilityChecks": true, to your mod.json, then not everybody will have to have the mod, only the host. I'm not sure how it will work for this mod, but maybe try it

This is just a simple mod that allows you to set up to 8 teams. I got the idea from Version 1.1 doesn't require everyone to have the mod, only the host more_teams1.1.pyromodmore_teams1.1.zip moreteams.zipmoreteams.pyromod

You mean the overlap of fields you see in game? They actually are not overlapping. The "core" part of a field is smaller, and I'm computing based on that core part only. In game, they render a bit more field outside of that core part. That part cannot be farmed, and is for aesthetic effect only.

Classic-Burger is absolutely right, the core capture system needs a major overhaul before we even think about adding complex mechanics like faction unit recruitment. Right now, without a proper cooldown or assimilation process, introducing cross-faction recruitment would just lead to insane snowballing or broken 'cheese' strategies in high-level matches. I love the tactical depth it could bring to protecting key tech structures, but the balance nightmare of mixing faction bonuses and counters might be too much for the current meta to handle.

So, isn't the advantage of cavalry their high health? They cost extra due to their superior speed, but they also have a massive amount of extra health.

I guess you didn't understand what I said in the first place, which was: no unit should be so OP as to have some gentlemen's agreement not to produce it, and when there's a misunderstanding regarding that, to have people whining about it, as it happened recently. So, if you say "champ cav is nonsensically fast", "naked fana has capture speed of a champ despite not having any of the drawbacks of a regular champ", and what you now added, I'd assume you agree with those complaining that they are OP, so I was agreeing that they should be nerfed, at least to the point of no ban needed to even be considered.

Hey, @Itms I just submitted my mod to mod.io and was wondering if you could approve it. The mod adds a unique Māori civ to the game. Thanks, Zach

@Seleucids If you stick to raiding the formerly Roman parts we should have no problem. Here's one I thought you might like:

The capture system needs to be improved first, as it hasn't received many changes since A16. There should be a cooldown and an assimilation process. The Dacians learned a little about making siege machinery from the Romans.