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
showError("The scenario editor cannot launch an unpacked scenario directly. You'll need to re-open the scenario from its .boes archive.");
- This might be somewhat hard
Pack and copy replay test scenarios into debug builds
- I don't want to have to do this for Visual Studio and Xcode builds.
- The code will need to change to search for scenarios in the build folder that are not VoDT, ASR, or ZKR
The text was updated successfully, but these errors were encountered:
NQNStudios
added
bug
game
Affects the game, as opposed to the editors
meta
Related to the build system or other things other than the code
replay
Affects the replay system
and removed
game
Affects the game, as opposed to the editors
labels
Feb 14, 2025
The way we're staging new-format scenarios in the repository is in conflict with the format the game needs scenarios to be in to launch them.
Possible fixes (each with drawbacks) include:
+
Easy change to make-
The unpacked folder appears as a non-functional duplicate entry in the scenario picker.-
Not DRY: The test scenario will need to be re-packed/re-unpacked anytime it changes. It should only exist in the repo in one form.+
this will help fix a pesky limitation of the scenario editor's launch feature:cboe/src/scenedit/scen.main.cpp
Line 106 in 3bd8874
-
This might be somewhat hard-
I don't want to have to do this for Visual Studio and Xcode builds.-
The code will need to change to search for scenarios in the build folder that are not VoDT, ASR, or ZKRThe text was updated successfully, but these errors were encountered: