Emmanuel BENOîT
afc66166e0
* Changed the way mining settings work: use a priority value (between 0 and 4) as the weight. Leaving them as they were before would have caused numerous problems (and a lot of unnecessary code to work around them) * Empire mining settings will be created along with the empire's own record. By default all natural resources will have weight = 2. * Added a set of four stored procedures which can be used to update an empire's mining settings, including planet-specific settings. The emp.mset_update_start() function can be used to start an update (on an empire's settings if there is only one parameter, or on a planet's settings if there are two parameters); the emp.mset_update_set() and emp.mset_update_apply() functions are then used to modify the settings and apply the changes, respectively. |
||
---|---|---|
.. | ||
000-typedefs.sql | ||
010-i18n.sql | ||
020-prefs.sql | ||
030-users.sql | ||
035-session.sql | ||
040-admin.sql | ||
050-accounts.sql | ||
055-bugs.sql | ||
060-naming.sql | ||
070-constants.sql | ||
075-resources.sql | ||
080-techs.sql | ||
090-buildables.sql | ||
100-universe.sql | ||
110-empires.sql | ||
120-construction.sql | ||
130-fleets.sql | ||
140-status.sql | ||
150-logs.sql | ||
160-battle.sql | ||
170-events.sql | ||
180-messages.sql |