Disruption using the wrong rotations #2599
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, we use the AABC pattern here, which is obviously incorrect.
We'd need some mission logs from disruption runs so we can correlate the request data with the intended rotations.
Disruption does not follow the traditional 'AABC' rotation for endless missions. The reward tier is determined by both round progression and round performance, i.e. the number of conduits successfully defended.
Round 1 conduit defended 2 conduits defended 3 conduits defended 4 conduits defended
1 A A A B
2 A A B B
3 A B B C
4+ B B C C
5 waves completed, this should work
lol, wrong log. either way would not be useful without knowing how you performed in each round.
which log is it??
all waves with all conduits defended
Server log of course. Mission report
do you need it from live or from sns?
if live i have no idea where to get that
SNS of course
Just did 3-4-4 so A-B-C according to the matrix; it seems
rewardTierOverrides
is used to indicate this: