feat: Void Corruption 2025 #2865
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "Slayer55555/SpaceNinjaServer:void-alerts"
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?
It works™
But I'm unsure of the implementation of alerts, it's my first time doing actual changes to the database and doing stuff with typescript, so I'm putting WIP until someone checks it out.
Re #2842
@ -315,3 +315,3 @@FusionTreasures: IFusionTreasure[];//WebFlags: IWebFlags;CompletedAlerts: string[];CompletedAlerts?: string[];This field has been in all inventories for at least 20 months. Why are you making it optional?
npm run verifyfails if it's not optionalnpm run verifydoesn't fails because of thatnpm run lint:cifails because there is uselessinventory.CompletedAlerts ??= [];Ohhh, I will try to fix it later, thanks.
@ -115,0 +151,4 @@enemySpec: "/Lotus/Types/Game/EnemySpecs/CorpusShipEnemySpecs/CorpusShipSquadDefenseB",minEnemyLevel: 20,maxEnemyLevel: 25,maxWaveNum: 10After 38.5 they changed needed waves to complete one defense rotation. And after that, they use multiples of 3.
They did, but those are the original alerts, I can change it but it wouldn't be faithful tho.
There are also some anniversary alerts here that have the same amount of waves.
Yes, first week of 12 anniversary
/Lotus/Types/Keys/TacAlertKeyAnniversary2019E(March 7 - March 14), but there's a problem: 38.5 was released on March 19. And then in one of the hotfixes, they specifically updated/Lotus/Types/Keys/TacAlertKeyAnniversary2017B(second week)“maxWaveNum”: 10,->“maxWaveNum”: 6,WIP: feat: Void Corruption 2025to feat: Void Corruption 2025Why is this implemented as an "all in one" option? Officially, these 4 alerts ran discretely over different weekends. The game itself also doesn't display more than 3 alerts.
@ -1482,2 +1566,4 @@fullyStockBaro(vt);}if (config.worldState?.voidCorruption) {worldState.Alerts.push(...voidCorruptionAlerts.map(alert => structuredClone<IAlert>(alert)));There's really no reason to use
structuredClonehere. You can updateIWorldStateto also specifyreadonly IAlert[]for what little value it has.Honestly? Because it would be tedious to enable them one by one as you complete them, and if you forgot to enable the next when you got to the orbiter you'd need to enter a relay or reload the missions in some way to be able to play the next one. Also the game did display all 4 alerts when I tested it. If you want I can make them separete, I just see it as inconvenient.
Great stuff. I do think especially considering the gifts of the lotus stuff, alerts would be better implemented as something where you just enter a mission node + rewards in the webui and then submit it, maybe with some presets there. Afaict, the
levelOverride,enemySpec, etc. here are copied from the underlying node so just some export improvements could make this very redundant.I agree on the mission node and rewards stuff, but I think Void Corruption and the floof alerts are an exception, most if not all of the times gifts of the lotus are one of this list: (silver or gold potato, forma, umbra forma, exilus adapters, riven transmuters and riven ciphers), sometimes BPs sometimes built.
Wow they're so different, they rewards mods or shipdecos instead of miscitems!
Oh you mean create alerts to reward any item?
I like that idea, I thought you meant only the items that have been available in alerts. But I think at least for now this PR should work.
Anyway, for the sake of this PR, please do make it 4 separate toggles at least.
Do these dates look overlapping to you? https://www.warframe.com/news/void-corruption-alerts-2025
what?
Explain what your idea behind
0d394d4591was because to me that does not look like 4 different toggles.It's literally the same implementation as galleon of ghouls why should it be different?
I don't see galleon of ghouls using
.sliceanywhere, this is what makes your "week 4" option actually "week 1 + 2 + 3 + 4"fuck
Also, as you yourself said, it would be annoying to have to change the active alert after having completed one, so I don't see why you disagreed with the simpler and more flexible approach of 4 different toggles. Galleon of Ghouls does not have that luxury because the client doesn't take well to multiple goals having the same tag, but I don't think the same issue is present here.
Mainly because I tried and I can't make it look even decent, my skills in html are lacking at best, can you give me a hand?
You had a toggle before, you just had to copy that 3 times?
Wouldn't that make it too cluttered?
It's already quite cluttered