feat: finishInvasionsInOneMission #2715

Merged
Sainan merged 12 commits from AlexisinGit/SpaceNinjaServerAlexFork:finishOneInvasionFinishTheWholeThing into main 2025-08-29 17:36:12 -07:00
Contributor
#2646
AlexisinGit added 2 commits 2025-08-28 03:25:29 -07:00
AlexisinGit added 1 commit 2025-08-28 03:39:55 -07:00
Cheat: finish One Invasion Finish The Whole Thing code style consistency change
All checks were successful
Build / build (pull_request) Successful in 1m36s
84e8d646db
Owner

This seems incomplete as you e.g. did not update the webui translation files to add your new string.

This seems incomplete as you e.g. did not update the webui translation files to add your new string.
Sainan changed title from Cheat: finish One Invasion Finish The Whole Thing to WIP: Cheat: finish One Invasion Finish The Whole Thing 2025-08-28 04:08:39 -07:00
Author
Contributor

should i leave an empty string or?

should i leave an empty string or?
AlexisinGit added 1 commit 2025-08-28 04:44:49 -07:00
Cheat: finish One Invasion Finish The Whole Thing translation
Some checks failed
Build / build (pull_request) Failing after 1m12s
8c2a4f40a1
Contributor

should i leave an empty string or?

No. Also DO NOT use AI translation in languages you are not familiar in. Use the [UNTRANSLATED] thingy instead, for non-english strings.

> should i leave an empty string or? No. Also DO NOT use AI translation in languages you are not familiar in. Use the `[UNTRANSLATED]` thingy instead, for non-english strings.
AlexisinGit added 1 commit 2025-08-28 04:50:40 -07:00
Cheat: translation js style consistency change
Some checks failed
Build / build (pull_request) Failing after 1m10s
7a9f772714
AlexisinGit added 1 commit 2025-08-28 04:54:42 -07:00
Cheat: translation js style consistency change (2)
All checks were successful
Build / build (pull_request) Successful in 1m6s
e7f7586f11
Author
Contributor

welp, this should work now.

welp, this should work now.
Owner

Please use the update-translations script to properly populate the non-en files.

Please use the update-translations script to properly populate the non-en files.
Sainan added 1 commit 2025-08-28 05:45:27 -07:00
boop
Some checks failed
Build / build (pull_request) Failing after 2m19s
b40a2a0f2b
AlexisinGit added 1 commit 2025-08-28 07:57:16 -07:00
non-en files by update-translations script
Some checks failed
Build / build (pull_request) Failing after 12m13s
42cd695d9f
AlexisinGit added 1 commit 2025-08-28 08:10:22 -07:00
Merge remote-tracking branch 'upstream/main' into finishOneInvasionFinishTheWholeThing
All checks were successful
Build / build (pull_request) Successful in 1m14s
219f04362b
Author
Contributor

I didn't realize we have such tool. Is there anything else I should be paying attention to?

I didn't realize we have such tool. Is there anything else I should be paying attention to?
Owner

I mean, I question the quality of this contribution more than anything.

  • Why is this a server-wide setting?
  • Why is this a toggle instead of a multiplier?
I mean, I question the quality of this contribution more than anything. - Why is this a server-wide setting? - Why is this a toggle instead of a multiplier?
Contributor

I mean, I question the quality of this contribution more than anything.

  • Why is this a server-wide setting?
  • Why is this a toggle instead of a multiplier?

Is... there a reason to make it a multiplier? Invasions are always "complete at least 3 more missions for one side than the other", they're not variable, you don't get bigger rewards for doing more than 3 missions, and multiplying by 2 ends up quite awkward.

> I mean, I question the quality of this contribution more than anything. > - Why is this a server-wide setting? > - Why is this a toggle instead of a multiplier? Is... there a reason to make it a multiplier? Invasions are always "complete at least 3 more missions for one side than the other", they're not variable, you don't get bigger rewards for doing more than 3 missions, and multiplying by 2 ends up quite awkward.
Owner

