Add localised reinforcement decay. #87
Conversation
|
I didn't see a config option for decay time, does it utilize the global_decay_timer and global_decay_multiplier that are currently in the config? |
|
Yes, it uses those values. It just changes the last activity time. |
|
bump |
|
A couple config comments: Can you add a config option for using the local decay, or defaulting back to the global decay? So this version of Citadel can be maintained with the feature even if users don't want to have local decay. Also, does this just work on top of the global decay? As in, does this local decay just have the opportunity to update the decay time earlier than the global decay? Just checking to see if you can seamlessly switch between the local and global |
|
Yeah you can switch betwen local and global seamlessly as long as you set the You can also disable local decay entirely by having it enabled on no worlds: |
|
Will the activity-default override all current group decay? For example, there are groups which are currently decayed. Will enabling this with activity-default set to now cause currently decayed groups to be reset to not decayed? |
|
No, the activity-default is used if a player on a group has not entered an area yet but a player on said group has logged in past the activity-default timestamp. If nobody on the group has logged in since the time set by activity-default, their last activity time is used. |
|
I tested and if you add this code and set activity-map-worlds: [] so it's 'disabled' it will still make the decay localized |
| }, 20 * 30, 20 * 30); | ||
|
|
||
| try (Connection connection = source.getConnection()) { | ||
| connection.createStatement().executeUpdate(CREATE_TABLE); |
There was a problem hiding this comment.
We have a system in place specifically for adding/modifying tables. This allow better tracking of when things break and modifying tables later on.
Closes #56