elexis

Why?

In alpha 21 the old fields have been replaced with new ones. I was wondering whether it would be better to have 2 variants of fields: one that provides food indefinitely and another that has a finite food supply, but faster gather rates. Thus we could also use both models (to me they look like wheat and grapes or apple trees).

Careful with the crush damage, do we want those things to destroy buildings, if so how many should be required?

That is true for rated 1v1s. Team games are a different story as setting players who left to defeated won't help the team that misses the player. Lag-trolls: Most people who are affected by lag are sorry for it, try and often do fix it. But there are f.e. some that acknowledge that they are lagging everygame every time, also observers yet won't leave the game freely wasting the time of all clients. Or people who rejoin a running game as late-observer, causing a very noticeable performance-lagspike. Once successfully connected they say hi, leave the game again, start rejoining again and again for no reason. Noob-trolls: Claiming to be an experienced player and then building 2 houses in the entire game. Leaver-trolls: Discussing the game settings, playing for some time, then resigning and exiting arbitrarily, without any warning, sometimes even without being attacked, thus defeating the entire team (typically gaia units killing the entire tradeline). (Often observers would be willing to play in place of the leaving palyer, but that won't work if he has resigned and decided to let his units attack his allies). I agree that it doesn't sound feasible nor sensible to track these things statistically. A moderator shouldn't be required for the issues above. The players inevitably have to identify how their teammates will play or whether they will end up sabotaging the match on purpose or due to negligence. It is the duty of the host to confirm and take the decision to either unassign or ban clients that are not compatible.

So we know what to commit after feature freeze :->

Hm, before seeing this picture I never realized how important damage variants are. They've been overdue. (Building crumbling sounds also in my opinion.)

a19 had the new pathfinder, but there were also some formation changes http://trac.wildfiregames.com/search?changeset=on&q=formation&page=2&noquickjump=1, 3086 perhaps

Guess you mean #3212: enhancement: [PATCH] Provide a unit tree like the tech tree is provided (We need simple tickets for those things. They might rot for some months or years, but it's not unlikely at all that it's being picked up)

Looks good. I recall the prosa code being really ugly as well. Where is the diff implementing that? (Couldn't find it in the delenda est repo) Having an overview that splits the trade carts by current tradegain seems nice, but not sure how to implement. These carts should be selectable, so that if one has 30 carts on a good route and 5 one with a bad route, the bad ones could be rerouted without affecting the good ones. (We can already see the total amount of resources they carry by selecting all trade carts (alt + doubleclick) and then moving the mouse over the number of units indicator)

"I remember the days when we played 1vs1vs1 and everyone won in their game because we were OOS " Ah, so you're voting for clinton? Seems to have worked though, as the second release candidate is being packed and tested.

Probably because half the buildings are for free with ptolemians.

I meant LordGoods images

First release candidate has been distributed, but we have found 2 more out of sync errors. Need prayers, not complaints

There are many core functionalities which are part of the "public" mod. Just the simulation part includes the ability to move (UnitAI) or attack units, capturing, build buildings, training units at buildings, gathering resources, fogging for example.

wang_wei also got this error after installing boost 1.62.. He solved it by symlinking 1.62 as 1.61

You can release it as an own independent game with its own identity and just hide the fact to the user that it's a mod. Why reinvent the wheel.

The edges of the soldier are very sharp, there could be some blur as the camera (nor eyes) can't focus both on the foreground and background.

Writing a new game based on the current engine is a task that will take many months, probably years. I suggest to start with a creating a mod http://trac.wildfiregames.com/wiki/Modding_Guide and replacing things one by one. Your new mod should only contain the new and modified files (instead of copying the old ones from the "public" mod). You might want to start with the templates in simulation/templates/ which specify the stats, names and graphics of the units. Then you will likely need new models if you want a different timeframe or civilizations. Even the public mod's game logic is designed to be versatile enough so that mods can reuse it. So you likely don't want to rewrite that but just extend some things if you want new features.

Replay? Can anyone test whether alpha 20 has it too?

Is it the old bug with errorspam or is it solely the animation? The animations had been rewritten in alpha 21 and there were some things like that already.

#3734 is done (both the open age ratings system and the keywords for the software center, amongst other improvements), someone should mail that gnome developer.

The error Phalanx describes is exactly out-of-sync error that occurs when doing something with the wrong revision or if there is a serious bug which I can't imagine being the case. Can you still reproduce the issue? Like exiting 0ad, updating to the most recent version, starting a game, then replaying the game (with or witout restart) and then getting those oos-errors you described?

If you still know the replay, you can lookup the time in the replay menu and click through http://trac.wildfiregames.com/changeset/ to find the according revision. Either way, in case you can reproduce any issue (whilst ensuring that the revision nr didnt change meanwhile), tell us.

Savegames can only be loaded with the same revision they were saved with. Same for replays.

Ok, so we're done with alpha 21 portraits of new structures. Thanks for your work Lion!