Capital Supremacy Game-State Glitch
Product: Star Wars Battlefront II
Platform:PC
What is your issue related to? General
Summarize your bug An edge case cascades into a whole waterfall of state driven bugs in new supremacy mode.
What is your gamertag/PSN ID/EA Account name? TotalDisdain
How often does the bug occur? Rarely (0% - 9%)
Can you tell us the date (MM/DD/YYYY) that you saw the bug? 04/08/2019
What time did you see the bug? (HH:MM AM/PM) 10:00 PM EST
In what game mode did the bug occur? Capital Supremacy
What is your time zone? EST (IET) - GMT - 5:30
Steps: How can we find the bug ourselves? Well, it looks like what started this was republic was attempting to complete the unlock doors portion on capital ship. They failed, and the droid announcer stated as such, I did not see anyone at either contested point, but someone on republic team said they got to the trigger "G" at or near 0. Looks like an edge condition.
What happens when the bug occurs? Instead of going to ground combat, the game went to second stage of capital ship, and replenished 50 units to republic. Droids stopped the attack. When the next round commenced on the ground, the CIS went directly to second phase of boarding the transports. after boarding, CIS failed to open the doors. Returning to ground combat, the republic started with 100 reinforcement points to CIS 0. They could not board transports even after achieveing 150+ reinforcement points. CIS finally acheived 50 points, then progressed to board transports. On capital ship, droids were able to open the doors, but failed to blow up the two objectives. Upon return to ground combat, the game appeared to continue properly.
What do you expect to see? It appears, that a bolean is used to share control of the sub-states of both ground and capital ship areas. The states should not be linked this way. The edge case needs to be addressed and properly handled. For some reason, an equal is used to signify that reinforcement should progress to boarding transports. It should be >= 50 instead. Each round should be properly initialized.
Please select your region North America
AMD or Nvidia Model Number
I don't think I could trigger this again if I tried.
