You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the powermark symbol is changed mid-game, the points shown in the ui will update accordingly, as well as the data in exported .qbj files. However, .json exports do not update.
Along with #255, a fix to this would be very helpful for tournaments that are using sets with nonstandard formatting.
note: the set used in these files uses [*] as the powermark (it's also cleared so dw)
The text was updated successfully, but these errors were encountered:
skysomorphic
changed the title
Changing powermark symbol retroactively change points in .qbj exports but not .json exports
Changing powermark symbol retroactively changes data in .qbj exports but not .json exports
Aug 5, 2024
The exact value in points isn't really used in GameState (which is what is serialized into the JSON file), we derive all the points from it. Right now it's used to check if something is correct or not (i.e. to make decisions if points > 0). See the comment in IBuzzMarker, which suggests changing the name to something like isCorrect:
The one place I see it possibly affecting things is in Cycle.orderedBuzzes, but that's only if you change the neg value, and changing the ordering here shouldn't affect anything:
I'm going to close this as Won't Fix for now. Tools should rely on the QBJ export, which is standardized and can be imported into other tools like Yellowfruit.
If the powermark symbol is changed mid-game, the points shown in the ui will update accordingly, as well as the data in exported .qbj files. However, .json exports do not update.
Along with #255, a fix to this would be very helpful for tournaments that are using sets with nonstandard formatting.
example
files before powermark change
files after powermark change
note: the set used in these files uses
[*]
as the powermark (it's also cleared so dw)The text was updated successfully, but these errors were encountered: