Hunger Games Simulation: Beyond the Possibilities

Bols◊, the safe male member of the Jaegers from Akame Ga Kill.

King Roland II◊, the safe male king of Enchancia from Sofia the First.

Couldn't come up with anything, so screw it, have some more Pokemon.

• Espurr◊ (Any Pronouns, Safe)

• Golduck◊ (Any Pronouns, Safe)

• Left Paddle◊
  • Source: Pong
  • Pronouns: Any
  • Flag: Safe

• Right Paddle◊
  • Source: Pong
  • Pronouns: Any
  • Flag: Safe

Edited by JankyKong on Sep 23rd 2023 at 6:48:28 AM

I'm curious on something: Would the hypothetical scenario where the RNG makes God a fictional character be okay for a save?

Cause I remember running an HGS simulation where Predator killed God by telling Him He doesn't exist. I believe in God, and I'd be fine with that.

Edited by CosmosAndChaos on Sep 23rd 2023 at 8:09:39 AM

Honestly, the only reason I used Imperative is because I couldn't find a good character to go with Exigent. The thing I was going for was that: what if the person who tagged along with Exigent had a plant parasite of some kind in their body, since Exigent is pretty much just a difficulty that got Reclaimed by Nature? A plant specifically, by the way. Unfortunately for my nonexistent brain located under a rock literally the only character I'm aware of that fits the description is a random Tumblr OC.

Edited by jtard on Sep 23rd 2023 at 9:17:50 AM

Vincent◊ (he/they)

Pechi◊ (any pronouns but most of the time is referred with she/her, 14-15-ish of age)

(ANTI-INCEST FLAG APPLIES SINCE THIS IS A FATHER AND A DAUGHTER)

Edited by SomeLibre on Sep 24th 2023 at 9:15:25 PM

That actually led to a debate in the server on whether or not deities from RL religions are considered Controversial Figures, but in the end, we decided to subject them to a case-by-case basis. That aside, I'm not offended at all with God or Satan being nominated, dying, or potentially being involved in that kind of event, even if I believe in them.

And kinda late, but nominations are closed. However, Reze shall be disqualified from this season for being nominated while her cooldown hasn't expired yet (she was last nominated in S292). supermario1096 can still keep Sturm because Enigma in the aforementioned season is a canon clone of him and thus considered fully separate from him.

EDIT: Event suggestions are also closed.

Edited by TroperNo9001 on Sep 25th 2023 at 2:18:35 AM

So has the running began yet? Just so I didn't get locked in.

Edited by jtard on Sep 24th 2023 at 9:49:16 AM

You can only run a season if you join the Discord server, unlike hosting

Edited by Billy5545 on Sep 25th 2023 at 12:31:40 AM

That's... not the point. The point is that I finally managed to come up with a good tribute alongside Exigent.

Edited by jtard on Sep 24th 2023 at 10:48:43 AM

That's not what they were asking

Ah, so you're going to swap out your second tribute for them? Is that what you meant? Because running hasn't started yet, so you still have time.

Yup. Anyways, here's my replacement:

ExileLord◊

• Source: Musical artist
• Pronouns: Male
• Flag: Said to be 17-18 around 2020, but Chartreuse (made that name up for yellow lime basically) just to be safe

Not only is this guy probably my #1 favorite artist (seriously, I can't stop listening to Soulless 5), but that dude in his PFP's green, AND Exigent and Exile both start with "exi".

Edited by jtard on Sep 25th 2023 at 9:40:06 AM

Actually, tributes who are "17-18" years old are usually flagged yellow-lime as they're right on the border between the two age groups.

Okay.

This probably won't come in all that handy, but in case you guys are wondering, here's the page for JJT on this website.

Edited by jtard on Sep 25th 2023 at 7:56:23 AM

Wait, you're a JToH fan too?

Epic, me too! Love that game!

I used to be active on JJT too but I left due to numerous toxic users and me getting hated on for using it in other games.

Edited by TheRealBerdly on Sep 26th 2023 at 3:08:50 PM

Holy shit!

Announcement

Over the past two months, we have been struggling with the glitch that prevents the Regular Save from being resimulated. We haven't found the true cause yet, but it is most likely because we have been constantly adding new events, and the sim inevitably became unable to handle all of them (despite there being no hard limit). We managed to do a few temporary workarounds by using the 3rd party Event Import/Export Tool to import all the events into a non-glitched save and quietly cutting some events^note specifically those where it's the same event but with the tribute names rearranged and the Phantom Tribute AEs due to them aging with Fan Myopia (but the latter is still up for debate on whether we should keep or remove them for good), but the production delays as a result have become a major issue.

We already reported the glitch multiple times to the BrantSteele staff, but until we're certain that it's fixed for good, we have no choice but to do any of these major changes:

1. Temporarily stop adding new events
2. Start removing a massive number of events according to criteria decided by the mods and/or community (e.g. snowclones, old events that no longer comply with the current event rules, partially removing events from specific sections (Bloodbath/Day/Night/Feast/Arena Events), etc.)
3. Do both of them

We understand that adding new events is one of the biggest appeals of this game, but like with the Reserve Era^note where everyone was guaranteed only 1 tribute, with their second tributes being added to a reserve list and then randomized to fill the much more limited tribute spots until we switched to the new sim, we think that these actions are necessary to speed up save production. With the diverse amount of events we already have, no two saves are ever the same, so it's never a dull moment in the Arena even if we do any of the suggested actions.

For the first action in particular, it may be upsetting for those who have huge event backlogs, especially since we don't know when the glitch will be fixed due to the BrantSteele staff being busy with managing other sims (but they have acknowledged our reports). On the plus side, these events can always be re-suggested when the glitch is finally fixed. Temporarily stopping new events also helps us prioritize fixing broken events and converting some events to the new sim formatting without having to deal with new ones in the meantime.

Other than that, we are open to other suggestions that you might have in order to resolve this long-term issue, and we hope that the glitch will be fixed soon.

Putting an halt on event suggestions until the glitch is fixed and removing snowclone events are fine by me.

My unfortunate takeaway here is that I don't know how much removing a smattering of snowcloned events is even going to do. If we consider every day and night event to be separate - which a computer would - then we have a total of well over fifty thousand events in our version of the simulator. I somehow doubt Brant coded the sim to be able to handle an event backlog of this magnitude, and whatever the "safe" number of events to have is - assuming that's the cause - I reckon we passed that number many thousands of events ago.

We can still try removing events here and there, of course. I'm just ready for it to turn out to not work.

I do admit that I have a large backlog of events, but temporarily not allowing until it gets fixed may be the best solution. As for removing events, I feel like they might be okay to remove some as long as there is a community consensus to removing those events (though it might be best to wait a couple of seasons where zero events end up getting added before we remove them).

At the very least, we should at least try to go with the plan of removing them/not adding new events. Plus, the clean save has not run into the re-sim glitch yet despite the amount of events that sim has, so going with this plan might work.

Edited by MummyGaGa on Sep 26th 2023 at 4:19:13 AM

I think 1 seems like a good idea.

3 sounds good

With what I've discussed in the server, I'm leaning more towards 3. Definitely try not adding anything more for a few seasons and possibly cut some old events too - we'll most likely need to cut something sooner or later anyway