Leaderboard
Popular Content
Showing content with the highest reputation on 2025-05-16 in Posts
-
If you believe a moderator is abusing his privileges, please report that in a private message to me instead of accusing somebody publicly.3 points
-
3 points
-
3 points
-
Hello everyone, This is my first time posting, and this is also my first mod for 0 A.D. This mod changes how units are reassigned when a player is defeated. Instead of transferring to Gaia, the units now go to the next undefeated ally. I think this is a really interesting mechanic, especially when playing the Regicide game mode—where all of a player's units get reassigned when their hero dies. Let me know what you think, and feel free to suggest anything I should add! Check it out here: https://github.com/TobyDustin/0ad-refugees-mod I'm also trying to get it on Mod.io. If anyone knows how to do that, I'd really appreciate your help. Here's the preview link: https://mod.io/g/0ad/m/refugees-mod?preview=f5ab66257bcb802a72f07e11b3139287 Some screenshots:2 points
-
I can answer, even if I'm not nani. Very important questions - which eventually can be rephrased as "why use proxies?". I hope the rest of this post will clarify. There are various reasons, I'll just state the two I find most important. One reason is compatibility with other mods. Imagine two mods overwriting the same init function: then, only the last loaded mod will work, whereas the first loaded mod will not work - not nice for users. Additionally: if you develop a mod, you expect to develop your code based on options.js from the public mod, right? But if this file is replaced by some arbitrary custom file, you can never know if your code will work properly. In other words, if you want your mod to be compatible with other mods, then you should let the other files exist, and not overwrite them. Another reason is compatibility with 0 A.D. itself. When a new patch or version of the public mod is released, it may happen that options.js gets changed too, as part of the update. If so, you (the mod developer) must take care of replacing that file too, and release a new version of your mod with the new file. And you have to do the same will all other files that have changed... dirty job indeed! Instead, if you build your mod around existing files, your code will (most likely) work straightforward - without having to check for all files that have changed and replace them one by one. So, what does it mean to build around existing files? And what should modders do? Answer is: use PROXIES! Javascript Proxies (similar to Python decorators - I seem to remember you like Python) ensure that modded objects wrap existing objects without overwriting them. An example: by using a proxy, you can run your custom init function after, before or around the original init function. And this is exactly what happens inside options~autociv.js! patchApplyN is a brilliant example of a proxy: it executes custom code around the original init function in options.js. You can find another concrete example of a proxy for the init function in options.js here. Most likely, it is caused by another mod which replaces existing objects/functions/variables/etc. - and if this is the case, you can gently ask the author to get acquainted with proxies.2 points
-
Someone needs to make a PR. Meanwhile: standalone mod to get this tooltip : garrisonedInfoTooltip.zip Already in Moderngui too.2 points
-
Ok @Genava55 do you have a possible idea for a raiding type unit? The gameplay design is somewhat focused on infantry mobility, so a faster, lightly armored, infantry unit is needed to replace the wolf warrior. i suppose we could go fairly generic and call it Crimbri raider or something.1 point
-
1 point
-
1 point
-
I don't think there was a specific troop wearing wolf skin and wolf head. Tacitus, Cassius Dio and Caesar don't mention it. The only place with a depiction of a sort of warriors wearing such items is on the Trajan column, but it is unclear if those are Germans or not. Those men are Roman auxiliaries in full armor, while the actual Germans fighting in front of them with their native weapons are bareheaded. Furthermore the current design is focusing on the Cimbri and pre-roman period. The berserkir/ulfhednar is mostly attested during the viking and post-viking period, in the Norse mythology and Norse laws. And nothing suggest they were a specific battle unit. So for the moment, leave them aside.1 point
-
1 point
-
Again, I don't think I care if my basic units needs 1 more XP to become advanced. I need to know if it's already ranked up or not. There can never be "one true way" to play the game. "Idle" units wouldn't be idle, they are training.1 point
-
Adding an experience meter that looks similar to the health meter of garrisoned units seems desirable. As for other suggestions, a quicker experience trickle for garrison units seems reasonable as its current form is useless. I would put this behind a tech, so it would be a choice between p3 eco techs and this experience tech. That would give a quick single push real strength but would sacrifice the ability to carry out a long term fight. But giving experience points to idle units seems to reward bad play and I don’t like that idea at all.1 point
-
"Hello, friends! I apologize for the delay, but this week was very busy and I couldn't make much progress on the project. However, I did manage to bring some news! I implemented two new buildings: the oven and the weaving workshop. In addition, I created another house variation, totaling 15 different options that can vary according to construction. The oven will be used to develop ceramic and clay technologies, improving buildings. The weaving workshop will have technologies that will improve units, such as protection, creation of primitive weapons made of stone and bone, and more resistant clothing. I also added music to the project! I completed all the buildings of the Flintstone Age and now I will focus on the units, improving textures, clothing, armor, and creating new units. One of the main goals is to create a nomadic leader who will be the first representative of the group on the journey. Leave your impressions here and share with your friends! I'm open to suggestions and ideas! See you next week!"1 point
-
Well the main way units gain experience is by having a successful fight, using healers, or moving wounded units to the back of the group. I think it is a desirable outcome that units generally take a long time to rank up by garrisoning, but it would be nice to show the mean rank of the units on the corresponding icon of the unit garrison stack within the barracks.1 point
-
1 point
-
This scenario is based to 265 B.C. in the Mediterranean sea, one year before the first punic war. In the past I realized various maps based in Europe and in this period, but the most of these aren't playable anymore, so i made another map for this scenario. The civ you can choose are: Aedui(Gauls), Romans, Carthaginians, Edetani(Iberians), Macedonians, Suebi(Britons), Iceni(Britons), Sarmatians(Gauls). RiseofRome.xml RiseofRome.pmp1 point
-
I think both of you have good points. And of course, I'm going to encourage you the take a look at historical patch. We have tried addressing this a little. As there are now "serf" units which can still fight but not as well as CS, but are better at gathering res. Then you have the merc type units that can build and fight, but not gather. And of course you have the champion, elite fighters who cant gather or build. I like the historical accuracy of the citizen soldier, and the more i read and learn about the different civilizations I agree its an important aspect of 0ad that makes it unique!1 point
-
MarcAurelius is a prime example of how power corrupts people, thinking he is above everyone else because he can mute/ban people as he pleases. Please remove this guy from the team, his continued presence in this role endangers the very principles they were meant to uphold. He must be held accountable and removed effective immediately!0 points