handlers: campaign subsystem — mission list, battle lifecycle, and rewards - #39
Open
Seltraeh wants to merge 1 commit into
Open
handlers: campaign subsystem — mission list, battle lifecycle, and rewards#39Seltraeh wants to merge 1 commit into
Seltraeh wants to merge 1 commit into
Conversation
…wards Implements the campaign subsystem. CampaignStart opens the campaign and returns the mission list. CampaignMissionGet reports per-mission progress, CampaignDeckGet the party deck. CampaignBattleStart locks the deck and begins the battle; CampaignBattleEnd persists the clear flag, credits the archive-driven reward and unlocks the following mission id. CampaignReceipt claims rewards and CampaignEnd exits. AreaInfo is the entry point for the quest menu and FixGiftInfo acknowledges the gift inbox. Adds 25042026_CreateUserCampaignTables for user_campaign_missions, user_campaign_decks and user_campaign_state. UserInfo emits cleared-mission history from user_campaign_missions. This is the progression driver: the client evaluates feature unlocks against this list, so functions gated on "mission N cleared" stay locked without it. CampaignStart and CampaignReceipt still return minimal payloads pending MST-driven reward tables.
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
1 participant
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.
handlers: campaign subsystem — mission list, battle lifecycle, and rewards
Branch:
split/10-campaignBase:
devMerge position: 10 of 13
Nine handlers covering the campaign flow end to end.
What's included
CampaignStart6Y0gaPQNCampaignMissionGetRSm6p2d4CampaignDeckGetC3a0VnQKCampaignBattleStarth1RjcD3SCampaignBattleEndpTNB6yw3CampaignReceipt5Imq3wC0CampaignEndjF9Kkro4AreaInfoZds63G5yFixGiftInfogLRIn74vWhy cleared-mission history matters
It is the progression driver. The client evaluates feature unlocks against this list, so anything gated on "mission N cleared" stays locked without it. This is not cosmetic.
Known incomplete
CampaignStartandCampaignReceiptstill return minimal payloads pending MST-driven reward tables. Flagging now rather than letting you find it.Verification
Campaign menu opens with tiles; clearing a mission persists the flag and unlocks the next.