feat: tactical alerts #2607
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "AMelonInsideLemon/SpaceNinjaServer:goal-dog-days"
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?
Includes all
Tactical Alertssince Star Chart 3.0 with exception:Snowday ShowdownWolf Hunt (2019)(couldn't find correspondedEventNodefor that)Void Corruption(that's goes intoAlerts)All
Warframe's AnniversaryRe #1103
@ -76,2 +76,4 @@"plagueStarOverride": null,"starDaysOverride": null,"waterFightOverride": null,"waterFightRewardsOverride": null,I don't love the use of codenames in the config, as it's still meant to be somewhat user-facing.
Also a minor thing is that
RegularCreditsshould be deleted when transforming message database to client since that's definitely not a real field (the credit reward is likely not even given via the inbox message)If that not real field then why i see it on https://api.warframe.com/api/inbox.php?
Oh nvm, I guess I was looking at the wrong log.
feat: dog daysto feat: tactical alertsMerge conflict, could you please rebase
Sorry to bother you, but would you consider adding Thermia Fractures? Thank you so much.
72572f2c47to6b3aa11ec1Done
@ -1403,2 +1404,3 @@...staticWorldState,SyndicateMissions: [...staticWorldState.SyndicateMissions]SyndicateMissions: [...staticWorldState.SyndicateMissions],InGameMarket: staticWorldState.InGameMarketThis is not creating a copy, so every single request to the worldState endpoint where this array is mutated persists those changes.
Typo in comments (present in a couple of more places, than the screenshot).
Incompatible*Uhhh, should we maybe just have the year load from a |YEAR| value? Because otherwise we end up with that, having identical strings with different years, resulting into (probably-)pointless extra strings.