Campaign Lua functions for branching#7298
Open
MjnMixael wants to merge 2 commits intoscp-fs2open:masterfrom
Open
Campaign Lua functions for branching#7298MjnMixael wants to merge 2 commits intoscp-fs2open:masterfrom
MjnMixael wants to merge 2 commits intoscp-fs2open:masterfrom
Conversation
MjnMixael
added
the
Requested by Active Mod
wookieejedi
added
enhancement
MjnMixael
force-pushed
the
campaign_lua_methods
branch
from
076915e to
18172a5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
BtA3 will have full campaign branching powered by a custom UI that lives outside of the mission environment. This PR provides the necessary methods to make that work.
First it provides a way to use ca.jumpToMission without mucking up the loadout in the campaign. Easy, simple boolean pass that preserves standard behavior.
Second there is a new method, ca:getValidNextMissions(), that walks the mission formula from the current position and returns a table of mission files names whose formula returns true. Standard behavior in FSO with a branch setup like this is to proceed to the first mission whose formula returns true. The rest are ignored.
With these in place, BtA3 can write the branching directly into the campaign file and access the list of valid next missions through Lua. With that we can build a UI and let the player select which mission they want. Then we can use ca.jumpToMission() to take them there with no side effects.