Unmaintained Tier Protection FREE 1.2
- Author jraServerAPI
- Creation date
The "Unmaintained" prefix is a technical term often used in the development world to signal that a specific piece of code, feature, or a resource is no longer actively managed or updated by its creators. It's similar to a 'Beware' sign on a physical property, warning visitors to proceed with caution.
For instance, if a developer creates a resource for other users to use, but later decides not to continue updating it due to various reasons like time constraints or shifting focus to other projects, they might attach an 'unmaintained' tag to it. This tag serves as a clear indication to other users that while they can still use this resource, they should be aware that it may not be up-to-date with the latest coding standards or security updates.
From a user perspective, an 'unmaintained' tag can help yourself identify resources that may not provide the best experience or security. It signals that the resource in question may have outdated features, potential security vulnerabilities, or bugs that are unlikely to be fixed.
For instance, if a developer creates a resource for other users to use, but later decides not to continue updating it due to various reasons like time constraints or shifting focus to other projects, they might attach an 'unmaintained' tag to it. This tag serves as a clear indication to other users that while they can still use this resource, they should be aware that it may not be up-to-date with the latest coding standards or security updates.
From a user perspective, an 'unmaintained' tag can help yourself identify resources that may not provide the best experience or security. It signals that the resource in question may have outdated features, potential security vulnerabilities, or bugs that are unlikely to be fixed.
What's new in version 1.3
- Added full cluster support with MySQL integration
- Fixed bug with the NPC in Genesis missions being protected in Thatch tier
- Fixed bug with tribes tiering up and "resetting" the lower attack overrides, when EnableLowToAttackHigh=true. Now when lower tiers attack higher tiers, the two tribes can battle anytime thereafter.
- Added NewTierProtectionDurationInDays - this temporary protection you get once you have tiered up. This is to protect you from immediate attacks from any tribes that may have been waiting to attack you the moment you tier up. New tier protection also protects you from lower tier attacks.
- Added ProtectedTribeIds to configure full time protection for admin stuff etc..
- Improved performance overall.
The config file has been updated.
Also if you are not going to use MySQL then you should remove your database files, because the database schema has changed.
