Seleucids

Hey hey hey All I'm trying to do is to make it harder to hack autociv. @wowgetoffyourcellphone if you have a better idea to defend the code than covering up the code, please suggest. As of now I am just brainstorming ideas and obfuscation is the first idea that came to my mind.

I don't test stuff when I'm playing. I test it when I am spec. I don't have enough apm to type code and play simultaneously

It can be ruled out for all cases because it's not the host that's relaying messages. I would like to test some features for mods or even future patches in practical conditions, i.e. a 4v4 game. If mod signing prevents me from testing and editing the patch on the fly then that would be annoying. I like the most recent versions of your Oddity detector. It flags out afk players and automation users in a non-offensive way

I don't understand, what is in violation of the license? At no point did the license mention restrictions on the names of variables and quality of code By introducing waffles and misleading variable names, I'm not denying the user access to anything. I'm just presenting a more messy version of the the product. With enough patience, the user can still understand which variable is which. The source code is freely available as always.

Unfortunately singleplayer is free cheat. Cheat codes are enabled by default, when you are under attack by the AI, all you need to do is gift from the gods + open developer overlay and win Possibly people are just curious / giddy with this new discovery earlier today. But by later this evening, in the TGs hosted by Chocapoca and Akentas, nobody even bothered to build a market and the thing was forgotten My plan would be to introduce some counter-intuitive names for variables and waffle a lot of irrelevant nonsense in the source code of Autociv to make it harder to pinpoint the important lines.

After a large increase in cheat accusations between players and Geriatrix's monologue of claims, I think it's necessary for me to debunk the possibility of cheating in A27. I will reference the source code in every one of my statements so that you can peer review what I write and make further studies. 1. Seeing enemy chat and spec chat. This is not possible anymore because all chat messages are sent to only the intended recipients by an engine function. The Engine.SendNetworkChat() function is defined at Line 237 of https://gitea.wildfiregames.com/0ad/0ad/src/branch/main/source/network/scripting/JSInterface_Network.cpp If you attempt to edit this file, the most you can do is send all of your messages to everyone, but those who use the official release will still be sending messages to the right targets, then you just make a fool of yourself. In A26 and earlier versions, the messages are sent to all players, then the GUI (defined in public mod) selectively displays these messages on the screen. Therefore someone can make a mod which removes the selection process to reveal all chat messages. 2. Revealing the map If you attempt to reveal the map by injecting commands into the console or using some kind of mod, you will get a message saying "Changing the perspective with cheats disabled is prohibited" . See lines 92-95 of https://gitea.wildfiregames.com/0ad/0ad/src/branch/main/source/ps/scripting/JSInterface_Game.cpp Therefore the reveal map cheat is gone from a mod level. Theoretically, one could edit the engine code to allow this function to be called, then recompile into a different version without causing OOS. However, this is beyond the level of most players. Furthermore, even if you call this function successfully, you will be put into a different player identity and you will not be able to control your own units and buildings. The advantage of the temporary vision is diminished by the need for extra apm and being afk for a bit. Oddity detector will likely pick you up and you might also have an OOS. 3. Seeing enemy stats This may be possible by changing some code in public/gui/ to display information about your enemy in the summary screen but I am not sure about this. One could theoretically edit the Javascript code of a mod with stat panels e.g. autociv, BoonGUI, ModernGUI to reveal enemy stats. However, actually doing it is non-trivial (not a 1-liner change) and most players don't even know where to start. @Atrik could we solidify our mod code to make hacks less easy? 4. Excessive automation It has been demonstrated by ProGUI and Quickstart that automation of commands is possible. Therefore it is theoretically possible to make a mod which does all of the micro tasks for you, or completely take over your eco. The core technology is the function Engine.SendNetworkCommand() which issues a command. This function is normally called after interpreting an user input, but one can also spam call it in GUI code. This is where @ffm2's oddity detector comes in handy: if somebody sends too many commands in a short time, they are automating things. You can also inject commands in via RL interface. However, what's the point ? You play 0ad because you enjoy playing the game and the action. If you automate everything that much, you might as well just stay spec behind some pro player who is actually playing and imagine that you are him. 5. Market exploit - yes this is still going on and we might ban this building / ask spectators to monitor abuse. 6. Biased spectators - some players have a pro friend who is watching and giving advice to them in global chat or voice chat on another platform. Some might make a smurf account which joins as spec to see the game. But this is much of a social issue not a technical issue.

Under certain conditions, the market can be pumped exploited with OP trades that will generate infinite resources. Below is one example of the exploit: One needs to firstly invest 3000 metal to buy some other resources, e.g. food, to really depreciate the metal value and raise the food value. Then you take 500 food to trade back more than 3000 metal - you end with a net profit in metal. Furthermore, the food is still highly valued and you can buy huge quantities of other resources with food, resulting in resources being generated from nowhere. However, this is not consistently working. I tried to reproduce this but did not get these profitable values like Cube did. After many trades, I was eventually able to generate 10K metal after spending 2000 food and 2500 wood (profit?) Ideally we make changes to the bartering mechanism to prevent this from happening.

