Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore stability waila info for black hole #3803

Merged
merged 2 commits into from
Jan 13, 2025
Merged

Conversation

FourIsTheNumber
Copy link
Contributor

This was a bad change that makes the multi unwieldy and confusing, as well as much more irritating to automate. Players should be able to visualize how it works and I do not believe it being inconsistent with tricorder is a meaningful issue.

@FourIsTheNumber FourIsTheNumber added the enhancement Improve an existing mechanic. Please explain the change with a before/after comparison. label Jan 13, 2025
Copy link
Member

@serenibyss serenibyss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discussed in discord - lets also add a stabilizing hatch or similar (gated UXV or so) to solve the automation as part of this PR

@boubou19
Copy link
Member

The idea was to hide stability info so you have to compute it yourself, avoiding the feeling that the game is frustating because it shows you the info but you'd have had no way to compute it "easily". It was a mistake apparently. So now we must add something to solve the puzzle easily a bit later, to reduce the frustration.

@FourIsTheNumber
Copy link
Contributor Author

It was always my intention to add a permanent stabilizer if black hole ever needed to be spammed to reduce the tedium of repeating the same automation and to minimize risks over a larger system. I do not think this is necessary in the current state of the game and I think it would be taking away from the current “meta” which uses a few different automation setups in lategame for different variants of universal or passive.

I am happy to code in the stabilizer but I don’t really think it should be obtainable in the current state of the game.

@boubou19
Copy link
Member

You can just gate it a bit later so people have to actually auto it once like intended, then they can unlock the stabilizer later. It's not necessarily a bad thing, and we handle the player frustration early, in case we start to resort on the black hole. Basically i want to anticipate the future with this.

@FourIsTheNumber
Copy link
Contributor Author

You can just gate it a bit later so people have to actually auto it once like intended, then they can unlock the stabilizer later. It's not necessarily a bad thing, and we handle the player frustration early, in case we start to resort on the black hole. Basically i want to anticipate the future with this.

No. Current critical recipes used specifically for stargate are designed around the mechanics of black hole and its spacetime usage. There is absolutely zero need for such a thing at the current moment and it would break a bunch of existing design work and dumb down the final challenges at the end of the pack. Permanent stabilization is absolutely something I have always been open to in the future, when the limits of the multi have been pushed and there is more content in the lategame, it does not make sense here.

I do not appreciate this small change that makes debugging your setup not completely miserable being held hostage over a nonsense unrelated change. I will add a stability seed if that’s what it takes, because I am a pushover, but it cannot be obtainable right now.

@FourIsTheNumber
Copy link
Contributor Author

FourIsTheNumber commented Jan 13, 2025

Or you can close the pr and just keep the user experience terrible if you’d prefer and are desperate to prove a point.

@boubou19
Copy link
Member

boubou19 commented Jan 13, 2025

No. Current critical recipes used specifically for stargate are designed around the mechanics of black hole and its spacetime usage. There is absolutely zero need for such a thing at the current moment and it would break a bunch of existing design work and dumb down the final challenges at the end of the pack. Permanent stabilization is absolutely something I have always been open to in the future, when the limits of the multi have been pushed and there is more content in the lategame, it does not make sense here.

Not for now, but you'd be surprised of the amount of time i heard this argument. And this is relevant to add just for creative testing at least. So we need it.

I do not appreciate this small change that makes debugging your setup not completely miserable being held hostage over a nonsense unrelated change. I will add a stability seed if that’s what it takes, because I am a pushover, but it cannot be obtainable right now.

I do not appreciate that you are trying to enforce frustration for players who don't care about puzzle solving aspect of the game. I get that it's your multi and all, but you have to acknowledge that not everyone is interested in puzzle solving, and that we have to also cover for our users who hate this kind of stuff. Having the game telling you to fuck off because of this one particular thing you hate in the game and not being able to bypass it is very not fun and it's sad to have a run killer this close to the goal. I'm not saying it should be directly availiable, i'm saying it should be availiable with a downside, probably the cost, so people will pay for their comfort.

Now i'd rather have you to add it because you know best the automation and all, so you should be able to properly add it to the game.

@FourIsTheNumber
Copy link
Contributor Author

And this is relevant to add just for creative testing at least. So we need it.

Sure. I already said I’ll add it but don’t think it should be obtainable.

I do not appreciate that you are trying to enforce frustration for players who don't care about puzzle solving aspect of the game.

Not related to what I said at all, which is bad practice with prs. This is not related to the thing you want but you’re forcing me to do it to get this critical change through.

I get that it's your multi and all

I don’t care about this

but you have to acknowledge that not everyone is interested in puzzle solving, and that we have to also cover for our users who hate this kind of stuff.

We have tons of automation challenges in the game which you have praised in the past so this is incoherent

Having the game telling you to fuck off because of this one particular thing you hate in the game and not being able to bypass it is very not fun and it's sad to have a run killer this close to the goal.

Not a run killer, people who don’t care about solving things will look up guides as they have always done for the entire lifespan of gtnh and every other video game ever made

I'm not saying it should be directly availiable, i'm saying it should be availiable with a downside, probably the cost, so people will pay for their comfort.

If you want it to be higher tiered so that people have to use the original automation then it’s especially nonsensical because then they still have to… do the puzzle that you’re so concerned about. And if you don’t want it to be higher tiered, this is just ridiculous. Just kill the multi alongside waterline and whatever else has any automation mechanic.

@FourIsTheNumber
Copy link
Contributor Author

#3808

@serenibyss serenibyss enabled auto-merge (squash) January 13, 2025 22:53
@serenibyss serenibyss merged commit 4022009 into master Jan 13, 2025
5 checks passed
@serenibyss serenibyss deleted the revert-bhc-waila branch January 13, 2025 23:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improve an existing mechanic. Please explain the change with a before/after comparison.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants