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

Ash Walker flavor text modification #43463

Merged
merged 1 commit into from Apr 7, 2019
Merged

Ash Walker flavor text modification #43463

merged 1 commit into from Apr 7, 2019

Conversation

subject217
Copy link
Contributor

🆑
tweak: Ash Walkers have received a modification to their flavor text clarifying their intent to remain on lavaland and protect their nest.
/:cl:

Why:
Because Ash Walkers breaking into mining and rushing off to the station is boring, obnoxious, and only ever fun for the people doing it, usually at the expense of permanently ending several other people's rounds. Ghost roles are not your free respawn to reinvolve yourself in the round, and for a ghost role that is given pseudo antag status this is doubly true. The way I chose to phrase this isn't set in stone, I wanted something that has at least a little bit of flavor to it instead of blatantly just writing "DON'T GO TO THE STATION".

Tweak was just a guess on my part, I don't really feel like this is balance because it mostly concerns how ash walkers are administrated, wherein the primary rule is "Obey your flavor text." If someone bitches and moans about my choice in CL tags I'll change it.

@carshalash
Copy link
Contributor

If this goes through can ash walkers default clothes get a protection rating?

@Tlaltecuhtli
Copy link
Contributor

just make ashwalkers unable to use shuttle consoles

@Tlaltecuhtli
Copy link
Contributor

attack is the best defense as yugi would say so your flavour text is invalidated

@subject217
Copy link
Contributor Author

if someone tries to use that argument ingame i will ghost role ban them

@Poojawa
Copy link
Contributor

Poojawa commented Apr 2, 2019

you could give the Ashwalkers lungs that can't breathe station air mix, but just fine on Lavaland.

Locking out the consoles is a good option as well.

@subject217
Copy link
Contributor Author

When you code it. I've expended my effort on this and I don't see any valuable justification in seeking a different solution beyond "I personally disagree with the method that you have gone about this".

@Poojawa
Copy link
Contributor

Poojawa commented Apr 2, 2019

Citadel-Station-13/Citadel-Station-13#8159

@Tlaltecuhtli
Copy link
Contributor

uh oh subreddit217 now has to port stuff from citadel...

@HomocidlePancakes
Copy link

Oh boy. I guess Subject is PRing this because of that one round where ashliggers abused golem ship ruin and make mechs to murderbone. If you aren't allowing them on station, then you might aswell allow them to use PKAs so they can attempt fauna.

@Tlaltecuhtli
Copy link
Contributor

they can literally respawn from their dead bodies and every kill is + 1 respawn they dont need pkas just trow spears and respawn

@HomocidlePancakes
Copy link

HomocidlePancakes commented Apr 2, 2019

Lizzards were made unable to use guns as a code solution to station raids. Since we are enforcing this as a rule now, we should remove the code restriction.

@HomocidlePancakes
Copy link

Actually I just looked at the fluff. It says "Do not leave nest undefended". Leaves some room to still allow station raids. Is this intentional Subject?

@necromanceranne
Copy link
Contributor

Also thrown spears don't damage fauna. So they have to rely on numbers to kill anything in melee. Even then they don't have a lot of tools available to them at all.

@anconfuzedrock
Copy link
Contributor

Imagine being such massive fucking hugbox pussies that you need to add a rule through the code that lizards who can’t use guns and die to light tubes can’t attack the station, making lavaland, which is flawed for being detached from the main game, even MORE detached.

@VileBeggar
Copy link
Contributor

yeah i really love it when ashliggers invade the station and start bohbombing the shit out of it, it was a lot more funnier back when bohbombing meant singulo

@HomocidlePancakes
Copy link

Megafauna can be damaged by spears and it doesn't aggro them. But you need 100 spears to kil so...

@Daxxed
Copy link

Daxxed commented Apr 2, 2019

Just because I as ashwalker will not be allowed on station doesnt mean I cant send bubblegum there.

@ExcessiveUseOfCobblestone
Copy link
Contributor

Is the issue that they're killing people on station with little regard in bringing them back or that they're killing people on station and bringing them back, aka gibbing them?

Seems like the latter should be encouraged.

@HomocidlePancakes
Copy link

HomocidlePancakes commented Apr 2, 2019

