just make a game go unranked if nl/nk is forced and make it grs to do these things on purpose in must lynch/act setups

GrossDude says

It's really easy to code something out of context. I work on a horribly designed application everyday where the simplest things require a ton of reworking.

Figuring out the logic for something like this is trivial, as you pointed out, putting it into an existing code base isn't.

I knew it. I even said so in my post.

This community is full of edgy teenagers that are completely against ANY sort of improvement to the game. How can implementing the code into already-existent code be any difficult if you already have the logic done? The system is literally already done and functional, you just need to adapt it a little.

And Togepi, if you can't even figure out the syntax, then you shouldn't comment on it.

ok I won't change the code

Hydra says

c++

But no that's not the issue, no one ever asked you to change the code. I'm well aware it won't be changed. Make it a violation.

GrossDude says

It's really easy to code something out of context. I work on a horribly designed application everyday where the simplest things require a ton of reworking.

Figuring out the logic for something like this is trivial, as you pointed out, putting it into an existing code base isn't.

in this case it's far easier to append to existing code

simply add a condition before prompting for kick where if votes are tied and it's must lynch, don't prompt to kick. not just simple to say, but simple to do as well.

c++

It seems like all of the mods support this, so can someone explain to me what the problem is in re implementing it? Just throw it under copied mechanics. As it stand must lynch is literally nothing.

Good effort though

yeah, pseudo code won't take you very far

I can't get past the syntax. And you're right, it is useless.

I don't know, I didn't even read it, I assume the logic is good, but like I said, it's ultimately useless.

Wtf is that code?

It's really easy to code something out of context. I work on a horribly designed application everyday where the simplest things require a ton of reworking.

Figuring out the logic for something like this is trivial, as you pointed out, putting it into an existing code base isn't.

The easiest way to fix the code is that, if the votes are kicked while in a draw and the timer reaches zero, just make a random person between the draw get lynched. For example, if the lynch is stuck between player A and player B, there's a 50% chance of A getting lynched and a 50% chance of B getting lynched. If the lynch is between No Lynch and Player A, then the lynch goes 100% to Player A.

It would take less than one day to add that functionality to the code. Problem is, this community for some reason hates to see the game being improved and want it to go stale, so most people will opposite to this with reasons like "N-No, you expect the admins to work on this game? Have you lost your mind?? OMFG!" or "No I like the way it is because I can cheat".

The code would be basically:

int playerAVotes = 3; // this changes with the game obviously
int playerBVotes = 3;
int playerCVotes = 2;
int playerCount = 3;
int noLynchVotes = 0;
int timer = 0;
boolean isKicked = true;

if (timer == 0 && isKicked == true)
{
if (playerAVotes > playerBVotes) {
if (playerAVotes > playerCVotes) {
lynch(playerA);
}
}
else if (playerBVotes > playerCVotes) {
lynch(playerB);
}
else if (playerCVotes > playerAVotes) {
lynch(playerC);
}
else if (playerAVotes == playerBVotes) {
if (playerAVotes == playerCVotes) {
var randomPlayer = math.Random() * playerCount;
randomPlayer = randomPlayer.mathFloor();
if (randomPlayer == 1) {lynch(playerA)} else if 2, lynch playerB, and so on...
}
else if (playerAVotes > playerCVotes) {
(random thing, except for only with A and B)
}
(repeat random stuff with B and C, and A and C)
}
}

There is obviously a way easier way to do this, but this code is adapted to work with anything. If even I can figure out the code, surely this website's programmers can too?

just make the game go unranked if nl is forced in a must lynch setup

Well lets make it a rule then.

Comment. Comment. Delete.
-giga

Giga13 says

Agreed 100% at OP same with Must Act and forcing NK; I was arguing this in mod forums a couple months ago

But its not a rule. And just because you are against it doesnt mean you can report people for it. Just as i had my own meteor strategy that you also dont agree with. Just because you dont agree with it doesnt make it illega . So repeal the violation you gave me. It was uncalled for and only done so you could fulfil your own agenda.

Easy fix: if options are tied at hammer in a must-lynch setup, choose the one with the most town members voting for it as winner

Forcing no-lynch is a scum and 3p tactic to eek wins, not a town tactic. Remove the reward to attempt the tactic and people won't try it.

Agreed 100% at OP same with Must Act and forcing NK; I was arguing this in mod forums a couple months ago

well yeah, forcing NL on must lynch should be impossible, and there's no way for the game to differentiate between a mafia blitz and a town force

Hibiki says

if votes are kicked and the kick-timer hits zero, the game should reset the kicks and day-timer to 1 minutes and unlock the votes. if the votes unlock 3 times in one day, meteor strikes

uhh, even if its only for must act games, it still prevents mafia from blitzing a nl on lylo if the opportunity arises since the votes would unlock if the nl gets forced.

only on must lynch games, obviously

Hibiki says

if votes are kicked and the kick-timer hits zero, the game should reset the kicks and day-timer to 1 minutes and unlock the votes. if the votes unlock 3 times in one day, meteor strikes

very stupid and takes away from the excitement u get out of the game when you have to make a quick decision. would also stall a lot of 3ways unnecessarily