Jump to content

Seleucids

Community Members
  • Posts

    551
  • Joined

  • Last visited

  • Days Won

    19

Everything posted by Seleucids

  1. The jump between sandbox and very easy is too big, imo. This is especially the case with my newly merged pull request where I buffed the eco and military performance of the bot
  2. I think there is something we need to change here: make "very easy" AI much much easier. It took me several tries to beat this very easy AI when I was starting. This can be achieved by: 1. Nerfing infantry rushes, reduce size of attack even further 2. Huge anti-bonus to the AI's eco and attack strength.
  3. Done for you https://gitea.wildfiregames.com/0ad/0ad/pulls/7929
  4. @nani could you explain what is the purpose of options~autociv.js and similar files with ~ in the middle? Why can't we just replace the options.js directly? Furthermore, why do we need patchApplyN!!! ? Some of these files are causing funny bugs such as not allowing the user to leave a page.
  5. Minor change: I aligned the spectator names to the right side of the panel and truncated the maximum length of names to 20 characters. This prevents players with extra-long names (especially customrating users) to take up too much of your screen. I have also started an A28 branch on the git repo; this branch aims to be compatible with the A28 game under development. There are some changes to engine code and general layout of code, which would cause incompatibility with the A27 version. This A28 branch contains most of the A27 features already and can be used when you are doing test plays on A28 dev version.
  6. An update: I've added colour to the hero icon, so now you know whose hero it is. Furthermore, I enlarged the minimap and added icons for cavalry units as well. antiherorush.zip Suggestions about icon schemes, colours and sizes are welcome. Right now I have not many ideas so I just take icons from chess
  7. Bug fix and adjustments: Statistics counter used to crash when you switch the perspective to Gaia, because the original rating symbolism code couldn't handle gaia's null value. My solution was to give Gaia a rating of 1200 and that prevented the crash. Player overlay was overcrowded with incidences of long names being split between lines or 2 short player names on one line. Now, I implemented an AoE style overlay without the shadows, restricting to 1 line per player. I also separated out the sections of Spectators and Missing Players Deleted some unused functions and variables to decrease performance impact. Return of Max and Min colour highlighting A new release has been built for the aforementioned changes; we are now on 27.0.5 The build environment was changed to Ubuntu 22.04 because GitHub removed Ubuntu 20.04 on 15th April 2025. This shouldn't affect any users, especially if you clone the code from source.
  8. Good point, but actually it's fine, just put the mod stack in this order: ModernGUI will overwrite autociv and still give the lobby button: ModernGUI lobby as usual when you log in:
  9. New feature: added an options button to the lobby that launches the settings page in an async subroutine In the base game, there is no way to change your settings once you are logged into the lobby! This provides you with the possibility of adjusting settings to optimum before game starts. If you have reached the gamesetup page, you can press Alt + L to launch the lobby page then press on Options.
  10. commands.txt This one is the crashed game In this second game, the game window freezes from time to time, turning white. The longer I play, the more often this kind of freeze happens. If the freeze lasts for too long, the OS will think the app has crashed, but 0ad doesn't print out any lag messages. This is not systematically reproducible, it just happens at random times. It happens all the time if I play continously for more than 2 hours, but disappears after I reboot pc commands.txt I don't think gitea topic is necessary at this point. Could be a hardware issue or some libraries in the system being too recent.
  11. ERROR: Cannot serialize NaN values. ERROR: Script component Timer of entity 1 failed to serialize: Serialize_InvalidScriptValue Serializing: ({id:118788, time:1016000, timers:{}, turnLength:200}) terminate called after throwing an instance of 'PSERROR_Serialize_InvalidScriptValue' what(): Serialize_InvalidScriptValue Aborted (core dumped) mainlog.htmlinterestinglog.html The game crashed when I was spectating a weird game. To reproduce: 1. Spectate a game with wonders (10 second win time), using A27.1 2. Select a group of champion cavs 3. Keep selected when the wonder is built. Then game crashes with this.
  12. I don't see why you are against citizen soldiers. It is the best advantage of 0ad over other RTS. CS means all of your units can be used for work all the time. That gives you flexibility between eco and fighting. On the other hand, in other RTS, when you have a small amount of soldiers, they have to fight or they are idle. But you don't want to take fights because you will likely get outnumbered or suicide, in early game. Therefore you waste res and time on Idle units whereas 0ad players are more efficient with eco. You can boom fast in 0ad mad get involved in action earlier. Furthermore, you can choose to rush with Cs if you wish If you don't like CS concept you should play Delenda Est mod
  13. Geriatrix claims that @Feldfeld left 0ad because of me. He has been re-iterating this statement for the past few months but without explaining the reasoning. He brought it up today and I am getting concerned. My question is: FeldFeld, am I the reason why you quit 0ad (if you have quit 0ad at all) ? If so, why? I only remember playing with FeldFeld once where he was on his main account. Being of the highest rated players, we don't want to loose you and if there is something that I can do to bring you back, please suggest! If anyone else knows something, feel free to comment below. Thanks.
  14. New update: Additional camera settings: These are configurable options that are normally hidden from the settings interface, presumably because it might confuse new players. However, I personally found these camera settings to be essential for players improve their micro. In short: Scroll speed changes how fast your camera pans around the map when you press WASD. The value is the speed of the camera in m/s and the default was 120. I personally use 620 so that I can quickly move myself around my base. I allow up to 1000 but that's a bit too crazy for me. The zoom options control your altitude from the map. Default minimum is 50, but if you have a high resolution screen, you can still see content clearly for up to 10 or even 8. FOV = Field of view
  15. In theory, Kushites are one of the most OP civs: Early game: Free healer for exploration and healing your cavs / archers after rushing Booming and eco: The size of storehouse is very small, so that they can be squeezed into clearings inside forests for ultra efficient woodlines. The pyramid might help as well but it's a bit expensive. However, archers walk slowly and have low angular frequency, which does slow down resource gathering. In phase 2 you can make mercenary skirmisher inf, which is useful. Booming with cav is also an option. Early pushing: you will rely on archers and a mix of melee infantry. They are a bit weak unless you have significant numbers of cav and skirmisher infantry (40+ jav units in total). However, the pikeman wall + archer sniping is op if you can micro well. You can also do Blemmye merc raiders. Late game: elephants + pikes at the front. Champion archers + jav cav at the back. Sniping with champion archers is OP. If you are dishonourable, you can spam champion cavs with Nastasen hero. The only imperfection is that champion swordsman can only be trained from temples - you can't spam them. However, in practice: Every time I play Kushites, something goes wrong. Either I get rushed hard or my teammates fail or somebody disconnects. I've had very few successful games with them, but when they are not cursed, they outshine every other civ: https://youtu.be/FpMxIPT42Qw
  16. A demo video of Petra_Extreme against Petra on Mainland. This time it didn't make 130 women. I think yesterday's incident was caused by Coastal Ranges map or some other weird settings.
  17. Hi, I downloaded version 7 of your bot and test played it against Petra on very hard random settings. A few observations: The bot makes all women in the early stage, up to a third of its population. This gave the bot very good eco compared to Petra but very weak against rushes. The bot still makes the same mistakes of using women to mine and infantry to farm. The bot loves cavalry and its eco is mainly cavalry focused. The bot wins against Petra but with a very low KD. Dropsites are not placed close enough to the resources. Point one can be improved by changing the target number of females. Normally, in a 200 pop game, 55-60 women is the sweet spot. Even in 300 pop games, assuming you use all women to farm, no more than 65 women is necessary from my experience. Point 4 is a result of point 1: the bot always fights outnumbered battles. Point 5 can be improved by decreasing the maximum acceptable distance between res and dropsite.
  18. When I was spectating a game, I got an error message It was nothing fatal, the game could continue as usual. But maybe it's something worth attention.
  19. If you don't think this is broken... For most civs, there is 0 counter to this madness. At the very least, remove these extra bonuses for Seleucids etc to make other civs playable
  20. I'm so tired of carrying noobs...

  21. This varies from map to map, but generally the civs which have strong early game are the most dangerous. Since the AI also does 0 micro, the unit dps is the dominating factor here, which means we are looking at a civ which can combine jav + swords. This makes Romans the top of the list. Spartans and Gauls are also strong. Normally the AI shouldn't be allowed to reach late game, but if it does, the civ with the best champions win. Elephant civs are probably the best? Then Macedonians and Iberians have the best champion lineup.
  22. Profanity issues aside, one important rule to not ruin your game: No more than 10 champ cav units per person
  23. Steak before 0ad, not during, otherwise you make a mess on the keyboard I find that drinking Actimel while playing improves my performance. Kefir also helps
  24. I understand the difficulty. Perhaps it would be a good idea to separate these civs out into 1 civ per mod. This makes debugging easier. Currently, there are 30 civs sharing files and folders with each other. Some errors are intertwined and one mistake in a file caused chain reactions the screwed up the whole thing. If we separate the civs, it would be easier to isolate bugs and imperfections, e.g. missing buildings / units. @Hulla can give us some expertise on Dacian units.
×
×
  • Create New...