It's hard to encourage ashwalkers to bring back their kills from station unless we make that a policy. You can already farm eggs relativly easy with tendrills. You can make simplemobs give it alot more less progress for next egg and give alot for humans (not the legion tendrill skeletons though) and that might work.

@ExcessiveUseOfCobblestone
Copy link
Contributor

What do you mean a policy? It should be clear in their flavortext (if not already) that they should focus less on mindless murder and more on sacrificing to the tendylord.

They aren't true-antags, they're just permitted to kill FNR due to their flavortext. HoStIlE FaCtIoN.

@HomocidlePancakes
Copy link

HomocidlePancakes commented Apr 2, 2019

I mean make "bring back kills" an actual rule. But thats silly and I doubt anyone will enforce it. Your average ashligger will almost never bring kills for tendrill because it doesn't benefit him in any way. We could make bringing humans that were player-controlled provide MINOR buffs and that will encourage people to get kills back

@ExcessiveUseOfCobblestone
Copy link
Contributor

Or we could just tell people if they want to murderbone to roll antag on the other server rather than taking up a ghostrole.

Not that I have an issue with making humans more valuable to sacrifice to have a mechanical incentive, just not a big fan of the implication that if you have to do the bare minimum in fitting with the role then it isn't fun anymore.

@HomocidlePancakes
Copy link

Admins will not ban you from lavaland for not filling the "bare minimum" as an ashwalker because it doesn't really exist.

New fluff has a rather large loophole. "Don't leave your nest undefended". It prevents solo ashwalkers from going on station, but it won't prevent full on raids. Just ask someone to stay at nest and blam. If they AFK/die/fuck off it won't be your fault for leaving it undefended.

@Tlaltecuhtli
Copy link
Contributor

@ExcessiveUseOfCobblestone problem is sometimes bored ghosts on 40min+ round see the ashliz spawn and go pretty much grief aka they go boh bomb or plasma flood or get mechs to kill the crew with or valid hunt instead of acting like tribals

@4dplanner
Copy link
Contributor

If the problem is ash walkers abusing high tech, would it not be better to target that? Genuine tribal invasions are pretty fun all round imo

@HomocidlePancakes
Copy link

Yes 4d. Thats the best solution for this. buuuuuuuuuuuuuuuuuut subject is a lazy nerd and here is what he said about this suggestion

When you code it. I've expended my effort on this and I don't see any valuable justification in seeking a different solution beyond "I personally disagree with the method that you have gone about this".
When you code it
When you code it
When you code it

If you aren't going to fix it properly Subject, then why do you even bother?

@4dplanner
Copy link
Contributor

lazy

And yet subject makes attempts to fix the problem while you just moan on his PR.

@HomocidlePancakes
Copy link

Gonna use "I can't code" but it's not really an argument.

@subject217
Copy link
Contributor Author

fun for a few validhunters =/= fun for the crew

@ATH1909
Copy link
Contributor

ATH1909 commented Apr 2, 2019

Again, what is wrong/bad about ash lizards invading the station? They usually only do so if there are a bunch of bored ghosts, which usually means that the round has gone on for too long/is boring people- which are problems that an ash lizard invasion of the station can fix.

@knacker48
Copy link

Ash lizards are such a non threat that It baffles me that anyone would have a problem with them. If there's even one person in cargo when they try to enter the station they're screwed because A) they don't have access to anything unless they somehow manged to kill a miner and B) The most they can do is chuck spears and fail to avoid stepping broken glass. Any sec officer can deal with more on a daily basis

@Teepeepee
Copy link

just throw glass shards how is this an issue lmao

@optimumtact
Copy link
Member

thog laugh at angry ashlizards in comments

thog probably merge this

thog threaten ashlizards with real code solution if they not play ball

@Repukan

This comment was marked as off-topic.

@FloranOtten
Copy link
Contributor

FloranOtten commented Apr 5, 2019

Honestly, I'd prefer a code solution. Maybe something that prevents them breathing station air due to pressure.

Does this even need fixing though? One of the greatest things I've seen in spess was an ash ligger disguising themselves as a station person and trying to blend in, failing horribly.

@subject217
Copy link
Contributor Author

Waiting for you to PR your code solution

Making them unable to use shuttle consoles is a better code solution btw

@zxaber
Copy link
Contributor

zxaber commented Apr 5, 2019

