Mentula

Currently not, but it doesn't look hard to implement (at least, in the context of the LocalRatings mod). Basically it's a matter of summing up the game duration, alongside the other players' stats. Cool idea! Edit: adding up the game duration might be an imperfect solution. A problematic case is the one of a player early-quitting the game: their stats will be computed until the end of the replay, although the player has left before the end. This problem (although it's probably a minor one) also affects the way LocalRatings currently computes stats; I don't have a good solution to this.

The smell of a new 0 A.D. release is in the air so... here's my TOP30 for the A26 season! My settings Match Filters: games with < 4 players are excluded. Player Filters: players with < 5 games are excluded. Score Weights: default, apart from exploration weights set to 0. Few comments Feel free to ignore #1 from the ranking; the mod tends to overestimate the owner's rating. I wished I had more games played with strong players. Unfortunately some of them do not appear in the list due to the small numbers of games played.

Good to hear you solved @JamesWright, maybe you can add some more details on the problem you encountered and the way you solved (e.g. the packages you installed) so that other users encountering the same issue can benefit from your solution.

Here we're going a bit off-topic but... this is not standard dev operation. If you are a modder reading this, please do not follow this recommendation. There are valid guides on the forum explaining how to make mods for the game.

Sorry to say this solution does not work. One can run any "pre-approved" mod as a subroutine of another mod (or even a modified version of the engine) which emulates checksum generation, for example, sending a pre-computed checksum.

I am trying to make a sense out of this. The whole point of LocalRatings being local is that the mod user is the only one who can see ratings and that ratings are calculated based on the user data. Why would one tweak a rating being the only one seeing it... self-motivation? PS: the fact that a user can edit a free-and-open-source project and its files (including replays) should not come as a surprise. Welcome to foss!

You can try this and tell us if it gets better.

Yes, heroes can die in Regicide mode. You can whitelist the "Hero" class from the options menu to prevent it.

Yes, you read the title correctly: this mod causes extinctions randomly destroying your entities. Official mod page on GitLab here. It's a semi-serious (working!) mod, whose idea originated from joking conversations in the lobby. Too OP and want to balance games? This is your chance to set it right. Features Set the entity reduction rate and the frequency of extinctions. Intensify/alleviate the entity reduction rate and frequency over time. Choose which entities can or cannot be destroyed. Totally voluntary usage: other players don't have to install it to play with you. Is that serious? Yes and no, I mean... it can be fun! On a serious note, scenarios or campaigns can be designed on top of it. After all, the idea is not that different from already existing features such as the rising of water level in the Extinct Volcano map. Events like the spreading of the Antonine Plague, imported by the Roman legions from the Near East, immediately come to my mind; although this example is outside the 0 A.D. time frame, events like this might well fit a scenario/campaign. Mod options (screenshot) Installation Click here to download the latest release. Install following the official 0 A.D. guide: How to install mods? Alternative downloads: Latest Release (.pyromod) | Latest Release (.zip) | Older Releases Contribute The public repository is at this page. Everybody is very welcome to contribute, suggest, fork or simply give feedback. Have fun!

If any of you is wondering why this mod is useful, this is what I do in almost every game: when reaching the population cap I might want to make space for new units (such as rams or elephants), so I do: 1. select all fields, 2. select one gatherer per field (using the mod) 3. destroy the selection. Another use case is when floating in food and short in wood. In this case one can: 1. select all fields, 2. select one gatherer per field (using the mod) 3. send selection to wood. In these (and certainly other) cases, one can keep field harvesting at its maximum efficiency.

