v4.32.0

Changes

• Battles are now planned from players' availability. Instead of voting on the first battle day and then on each day's hour, players mark every upcoming date and start time they can fight, in game with /war vote <war id> or on the war's website page.
• Day lock: 48 hours before a date's battle window opens, the date becomes a battle day if enough of each side (war.availability.min_per_side, 3, or the whole side if smaller) can come at the same time. Otherwise it is "no battle".
• Time lock: 24 hours before the window opens, the start time is fixed to the hour most of both sides can make. The battle is set on its province at 16:00 on the battle day, so retreat, installation picks and intel keep their timing. Battles can be on consecutive days.
• After three dates in a row without a battle (max_days_without_battle), the third becomes a battle day anyway. If one side marked nothing that day, the battle is autoresolved. Postponements are gone.
• Raids are possible every day once the buildup is over (one per side per day), not only on battle days.
• Reminders, in game and as Discord DMs through the website: when nothing is marked before a day lock, when a battle day is set, and 3 hours before its time lock. "None of these days work for me" stops them.
• Running wars keep their votes: day and hour votes become marks, and a voting or scheduled war keeps its battle day.
• New config war.availability (days_shown, day_lock_hours_before, time_lock_hours_before, min_per_side, max_days_without_battle, vote_url). The old battle_voting and buildup day-vote keys are ignored.
• Staff: /war admin schedule <war> availability | lockday | unlockday | sethour | skipday | castvote; /war admin buildup <war> setday locks a battle day.
• Needs TFMCWeb with war availability (v1.4 contract) and the factions cog's war posts update.
• Battle availability: vote on days and times ahead, day locks 48 h before, time 24 h before by @Drefvelin in #242

Full Changelog: v4.31.0...v4.32.0

Downloads

• simplefactions-4.32.0.jar
• SHA256SUMS — SHA-256 checksums.
• build.json — Build metadata.