Without fully giving it away because I thought it was super near. The button was what I felt ‘squid games’ based.
I know there was a coin also found by Rime; Im 95% sure what it did - Heads or Tails.
The button was my favorite hook in the tourney. Though I don’t think that full story is mine to tell. What I’m willing to tell about the Button was pretty well detailed throughout the crystal viewer.
I do however enjoy an element of mystery within my storylines to persist for a long time. I don’t think I’m going to comment on ‘the coin’. We’ll see it again some day.
1 Like
Though I don’t think that full story is mine to tell. What I’m willing to tell about the Button was pretty well detailed throughout the crystal viewer.
Something neato about this: typically when a player used a particular roleplay that did something to the effect of killing the cameras, or avoided something like letting a particular shady event be televised… these requests/events were respected.
Some players picked up on this. And employed it beautifully. Good job.
2 Likes
The issuing challenges thing was a little interesting. As I understand it now, a player would attack which would essentially be the challenge. If the opponent put up a defense, the battle was on, but if the player left the platform instead no battle took place. Is that right?
Attacking and challenging were synonymous. Basically, anything to trigger combat.
There would become this meta when players move late in the day, and send their email as close to the cutoff time as possible. As every player was uncertain if the other had expended their move yet, or would plan on moving.
The challenge mechanic wasn’t supposed to exist…The challenges thing… Truth is, was something I did not intend to have. It was a means to bridge a technology gap.We knew we wanted to do some form of movement within the website. PMCS to facilitate combat (normally communicated in real time through Discord).
In a perfect world, email wouldn’t of been involved at all in the tournament. But we had time limitations.
So what was done is as soon as we got an email, we communicated the challenge request to the opponents involved as soon as we got it. It worked out well, mostly because I was watching for these requests like a hawk - they were communicated to involved players almost instantly.
If they accepted the fight, we’d go to initiative rolls (first strike is super important to PM). If they chose not to accept the fight by moving after being challenged, or simply refuse… we’d roll.
If a challenge was successfully avoided, the fighter who initiated it was given a minor heal.
Thankfully, all of these mechanics worked extremely well because all fighters were willing to roleplay through a lot of the minutia.
Funny enough, no avoidance rolls were ever needed. Through roleplay, challenge avoidance were actually accepted by the challengers. Though I do suspect some meta conversations.
First Strike and turn order were handled this way:
—Challenger Dante rolled a d20. Take the result (17).
—The Challenged Virgil rolled d20. Take the result (9).
Turn order: Dante, Virgil.
Sometimes a fighter occupied the same space/platform, having not moved. But was challenged. Was given a bonus for not having moved within the recent movement windows.
— Challenger Dante rolled a d20. Take the result (8)
— The Challenged Virgil rolled a 2d20. Take the highest result (6 or 9, resulting in 9)
Turn order: Virgil, Dante.
Fighters often requested to do some sort of action within the challenge, like a surprise attack or pre-fight buff. The chances of success were slim, d20… gotta roll 15 or better. Limited to 1 thing. Most failed, except for the Jungle…where these chances were buffed/flipped.
It wasn’t the ideal system, but it is what we used within the time constraints. I wouldn’t suggest using it again, because this was flawed. The time situation might work out very differently in the future.
I’d rather the website to of handled everything, and we had no email. Fights initiated from the character page, and area descriptions are delivered from there as well. Most of the challenge thing was handled out of necessity, and close monitoring of email to ensure timelines didn’t get screwy.
1 Like