Hi 0 A.D. friends, the FieldManager mod I am presenting in this post is aimed at reducing micro-management on fields. Official mod page on GitLab here. The mod has been around for a while and I see players on the lobby already using it. I was hesitant to announce it on the forum, for I wished to come up with more functionalities but... I couldn't so here it is! Despite its ostentatious name, the mod provides few but useful features: Select military/non-military/all gatherers from selected fields. Select one gatherer from each selected field. Evenly distribute gatherers across selected fields. Here's a screenshot of the commands available when selecting a number of fields: Be aware that... This mod executes automated actions. This can be considered as a cheat. When you play a game with this mod, make sure other players are aware you are using this mod and agree. Installation Click here to download the latest release. Install following the official 0 A.D. guide: How to install mods? Alternative downloads: Latest Release (.pyromod) | Latest Release (.zip) | Older Releases Contribute The public repository is at this page. Everybody is very welcome to contribute, suggest, fork or simply give feedback. Have fun!

Unfortunately no, as far as I know. It would be great to have an "Inspect" functionality, like the one present on most browsers. Maybe it is worth to considered it as a long-term addition to the game. This would make the game more attractive to modders and facilitate the development of mods/features/patches. @Stan` what do you think?

The local.cfg file must be placed in the same folder as the user.cfg file. Therefore, look for user.cfg in your system. On a typical GNU/Linux installation, the user.cfg file is in ~/.config/0ad/config, but since yours is a snap installation, I have no clue where to find it. I'm sure you will easily find it with a file search. Surely though, the folder in which user.cfg is placed is not the same of default.cfg. Remember that default.cfg is not supposed to be changed. You will only use it to look at all the possible configurable options, and copy-paste from it to your local.cfg, but don't modify it.

I hope this post can clarify things a bit more. There are at least three options to change hotkeys. Option A Open 0 A.D., then open the Settings > Hotkeys menu. Change hotkeys from there. Note: @gui456wSERTDYF I know you are already aware of this solution, but I report it for completeness. This solution can be ok for replacing few hotkeys, but not suitable for changing many hotkeys. For example, this is not ideal for @gui456wSERTDYF's issue (replacing "Ctrl" everywhere). Option B Look at the default.cfg file present on your computer: this file should look like this. Each line identifies a configuration option. Just to make one concrete example, the default hotkey for attackmove can be found under the [hotkey.session] section in the default.cfg file: [hotkey.session] attackmove = Ctrl ; Modifier to attackmove when clicking on a point I you wish to rebind attackmove, say for instance to CapsLock, add this line to your user.cfg file: hotkey.session.attackmove = "CapsLock" Option C (recommended) Very similar to Option B. Following the above example, if you want to rebind attackmove to CapsLock (again, as an example), add these lines to your local.cfg file: [hotkey.session] attackmove = CapsLock ; Modifier to attackmove when clicking on a point The local.cfg file lies in the same folder as the user.cfg file; it possibly doesn't exists: if so, create it. The local.cfg file has the same structure of the default.cfg file. In principle, you can copy-paste everything you want from default.cfg into local.cfg and tweak the values at your own needs. Note: this solution is probably the one @gui456wSERTDYF is looking for. You can copy-paste all the default.cfg content that includes "Ctrl" into local.cfg and replace the "Ctrl" occurrencies with the key you like. Remember to include the section names (in the above example, the section name is [hotkey.session]). Option D (not 0 A.D.-related but OS-related) @gui456wSERTDYF if your Ctrl key is not working... have you considered assigning Ctrl to a different key system-wide? In many operating systems (and certainly in the GNU/Linux ones) you can assign Ctrl to other keys, for example to CapsLock.

Yes @real_tabasco_sauce. Look at these lines (and many view-related others) in the default.cfg file: [view] ; Camera control settings scroll.speed = 120.0 scroll.speed.modifier = 1.05 ; Multiplier for changing scroll speed What you might want to do is to copy-paste these lines (and others that you wish to change) into your local.cfg file and tweak the values at your own need. If instead you wish to change these values in your user.cfg you can add the lines there: view.scroll.speed = "120.0" view.scroll.speed.modifier = "1.05" and all the other lines you want to tweak, with the values you want. Basically, there are two alternatives: do it in local.cfg or in user.cfg. I recommend the first of the two options; there are reasons for that, which I omit here.

This question has already been asked and answered here: This page will help you find the correct datapath of the configuration files for your operating system: https://trac.wildfiregames.com/wiki/GameDataPaths Cheers

There is no shared database/cloud/space for replays, as far as I know. The idea of sharing replays has been brought up by other users, and I personally like it, as it has other side benefits in terms of sharing knowledge about the game. For what it is worth, my dream is that one day Wildfire Games will have the economic and developing resources to afford own lobby servers. That will allow collecting replays, along with solving many of the major problems affecting the game today.

I updated ResetQueue to version 0.26.2. The main change is a new hotkey that clears the trail of production queues: in other words, all but the current item are removed from the production queue. This hotkey is in addition to the existing one, that completely clears the production queue (including the current item). Further, with the new version, hotkeys are not mapped by default to pre-set keybindings; I noticed that some users find conflicts with existing keybindings, so it's better to leave the choice open. Cheers. ResetQueue.pyromod ResetQueue.zip

Hello everyone, I recently had a few conversations with players on the lobby about "how to improve". When I am being asked, I usually reply with: 1. watch replays 2. watch ValihrAnt videos 3. read this file. This file is what I am presenting in this thread: it's a collection of tips & tricks I initially shared with my friends and then made it public on my GitLab page. It might be incomplete, it might be wrong in some of its parts, it might give importance to aspects that are not or viceversa, etc... I am not in the position of claiming this is a manual to become a good player. However, it might be useful to somebody and I'm happy to share if it helps. The file is divided into three sections: 1. Interface, 2. Logistics, 3. Fighting. Each section contains a list of tips & tricks in sparse order; each tip comes with an extra tip. Cheers Source: https://gitlab.com/mentula0ad/0ad-tips-and-tricks

Hello 0 A.D. friends, I have been thinking about the possibility of making a mod implementing macros and came to the conclusion this is feasible, albeit complicated. Despite my good intentions, I will be in shortage of time very soon, and this is the kind of project that takes a while to be developed. Perhaps, this is also the kind of project that triggers the interest of some of you smart guys populating the forum. If so, this is the topic for you. If any of the developers has considered this before, I'd be curious to hear from them. This might not be a new idea after all. This post is organized in sections, so a reader can skip the parts they're not interested in. 1. What are macros? 2. Why do 0 A.D. players need macros? 3. Why macros, when there are mods around? 4. What's the proposal? 5. How can a player define a macro? 6. Implementing macros can be complicated

It's on the FAQ page. In short, the page says: For a general overview on the ELO rating system(s), Wikipedia offers a good explanation. As you will notice by looking into elo.py, the adjustment of a player's rating mostly depends on the difference between that player and their opponent. The stronger your opponent is, the more your rating will increase in case of victory. Similarly, the weaker your opponent is, the more your rating will decrease in case of defeat. Therefore, having played hundred of games does not say much on the player's ELO rating. Winning/losing "quality" games is what affects the rating most.

@maroder's solution is correct. For your information @Thales, you can achieve the same, but without entering the Game Lobby. Just do the following: one of the players hosts the game: from the main menu choose "Multiplayer" and then "Host Game"; the other players join the game: from the main menu choose "Multiplayer" and then "Join Game". The joining players just need to enter the IP address of the hosting computer in the prompt. If playing with people you know, this alternative solution has some benefits: no need to register/authenticate with a lobby account, no need to set a password when creating a game, no information on your games are made public, risk to be DDOSed is reduced.

@poised you can toggle the summary charts by pressing "Ctrl+Tab" at any time while watching a replay. I know this is not exactly the solution to what you are asking for, but it's a good approximation and a viable solution that does not require tweaking the code. In my opinion, this is satisfactory enough.

Colors are obtained from the player name by applying a specific function. The function is described here. The function's documentation also refers to this page on StackOverflow.

default.cfg is the right file for default configuration parameters such as keybindings. Your default.cfg file should look like this one; as you can see, all keybindings are listed there. local.cfg should be used for custom configuration. This file is possibly empty and you can edit it at your own needs.