Leaderboard

Why this topic feel so old, I mean its old as well. Anyway, im from Vietnam, the land of the blue dragon, and let me explain why it's called this. Vietnam is sometimes called the “Land of the Blue Dragon” because of a mix of ancient mythology, geography, royal symbolism, and East Asian cultural traditions. Dragon itself is a sacred creature in Vietnamese culture. My name is Duc and nice to meet you all. I am learning content writing and here is a website I work for, its for motorbike tours: https://www.irtouring.com Anyone from Vietnam, or where y'all coming from? Thank you and take care

Well if you know someone that can implement hotseat (that's how that's called) feel free to redirect them to https://gitea.wildfiregames.com

Welcome to the official topic for Classical Warfare AEA - A more in-depth version of 0 A.D., with an emphasis on historical accuracy. New units and technologies, but a similar approach to the game. (In simple words, we think it makes the game better.) Our original post was deleted when the account was accidently flagged for spamming Anyway, welcome and we hope you enjoy the mod. IF you have any suggestions or are fascinated with this part of history and want to contribute don't be shy! We are hoping to keep it going as long as there is interest from the community, after all it's the community that makes this game and this project so much fun! Big thanks for all the people along the way that have helped keep this project going. Starting with of course the one and only @TheCJ but also @Genava55 @Atrik (but he seems to mostly be retired now) @Tyrannosaurus @Thalatta @Seleucids (another retired OP soul) @Outis @Stan` and I'm sure many more that I am forgetting. Emacz2/classical-warefare-aea our git hub incase you want to download or check out some of the differences! you can visit our webiste here! Thanks @Asher for setting it up

I think it would be nice if when a host disconnects, the game is automatically transferred to one of the other players, until there are none left. This would: A: help people who are hosting a match of 3 or more people, and have to go mid-game B: fix hosts being able to cheat the ratings system by exiting the match, the other players could then defeat they’re uncontrolled units and structures.

LocalRatings Team Balancer A mod that extends LocalRatings by Mentula with two new buttons on the game-setup screen. One balances teams automatically by rating, the other evaluates the current setup and adds two outcome-based rating systems, Glicko-2 and OpenSkill, alongside the original LocalRatings score. Why outcome-based ratings? The LocalRatings ranking list already shows the problem: even with plenty of replay data, some known-strong players end up rated poorly and some known-weak ones look stronger than they are. Raw in-game statistics don't track skill cleanly. In a 4v4, if three players focus-harass one strong opponent, that player's stats look weak, though they're being targeted because they're strong. A useful comparison: modern chess engines evaluate positions with neural networks far beyond human understanding, yet FIDE still uses Elo, chess.com uses Glicko-1, and lichess uses Glicko-2. Even with perfect game analysis available, the established outcome-based systems remain the standard for tracking player skill over time. Win/loss results across many games carry a signal that in-game metrics miss. 0 A.D. has no chess-engine equivalent, so the case for outcome-based rating is even stronger here. Rating systems Three systems are available, selectable in the LocalRatings settings: Local Ratings (original) - rates players by in-game statistics relative to others in the same match. Works for all game types but inherits the limitations above. Glicko-2 - tracks each player with a rating, a rating deviation (confidence), and a volatility. New players start at 1500 ± 350. The conservative rating used for balancing is rating − 2·deviation, so a fresh player is treated as significantly weaker than someone who has won even one game. OpenSkill - an open-source Bayesian system based on the Bradley-Terry full model. Each player has a mean skill mu and an uncertainty sigma. New players start at mu 1500, sigma 500. The conservative rating is mu - 3·sigma. Glicko-2 and OpenSkill only count locked-teams games with exactly two teams; free-for-all and unlocked-team games are excluded. All other LocalRatings filters (minimum duration, population cap, cheat games, etc.) still apply and can be configured in the LocalRatings settings. Win/loss counts are tracked separately and shown alongside ratings. Balance button When the host presses balance, the mod reads all currently assigned players, looks up their ratings, and finds the partition into two teams that minimizes the difference in conservative rating sums. It then reorders the player slots. The result is posted in chat with rating sums, the rating difference, and a predicted win probability. Note the win probability it calculated with the raw rating and the pairing done with the conservative rating. Non-host players with the mod see a suggest button instead. Pressing it posts the same proposal to chat without changing any settings, so the host can decide whether to apply it. Both buttons have spam protection: pressing them again with the same player constellation does nothing. Slot shuffles or team swaps don't count as a new constellation. Evaluate button Reports on the current team assignment without changing anything: rating sum and conservative sum per team, the rating difference, which team is stronger, predicted win probability, and a full player ranking by rating with win/loss counts. Observers in the lobby appear in the ranking as well. End-of-game rating updates When a game finishes, the rating database updates on every mod user's machine. To avoid multiple mod users posting the same numbers to chat, only one client announces the changes; the others update silently. There's a known chat-line spacing bug that pushes this announcement far below the regular chat area. It can be fixed with this patch Including older replays The engine only exposes replays from the currently installed version, so by default ratings are built from 0.28.0 replays only. To include 0.27.1 replays, copy them into the 0.28.0 folder. They count toward all three rating systems. Linux: copy or move everything from ~/.local/share/0ad/replays/0.27.1/ into ~/.local/share/0ad/replays/0.28.0/ Windows: copy everything from %APPDATA%\0ad\replays\0.27.1\ into %APPDATA%\0ad\replays\0.28.0\ macOS: copy everything from ~/Library/Application Support/0ad/replays/0.27.1/ into ~/Library/Application Support/0ad/replays/0.28.0/ After copying, open the LocalRatings page and press Rebuild list to re-process all replays in date order. This step is needed even when rebuild isn't normally required, because the imported replays are older than your existing ones and the ratings have to be recalculated from the beginning. The imported replays won't be playable as visual replays in 0.28.0, but their metadata is read correctly for rating purposes. Limitations Team rating is inherently harder than 1v1. Individual contribution isn't fully separable from team performance, and the rating systems see each game as a single team win or loss. This is a fundamental constraint of every team rating system, not something specific to this mod. Cold-start: ratings come from the host's local replays only. Since the database is built from whatever the host has played or observed, players who appear in the lobby with no recorded games start unrated, and their conservative rating sits well below average until they accumulate results. A genuinely strong player with only a few recorded losses will likewise look weaker than they are. The automatic team pairing works as a correcting instance: A strong player with low rating will be paired with players with a high rating, resulting in a very strong team and a high likely win. This strong player will then accumulate wins. These unbalanced games might be frustrating. Three things you can do meanwhile: Accept the balance and play. The fastest fix is more games with the automatic pairing. Adjust manually. Use /rate username 1600 to set a player's rating before the match starts. Useful when a rating is obviously off. Seed the database. Download games with known outcomes from replay-pallas and drop them in your replays folder, then rebuild. Pick a balanced selection - similar wins and losses for each player - so you don't accidentally bias the rating in either direction. A player can help to fix their rating by uploading a few decisive games to replay-palas for the hosts to download. Non-decisive games. Most 0 A.D. team games don't end with the entire losing side eliminated, and Glicko-2 / OpenSkill can only update on games where a winner can be determined. The LocalRatings Team Balancer ships with an Auto-Classifier that infers a winner from in-game data (surviving populations, final scores and defeated-count difference) for games that ended without a clean engine verdict. The quality of your ratings therefore depends partly on how well the Auto-Classifier performs on your replay set. Per-game rating changes under your current settings are visible in the replay section. Locked teams. The most sensible option usually would be only evaluate games with locked teams. The problem is when one switches the map e.g. from mainland to balanced-mainland the settings defaults to unlocked teams. In most cases this is harmless as the players just don't change their diplomacy states. Therefore the option Rate unlocked-team games exists. LocalRatings_Team_Balancer.zip

More Infantry photos Daylami mercenaries

The basics are: Spearmans. Archers (in this case it applies instead of skirmishers). Heavy shock infantry either normal or champion. You already mentioned cavalry. 3 heroes. some other unit The name of the priest/healer.

Sassanian military was heavily dependent on cavalry. Therefore, I recommend adding these units to the Sassanian faction : Vacabara: Lightly-armoured horse archers with long range and fast speed but low attack damage and low total health value. Dehqan cavalry: medium-strength cavalry with bow and lance. Quite balanced role. Cataphract: heavily armoured cavalry with lance, but moves slowly. They should have very big total health value Azadan: elite cavalry that can switch between bow and lance. It would be an improvement to allow some Persian and Sassanian cavalry units to switch between bow and spear using a hotkey. Historical Sassanians did this to accommodate for long distance arrow fights and short range combat. In the game, this feature allows the player play more strategies using the same units. I look forward to playing with this faction.