Canceling war and relaunching it is EXTREMELY problematic. Let’s say you have a player who logged in six hours before war started. Their device has instructions in it to launch a war event at a certain date and time. One hour after war starts, they cancel war and then an hour after that, they relaunch it. Now let’s say that person who logged in six hours before war started hasn’t been logged in yet. Their device doesn’t know about the cancel and relaunch, and it could take up to 20 minutes after they login for that information to get downloaded to their phone. When they login, before they get the instructions from the server that the war event has been canceled, their device starts the war event that was previously loaded in. They see the war splash screen and declare war, because as far as their device knows, the ORIGINAL war is still on. This is how we get into those messy situations where the server has 2 war queues going and some players in some factions can war and others can’t because there are 2 conflicting war events going on at the same time. It’s happened before, more than once.
The only safe way to cancel war and relaunch it is to cancel war and relaunch a war scheduled to start AFTER the originally scheduled war was scheduled to end. Why would you waste a weekend war for everyone because there are 32 1B regions out of ~250 total regions that will be affected? And it’s not like those 32 regions can’t war…they can, it’s just not an ideal configuration.
Sorry, 1B, I know it sucked, but they made the right call here.