Is the issue the fact that ash lizards are given full antag rights, or that they get multiple spawns? Because I'd totally code a limiter that prevents someone taking a second egg if it meant this fluff change wouldn't be needed.

@linked7
Copy link

linked7 commented Apr 5, 2019

why are you changing rules through code

@subject217
Copy link
Contributor Author

subject217 commented Apr 5, 2019

@zxaber both, but it's mostly how ash lizards use those privileges more than that they have them.
@habader because the rules are that these thingies in the code determine what you're allowed to do, and this doesn't particularly bother me outside of isolated incidents where I think the flavor texts do not do a good enough job, with this being the primary one. nobody is getting banned the moment this gets merged, just like nobody got banned from the derelict drone flavor text change.

@Fikou
Copy link
Member

Fikou commented Apr 5, 2019

give them lavaland syndie rules so they cant leave lavaland unless someone destroys the tendril

@Daxxed
Copy link

Daxxed commented Apr 5, 2019

I think a flavour text this vague would allow admins to ban whoever they wanted.
A code solution is always better.
My preference would be to keep the station vs ashwalker war but maybe contain it on lavaland.
For example prevent ashwalker species on the shuttle, once the console is destroyed a 15 minute timer starts for the station crew to rebuild it, if they fail the ashwalkers win.
Golems could also do without the ability to build a teleporter.

Just my 5 cents after 100s of hours as miner and like 20+ of each ghostrole

@ExcessiveUseOfCobblestone
Copy link
Contributor

one day ill replace golems... one day...

@subject217
Copy link
Contributor Author

subject217 commented Apr 5, 2019

nobody is going to get banned for walking away from their base, pure fear mongering lmao

there is a world of difference between running around everywhere on lavaland and flying to a fucking space station

edit: admins don't get some sort of gratification from banning people, if someone isn't causing trouble there's no reason to ban them and if ashwalkers aren't excessively reinvolving themselves in the round as a guaranteed antag they can do what they want to.

@Tlaltecuhtli
Copy link
Contributor

people without contributor tag arent real

@FantasticFwoosh
Copy link
Contributor

FantasticFwoosh commented Apr 6, 2019

(A)subject217 Ghost roles are not your free respawn to reinvolve yourself in the round, and for a ghost role that is given pseudo antag status this is doubly true.

I won't dwell, but for many non-antagonistic ruin spawns like the Animal Hospital particularly as Stranded-Hermit++, this is the only resounding objective they have for people to choose them for reintegration with the crew as a fresh individual without checks or bureaucracy records; for clarification with your viewpoint.

They don't have anything interesting to do besides existing and emigrating in which unlike the Hermit they already have some resources negating challenge and mostly contribute to wasting ruin-generation budget with size rather than complexity.

(B)Daxxed I think a flavour text this vague would allow admins to ban whoever they wanted.

Nah, Citadel's planet habiting solution directly stated in server rules is a lot more hard by comparison but serves a effective barrier without much gameplay change.

@subject217
Copy link
Contributor Author

That's a code issue, Fwoosh. Ghost roles are by and large not meant to immediately reinvolve themselves in the round, that doesn't mean that players are suddenly entitled to free respawns because the roles suck and that's all they're good for.

@imsxz
Copy link
Contributor

imsxz commented Apr 7, 2019

if anyone who really cares wants an alternate solution idea: make ashliggers degrade when theyre off the z level for lore reasons, have the gubbuck milk halt the process so that they have to sac corpses and wait for gubbucks to produce milk to be able to venture on station safely

@SpaceManiac
Copy link
Contributor

this is the bikesheddingest PR of all time

@knacker48
Copy link

@imsxz aren't gubbucks still broken so that they don't produce milk, which is because the corpses dragged to the tendril don't explode into gibs so the gubbucks can't eat

@Tlaltecuhtli
Copy link
Contributor

@imsxz cool coding fix: they need co2 to breath

@subject217
Copy link
Contributor Author

it's called administration spacemaniac you should try it sometime

@optimumtact optimumtact merged commit c013c37 into tgstation:master Apr 7, 2019
ghost referenced this pull request in HippieStation/HippieStationdeprecated2020 Apr 7, 2019
Ash Walker flavor text modification
@subject217 subject217 deleted the ashwalker branch April 10, 2019 07:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet