Issue:
If the season begins on spring, or begins on another season and gets to spring, the program will no longer cycle seasons after the timer decreases.
Replication:
Start the server on the season spring, set timer to 1 minute. After 1 minute, the season will remain as spring.
Identification:
The issue is identified to be line 258 of SeasonManager.java, specifically setting the season. It's a logical issue caused by setting the season to the same season, not the next. This causes an infinite loop of not allowing seasons to cycle past spring.
Solution:
Have the manager set the proper season, allowing for the proper cycle.
Why was it not caught?
During testing I had the season set to summer in an effort to test some WIP features, and never got around to testing all seasons.
Hotfix?
The implemented patch will be released in v 2.0.2 alongside Perks and Stats.
Issue:
If the season begins on spring, or begins on another season and gets to spring, the program will no longer cycle seasons after the timer decreases.
Replication:
Start the server on the season spring, set timer to 1 minute. After 1 minute, the season will remain as spring.
Identification:
The issue is identified to be line 258 of SeasonManager.java, specifically setting the season. It's a logical issue caused by setting the season to the same season, not the next. This causes an infinite loop of not allowing seasons to cycle past spring.
Solution:
Have the manager set the proper season, allowing for the proper cycle.
Why was it not caught?
During testing I had the season set to summer in an effort to test some WIP features, and never got around to testing all seasons.
Hotfix?
The implemented patch will be released in v 2.0.2 alongside Perks and Stats.