Well, the name of this option is quite awkward compared to e.g. "Invasion Progress Multiplier". And the implementation is a multiplier anyway, so could give the user more flexibility.

Well, the name of this option is quite awkward compared to e.g. "Invasion Progress Multiplier". And the implementation is a multiplier anyway, so could give the user more flexibility.
Contributor

"Finish Invasions in One Mission" would definitely be less of a mouthful. And again I question the need for flexibility here. Having 0, 1 or 2 completed missions have the same end result of not qualifying for invasion pay. Having 3, 4, 5 or 99 all have the same end result of qualifying for invasion pay.

Plus since it's 3 invasions for pay, the only valid actual multipliers would be 1, 2 or 3, one of which is normal, one of which is instant completion, and the other is an extremely awkward middle ground I don't think users would actually care for if they're messing with faster invasion completions anyway.

"Finish Invasions in One Mission" would definitely be less of a mouthful. And again I question the need for flexibility here. Having 0, 1 or 2 completed missions have the same end result of not qualifying for invasion pay. Having 3, 4, 5 or 99 all have the same end result of qualifying for invasion pay. Plus since it's 3 invasions for pay, the only valid actual multipliers would be 1, 2 or 3, one of which is normal, one of which is instant completion, and the other is an extremely awkward middle ground I don't think users would actually care for if they're messing with faster invasion completions anyway.
Owner

I mean, users might want to have to do 2 invasion missions instead of 3 but not go all the way to 1 ?

I mean, users might want to have to do 2 invasion missions instead of 3 but not go all the way to 1 ?
Contributor

Would they really, though? Given the relatively small difference between doing 2 vs 3 missions, compared to doing 1 vs 3 missions, if a user is annoyed enough by invasions to want to speed them up, chances are they want the bigger skip, not just skipping out on a single mission.

Would they really, though? Given the relatively small difference between doing 2 vs 3 missions, compared to doing 1 vs 3 missions, if a user is annoyed enough by invasions to want to speed them up, chances are they want the bigger skip, not just skipping out on a single mission.
Author
Contributor

I'm still learning about account and server-wide cheats.

Meanwhile, I also don't think a multiplier would be the best idea. 0,1,2,3 is a lot more to comprehend than a toggle.

The issue is "finishing one invasion mission finishes it's whole thing" rather than "manipulate invasion score". I'm just making a cheat option that does the job. I don't think the name displayed on the UI needs to match its underlying logic, neither do users need to know how it is implemented.

I'm still learning about account and server-wide cheats. Meanwhile, I also don't think a multiplier would be the best idea. 0,1,2,3 is a lot more to comprehend than a toggle. The issue is "finishing one invasion mission finishes it's whole thing" rather than "manipulate invasion score". I'm just making a cheat option that does the job. I don't think the name displayed on the UI needs to match its underlying logic, neither do users need to know how it is implemented.
Author
Contributor

like... for "Invasion Progress Multiplier" i would not be knowing what it does.

but for "Finish Invasions in One Mission" i would know. Because it's what i want to do.

like... for "Invasion Progress Multiplier" i would not be knowing what it does. but for "Finish Invasions in One Mission" i would know. Because it's what i want to do.
AlexisinGit added 3 commits 2025-08-28 19:22:31 -07:00
Sainan changed title from WIP: Cheat: finish One Invasion Finish The Whole Thing to Cheat: finish One Invasion Finish The Whole Thing 2025-08-28 20:18:21 -07:00
Sainan approved these changes 2025-08-28 20:18:27 -07:00
Sainan changed title from Cheat: finish One Invasion Finish The Whole Thing to feat: finishInvasionsInOneMission 2025-08-28 20:18:40 -07:00
Sainan merged commit 9add016d7b into main 2025-08-29 17:36:12 -07:00
Sainan deleted branch finishOneInvasionFinishTheWholeThing 2025-08-29 17:36:12 -07:00
Sign in to join this conversation.
No description provided.