Changes in what a 3.2 ruleset can do
Re: Changes in what a 3.2 ruleset can do
Type / module of the AI's to be created can now be controlled by a new aitype server setting. hrm #858206
Re: Changes in what a 3.2 ruleset can do
Default AI level is now settable also as a server setting. osdn #44105
This allows things like having the level defined in settings section of game.ruleset, and also, when some players have already been created, without changing levels of those existing players like the dedicated level setting commands do. Separate commands still remain, to be used in cases where their semantics is more correct.
This allows things like having the level defined in settings section of game.ruleset, and also, when some players have already been created, without changing levels of those existing players like the dedicated level setting commands do. Separate commands still remain, to be used in cases where their semantics is more correct.
Re: Changes in what a 3.2 ruleset can do
Lua: Player:lose() method added osdn #44273
Re: Changes in what a 3.2 ruleset can do
Ruleset author now has some control over how AI evaluates how valuable user defined effects are. Previously AI has given no value at all to them. osdn #44771
Re: Changes in what a 3.2 ruleset can do
Hut type extras can now appear (generated by the map genarator) also to frozen terrains. hrm #660056
Re: Changes in what a 3.2 ruleset can do
Trade partner revealed only if ruleset requests so osdn #42970
There's no longer need to reveal ends of the trade route to each other in case of international trade route, so we don't by default. Ruleset can still enable the old behavior of revealing the trade partner.
There's no longer need to reveal ends of the trade route to each other in case of international trade route, so we don't by default. Ruleset can still enable the old behavior of revealing the trade partner.
Re: Changes in what a 3.2 ruleset can do
Ruleset can now enable new "Shared Tiles" clause type. osdn #44161
With such a clause in a treaty, the receiving party's cities can place their workers within the borders of the giving party.
With such a clause in a treaty, the receiving party's cities can place their workers within the borders of the giving party.
Re: Changes in what a 3.2 ruleset can do
Units now have a generic requirement vector. hrm #846779
Re: Changes in what a 3.2 ruleset can do
This one is not a ruleset feature, but a scenario one. As we don't have separate thread for those, I guess it's ok to tell about it here.
Scenario file can now mark players in it so that user connecting to the game automatically gets one of them (previously user had to /take player when no player has been associated with the user's username). This is given as weight, so when multiple players are available for potential autoselection, they may have different likelihood to get randomly selected. hrm #701752
Scenario file can now mark players in it so that user connecting to the game automatically gets one of them (previously user had to /take player when no player has been associated with the user's username). This is given as weight, so when multiple players are available for potential autoselection, they may have different likelihood to get randomly selected. hrm #701752
Re: Changes in what a 3.2 ruleset can do
Lua: Directions now have boolean cardinal property. hrm #657148