![Image](https://tgstation13.download/dip/discordimageproxy.php/attachments/385606030127661057/1239457962981068891/GNb_FUmXsAAM2cs.jpg?ex=6643a76e&is=664255ee&hm=a857928323e0d3d0305bf9925efa601e38b8d23a418c29cf15525ab75b8b42a0&)
if you're so curious: https://discord.com/channels/3268221442 ... 4708694119
Coder problem, not a me problem
MrStonedOne wrote:I always read dendy's walls of text
Relax and do what? Greenshifts in general aren't a good thing. We have antagonists for a reasondendydoom wrote: ↑Tue May 14, 2024 12:06 am you will never be able to convince me that greenshift announcements are a good thing. they aren't.
what kind of paranoia-laden roleplaying game starts its round with an announcement that there will be no paranoia today?
it sets unrealistic expectations that nothing should happen on both sides of the aisle: nothing should happen so i don't want to play vs nothing should happen so i better not see any excitement disturbing my bar rp.
don't tell the crew anything. if it's 45 minutes in and no antags, then you should relax but there should still be that "what if..." in the back of your mind. if that's gone completely then we're doing ourselves a disservice.
thehogshotgun wrote:How does having jannies like you, who have more brain tumor than brain benefit the server
greenshifts in general aren't a good thing but variance is.NoxVS wrote: ↑Tue May 14, 2024 1:00 amRelax and do what? Greenshifts in general aren't a good thing. We have antagonists for a reasondendydoom wrote: ↑Tue May 14, 2024 12:06 am you will never be able to convince me that greenshift announcements are a good thing. they aren't.
what kind of paranoia-laden roleplaying game starts its round with an announcement that there will be no paranoia today?
it sets unrealistic expectations that nothing should happen on both sides of the aisle: nothing should happen so i don't want to play vs nothing should happen so i better not see any excitement disturbing my bar rp.
don't tell the crew anything. if it's 45 minutes in and no antags, then you should relax but there should still be that "what if..." in the back of your mind. if that's gone completely then we're doing ourselves a disservice.
MrStonedOne wrote:I always read dendy's walls of text
@Head Admin Hey, why are admins allowed to nuke a perfectly good greenshift? What the fuck? This is supposed to be ROLEPLAY. And your fucking admins just come in and relying on a vote of like 15 people saying yes ruin it with highlands + 5000 ms of lag + making every wall a fucking SM.
Why the fuck is that allowed.
Interesting idea, do you think threat should have a minimum floor so there's never a round without antags? Seems like the easiest solution to greenshifts being bad.
kieth4 wrote: infrequently shitting yourself is fine imo
There is a lot of very bizarre nonsense being talked on this forum. I shall now remain silent and logoff until my points are vindicated.
Player who complainted over being killed for looting cap office wrote: ↑Sun Jul 30, 2023 1:33 am Hey there, I'm Virescent, the super evil person who made the stupid appeal and didn't think it through enough. Just came here to say: screech, retards. Screech and writhe like the worms you are. Your pathetic little cries will keep echoing around for a while before quietting down. There is one great outcome from this: I rised up the blood pressure of some of you shitheads and lowered your lifespan. I'm honestly tempted to do this more often just to see you screech and writhe more, but that wouldn't be cool of me. So come on haters, show me some more of your high blood pressure please.![]()
You just can't post... everEmpressMaia wrote: ↑Mon May 13, 2024 10:11 pm i made a admin feedbac about this does that mean i cant post here
The game is good when people do this, but some games take being punched less well than others.dendydoom wrote: ↑Tue May 14, 2024 1:42 amgreenshifts in general aren't a good thing but variance is.
changing things up regularly reminds us that this game is a roleplaying sandbox and is at its best when people approach different situations in different ways and explore/experiment with a wide variety of scenarios and themes.
when a greenshift is announced it cements those expectations. half the server quits because they don't expect anything to happen, and the other half get upset if anything does happen because they were "promised" a greenshift with the announcement.
keeping the crew in the dark sets no expectations and therefore doesn't cement any pre-determined "meta" or rote approach to a situation. in this state players just roll with the punches, adapting to whatever comes next and the game is really good when people are willing to do this.
that'll be my policy suggestion if I understand what dendy's getting at - axe threat reports entirely, every round starts green until raised in-roundkayozz wrote: ↑Tue May 14, 2024 10:00 pm I should add I have nothing against Greenshifts, but IMHO nobody should know they're Greenshifts. Keep that scary factor up.
(EDIT: Not sure how that would work with the star announcements?? [replace green star announcements with whatever one has the next lowest threat?])
Yours is a very empathetic position, and I respect it. I also respect the players that want to do their greenshift long-term projects, and all. I just personally think that when we have like, MUCH higher suicides on a greenshift than otherwise, it's a very evident fact that a lot of people don't like them. Even most long-term projects CAN be accomplished on a shift with antags, I just think it's a matter of doing all the rolling with the punches along the way. Dynamic makes that harder, often, but I also personally like that it's such a... Dynamic game. Y'know?
Mind me asking what the formula for raising it is though? My meagre understanding is that it's split between starting threat level (i.e star colour) vs time passed (i.e start/midround) vs casualties?Higgin wrote: ↑Tue May 14, 2024 10:06 pmthat'll be my policy suggestion if I understand what dendy's getting at - axe threat reports entirely, every round starts green until raised in-roundkayozz wrote: ↑Tue May 14, 2024 10:00 pm I should add I have nothing against Greenshifts, but IMHO nobody should know they're Greenshifts. Keep that scary factor up.
(EDIT: Not sure how that would work with the star announcements?? [replace green star announcements with whatever one has the next lowest threat?])
Make every shift start on a green report until the Captain has enough credits/ Research points to purchase the actual data? And then 'oh btw it's a black star'.
Threat Reports are also a really cool feature, I think. Maybe shifts like a Blue Star can leave it on Green Alert to start, since it's just information of enemy movements in the wider sector? We could reflavor it a bit to make more sense in the universe.
Maybe so - or the threat report range could be widened and the categories lessened so it's more of a "low/medium/high" threat advisory in which the low category can include greenshifts, or maybe even the medium category, in combination with considering what the random events controller is set at (since it's perfectly happy to throw in antags too.)DrAmazing343 wrote: ↑Tue May 14, 2024 10:10 pm[...]
Threat Reports are also a really cool feature, I think. Maybe shifts like a Blue Star can leave it on Green Alert to start, since it's just information of enemy movements in the wider sector? We could reflavor it a bit to make more sense in the universe.
That's also a cool idea - an IC way to augur the round a little bit and something for command to do (or not.)kayozz wrote: ↑Tue May 14, 2024 10:14 pm
Mind me asking what the formula for raising it is though? My meagre understanding is that it's split between starting threat level (i.e star colour) vs time passed (i.e start/midround) vs casualties?
I might be very wrong here.
I don't think axing reports is a good move, but Captain should be able to request such data for a price/cost.
Code: Select all
/// Generate the advisory level depending on the shown threat level.
/datum/controller/subsystem/dynamic/proc/generate_advisory_level()
var/advisory_string = ""
if (prob(PULSAR_REPORT_CHANCE))
if(HAS_TRAIT(SSstation, STATION_TRAIT_BANANIUM_SHIPMENTS))
advisory_string += "Advisory Level: <b>Clown Planet</b></center><BR>"
advisory_string += "Your sector's advisory level is Clown Planet! Our bike horns have picked up on a large bananium stash. Clowns show a large influx of clowns on your station. We highly advise you to slip any threats to keep Honkotrasen assets within the Banana Sector. The Department of Intelligence advises defending chemistry from any clowns that are trying to make baldium or space lube."
return advisory_string
advisory_string += "Advisory Level: <b>Pulsar Star</b></center><BR>"
advisory_string += "Your sector's advisory level is Pulsar Star. A large, unknown electromagnetic field has stormed through nearby surveillance equipment, causing major data loss. Partial data was recovered and showed no credible threats to Nanotrasen assets within the Spinward Sector; however, the Department of Intelligence advises maintaining high alert against potential threats due to the lack of complete data."
return advisory_string
switch(round(shown_threat))
if(0)
advisory_string += "Advisory Level: <b>White Dwarf</b></center><BR>"
advisory_string += "Your sector's advisory level is White Dwarf. Our surveillance has ruled out any and all potential threats known in our database, eliminating most risks to our assets in the Spinward Sector. We advise a lower level of security, alongside distributing resources on potential profit."
if(1 to 19)
var/show_core_territory = (GLOB.current_living_antags.len > 0)
if (prob(FAKE_GREENSHIFT_FORM_CHANCE))
show_core_territory = !show_core_territory
if (show_core_territory)
advisory_string += "Advisory Level: <b>Blue Star</b></center><BR>"
advisory_string += "Your sector's advisory level is Blue Star. At this threat advisory, the risk of attacks on Nanotrasen assets within the sector is minor but cannot be ruled out entirely. Remain vigilant."
else
advisory_string += "Advisory Level: <b>Green Star</b></center><BR>"
advisory_string += "Your sector's advisory level is Green Star. Surveillance information shows no credible threats to Nanotrasen assets within the Spinward Sector at this time. As always, the Department of Intelligence advises maintaining vigilance against potential threats, regardless of a lack of known threats."
if(20 to 39)
advisory_string += "Advisory Level: <b>Yellow Star</b></center><BR>"
advisory_string += "Your sector's advisory level is Yellow Star. Surveillance shows a credible risk of enemy attack against our assets in the Spinward Sector. We advise a heightened level of security alongside maintaining vigilance against potential threats."
if(40 to 65)
advisory_string += "Advisory Level: <b>Orange Star</b></center><BR>"
advisory_string += "Your sector's advisory level is Orange Star. Upon reviewing your sector's intelligence, the Department has determined that the risk of enemy activity is moderate to severe. At this advisory, we recommend maintaining a higher degree of security and reviewing red alert protocols with command and the crew."
if(66 to 79)
advisory_string += "Advisory Level: <b>Red Star</b></center><BR>"
advisory_string += "Your sector's advisory level is Red Star. The Department of Intelligence has decrypted Cybersun communications suggesting a high likelihood of attacks on Nanotrasen assets within the Spinward Sector. Stations in the region are advised to remain highly vigilant for signs of enemy activity and to be on high alert."
if(80 to 99)
advisory_string += "Advisory Level: <b>Black Orbit</b></center><BR>"
advisory_string += "Your sector's advisory level is Black Orbit. Your sector's local communications network is currently undergoing a blackout, and we are therefore unable to accurately judge enemy movements within the region. However, information passed to us by GDI suggests a high amount of enemy activity in the sector, indicative of an impending attack. Remain on high alert and vigilant against any other potential threats."
if(100)
advisory_string += "Advisory Level: <b>Midnight Sun</b></center><BR>"
advisory_string += "Your sector's advisory level is Midnight Sun. Credible information passed to us by GDI suggests that the Syndicate is preparing to mount a major concerted offensive on Nanotrasen assets in the Spinward Sector to cripple our foothold there. All stations should remain on high alert and prepared to defend themselves."
Code: Select all
/datum/controller/subsystem/dynamic/proc/setup_shown_threat()
if (prob(FAKE_REPORT_CHANCE))
shown_threat = rand(1, 100)
else
shown_threat = clamp(threat_level + rand(REPORT_NEG_DIVERGENCE, REPORT_POS_DIVERGENCE), 0, 100)
Code: Select all
var/greenshift = GLOB.dynamic_forced_extended || (threat_level < min_threat && shown_threat < min_threat) //if both shown and real threat are below any ruleset, its extended time
SSstation.generate_station_goals(greenshift ? INFINITY : CONFIG_GET(number/station_goal_budget))
MrStonedOne wrote:I always read dendy's walls of text
would it be better if they were more reliable in this case? you've got an 8% chance of it flat-out lying and random skew that can take it 30 pts. different from the true value - then an additional 15% of it handing you a low-threat fake greenshift if you somehow got a (real or fake) blue star (after the random skew, which could conceivably give you a fake greenshift at 34 threat)dendydoom wrote: ↑Tue May 14, 2024 10:43 pm thanks for the thoughtful replies. i'll have another essay to deploy but in the interim i'd like to say that i have no desire to stop roundstart threat reports.
i used to think that it might be nice to make the report lie more often, but i've since questioned this - i think it would lead to people just ignoring it outright and using it as an indicator of "threat report printed, i am now authorized to destroy antags" rather than actually reading it and taking the opportunity to use that information as a catalyst to create some sort of narrative for the round. i really like captains who will take the report and make actual announcements to the crew, delegate to command with this new knowledge of what the threat is going to be like, etc. if captains get used to the report lying way more often than not, then i think they'd view this sort of thing as a waste of time and stop doing it.
hmmm we're delving into code issuedendydoom wrote: ↑Tue May 14, 2024 10:43 pm thanks for the thoughtful replies. i'll have another essay to deploy but in the interim i'd like to say that i have no desire to stop roundstart threat reports.
i used to think that it might be nice to make the report lie more often, but i've since questioned this - i think it would lead to people just ignoring it outright and using it as an indicator of "threat report printed, i am now authorized to destroy antags" rather than actually reading it and taking the opportunity to use that information as a catalyst to create some sort of narrative for the round. i really like captains who will take the report and make actual announcements to the crew, delegate to command with this new knowledge of what the threat is going to be like, etc. if captains get used to the report lying way more often than not, then i think they'd view this sort of thing as a waste of time and stop doing it.
joooks wrote:Quoting a legend, at least im not a faggot lolNaloac wrote:
In short, this appeal is denied. Suck my nuts retard.
See you in 12 months unless you blacklist me for this
Timberpoes wrote: ↑ I'm going to admin timonk [...]. Fuck it, he's also now my second host vote if goof rejects.
pikeyeskey13 wrote: ↑ ok don't forget to shove it up your ass lmao oops u can delete this one I just wanted to make sure it went through
Agux909 wrote:Woah bravo there sir, post of the month you saved the thread. I feel overwhelmed by the echo of unlimited wisdom and usefulness sprouting from you post. Every Manuel player now feels embarrased to exist because of your much NEEDED wise words, you sure teached'em all, you genius, IQ lord.Timonk wrote:This is why we make fun of Manuel
Good, don't apologize for shit, your idea fucking rules. More specific but more inconsistent threat reports would kinda fucking rule- sometimes, even especially as that antag, I'd argue.
what if they announced it before the roundstart (and in big letters next to the join button if a late join) so that players that hate it have zero excuse to throw a fit ingame. a lot of people enjoy them, like knowing it's a good thing so they can do projects they aren't normally capable of, and base their rounds around that. in a game where people have finite time in their day it seems pretty reasonable to want to know if a threat is chiller than most so they don't feel like their time is wasted on things that take longer. usually we have a ton of green shift saboteurs that use excuses like "i wouldn't have gone medical or sec if i knew it was a green shift" or heads trying to speed shuttle call because they only play for sec.
i like doing this as cap but you have to quickly delete the threat report and burn the printed out papers because AIs have a nasty habit of announcing the starTheLoLSwat wrote: ↑Wed May 15, 2024 12:53 pm As captain I enjoy hiding the threat level from most of the crew because realistically only your security and 1-2 command staff should be aware of the danger, and everyone else should be on a need-to-know basis.
i put a picture of a possum in the op so you have to be nice to me
Users browsing this forum: Constellado, Riggle, WineAllWine