How do you account for RD increasing over time? do you factor in the replay date?

Firstly, you installed the outdated A26 version. This is because Debian always gives you outdated packages. You should download the latest release A27.0 from another source. However, A27.0 also stutters a bit, in which case, you can help by testing the RC version A27.1 at http://releases.wildfiregames.com/rc/ The build instructions is here https://gitea.wildfiregames.com/0ad/0ad/wiki/BuildInstructions

CS jav cav was op in A25. But now they are not as OP because of the acceleration mechanic and the buffed spear cav hard countering them. And speed is exactly why we make cavalry in the first place This is a good idea in my opinion

It was an old joke shared in our Discord server, where we have a pie-chart-slander channel https://discord.gg/kwRvm9kd

I look like Lichtenstein or Luxembourg

The content of Public must be balanced, fair and stable for multiplayer games, both 1v1 and team games situations. The MP lobby is the biggest stakeholder of balancing, as they are the most sensible to and dependent on fair balancing. Any small perturbation can ruin an alpha's gameplay. On the other hand, single players can just rig the game settings to whatever they like . If they want some change, just make a mod. It's impossible to distribute a mod to everyone in the lobby. Even community mod and historical mod are still not popularised despite the advertising efforts. It's safe to say that most players will be stuck to whatever the alpha has by default.

No. This is exactly what makes 0ad different and we would like to keep it that way. Many of your ideas are trivial to achieve with mods which you can make yourself in 10 minutes.

Why? it is very useful because it allows players to focus on micro instead of checking training at home If we return to the times before autotrain, people will spend way too much attention in building eco and not as much rushing/early engagements. Furthermore, many semi decent players will suddenly become total noobs. Autotrain makes the learning curve of the game less steep so that out player base can grow. In any case, you just don't use the feature yourself

Looks amazing! What would be the purpose of this building? Some ideas: Train gladiator champions (which exist as templates but are hidden from the main game) Garrison units to rank them up very quickly

@Jan it's easy to make a mod which changes the food icon. This way you can have it any way you like, immediately, without having to debate or wait till next release. Try it yourself

Why nerf the speed of cavs? The whole point of cavs is being fast. If cavs are slow then just use infantry instead. We do need strong units but at reasonable quuantities.

Don't you worry, there is so much lag in networked games (especially more than 2 players) that dancing is non-existent. Sadly they do need this speed to counter fire cav and archer. All in all, I think champions occupying 3 population each is probably agreeable. If you want to make 30 champion cavs then you bascially have no pop space for anything else. If there is objection to moving them to fort, maybe we can consider other special buildings. I picked fort because that was the champion building in the past and was expensive enough to counter rich players spamming it.

As soon as you nerf the champ cavs, the champ infs will become OP. It's only a matter of time. Naked fanatics are already en route to becoming the next broken unit but it's just that Gaul players have not spammed it enough for people to notice yet. ok this is good idea These are the exact reasons why champion cavs should exist why they should be made in a game. We don't want these strengths to vanish, at any means. My whole idea is to put a soft limit onto the number of these that can appear. That's all. The focus is actually not fortresses but the constraining the rate of production of champion units.

The range visualisations shouldn't affect the game state when computing simulations, right? It is a pure visual element. Therefore it shouldn't be a part of OOS. The same applies for alarms suppression queue, which shouldn't be reported as OOS if it's different for each player.

You can play all slings, it's not weak, some players do that, but that's not as effective as a mixed army. Playing Britons every day, I find that 40 slingers + 40 javs + 50 spearman is the best combination. Reason: pathfinding + dmg output + snipe Athenians is also better when mixed with jav cav and merc javs. In A27, siege weapons seem quite unecessary unless your enemy is ultra turtle with towers, forts and walls. You can capture CC with any army after they lose, no need for using slings to smash. I find beating their defence army more important than using siege to knock down buildings.

I agree with this, but sadly there is no balance when it comes to champions right now. Some civs just have better champions that counter other civ's champions. If you try to balance all of the champions, people will scream "historically inaccurate" or "boring"

Melee will end you. I would argue that you are not forced into building the fort. If you want to attack early, you push before their fort is up or while they are building the fort. You would have an advantage, because they are investing building labour and huge quantities resources into the fort. Their units would also be in a bad formation and you can melt the builders if they don't react early enough. Since champion spam no longer exists, it's possible to win fights with a CS army + good micro. The champions will just be an icing on the cake for those who had a chance to build it. It would be more attractive to play aggressively, compared to the current meta of waiting for the champion unlock tech then spam broken units. Another idea is we give every civ a special building for them to produce champions from. But that is a lot more work than just moving back to fort.

I think l10n folder contains the translations for "Food"