That's WAY too many categories. You gotta draw the line somewhere.
"I have World Record in Resident Evil 2 2019, New Game, Standard. Claire, A scenario, Glitchless, Variable, 120fps...."
This is insane.
I can't believe I'm hearing people make serious suggestions for banning knife in boss fights above locking FPS. It's honestly shocking to me. When there's zero good argument against locking FPS. Not one good argument, outside of "ew."
SLr, I don't necessarily disagree with you, but I think you may want to take a break from this site for a bit. Just for a breather. The way you're sending your message is not the most effective.
It's just a game, mate. It's gonna be okay.
I will take using Rivatuner to cap my FPS to 120 over simply allowing uncapped, or banning the knife in any respect.
It would be annoying and would probably turn people off of the game. (not me, but I'm sure at least one person would be like "I have to download what? fuck that") But it's a compromise I think a fair portion of people would be willing to make. It only affects those with 60hz monitors.
@kahuna That still doesn't make any sense. Why NOT use the knife on bosses? What an odd rule. If the knife was so broken that it killed every boss in one hit, no matter FPS, this discussion wouldn't even be happening. It might be considered a "glitched" run, but I think even that is a stretch.
Again, it's not about how OP the knife is. It's about how inconsistent the knife is depending on the power of your PC. And it's easily fixable by simply capping frame rate. Banning an entire weapon, even just against certain enemies, makes more sense than simply saying you can't run the game at a faster framerate than 120? Let's stay reasonable, here.
Banning a weapon is such a silly rule. It's in the game. It's not a special weapon. It's not a rocket launcher or a minigun... it's a knife! Ban the inconsistency, not the weapon.
I don't agree with that at all, personally.
EDIT: Hypothetically, let say this FPS damage correlation made every weapon, except Matilda, seriously OP. Would we ban every other weapon? Or just lock FPS? Banning the weapon makes no sense.
Livesplit is optional. SRT is optional. It's a REQUIRED third party program that's questionable.
I mean, I'll do it, if it's decided, and it works regardless of monitor. But REQUIRING a third party program to run a game is a bit sketchy.
Nothing is 100% ditched. That's an overreaction. Nothing is even 5% ditched. Bosses are what, 5% of the total run? Literally nothing is lost that's been gained so far, except maybe longer boss fights, regardless of what's decided. The route is identical, otherwise.
Yeah it's not about how broken the knife is. If it killed bosses super fast on any framerate, this wouldn't even be a discussion. provided it killed the bosses the same SPEED. It's about consistency.
Here's the simple thing; if we can change some settings to achieve cap at 120fps, fuck yeah. Sounds great. I agree that if we just need to sacrifice some graphical quality to run equally, then that's acceptable. But if I need to purchase a 144hz monitor just to run this game competitively AT ALL, that's fucked up.
Whatever the decision is, it needs to support any monitor the game is run on. I feel like that's common sense.
The point about monitors, Sabaka, is you can't CAP a monitor at 120 using vsync if your monitor only supports 60. It'll be variable, or locked at 60. Do I need to buy a 144hz monitor to run this game?
EDIT: If I can cap my framerate to 120 while using an 60hz monitor, without a third party program, I'm 100% for setting the cap to that.
The runs already done are irrelevant. The boards aren't even open yet. Doing runs before the boards are even open, and rules established, is just the risk people took. There is no reason they should expect those runs to be valid. And the practice isn't just trash. Just do it again, within the rules.
I'm not opposed to upping the limit from 60fps, but the runs already worked on should not be a factor. At all. And no cap to something that requires external program. Cap it at 144, or 60. Something the game can easily have set on it's own.
There's an OOB glitch already. Chances are more will be found. It's only been 6 days.
Also, FPS glitch aside, knifing bosses is probably STILL going to be the strat, even on 60fps. The knife is broken af.
Yeah I think displaying FPS for NMG is a given. There's absolutely no reason not to make it a requirement. I don't think you can play this game (legally) without Steam, and Steam has a built in FPS display. There's no excuse not to display your FPS.
100% in favour of locking FPS to 60. At the very least for glitchless.
I don't have a solid reason why this shouldn't be allowed for technical reasons, but from a preference point of view, if this technique was required in order to get WR, I'd stop running the game. Obnoxious and annoying strat that takes far more of my real life away in order to shave time off the IGT. You'll take a 2 hour run to 2.5 hours for the sake of manipulating the IGT.
You can argue that it's an acceptable method of IGT manipulation in many other games. Maybe even acceptable in this one, and I would agree with you. However, if it becomes required to any extent close to what RaveTuba posted, then it's a gross strat and would make this game far less enjoyable to run.
While I agree with zenix, that's an ambiguous rule, if you can even call it that, and I recall the reason for banning music entirely was that the existing rule of ensuring music doesn't drown out game audio was already being ignored. The response to receiving several submissions with muted audio or music that's blasting over the entire game audio prompted mods to instill the "no audio save for game and mic audio" rule being implemented in the first place.
With that said, I definitely agree that the music rule should be simple etiquette on the runners part if they want to submit a run, however I also understand the mods' frustration with runs that end up muted or have music that is simply way too loud.
I don't have a dog in this fight since I don't run this game, but I think zenix is on to something with reinstate a vague suggestion, rather than a rule. Mods can use their discretion to accept or reject a run. If a runner has an issue with a rejection while they have muted audio, too bad. However if someone submits a 14th place run and a mod lets it go with a chunk of audio muted, I see very little harm done with that as well.
Double standard? Sure. But people seem to hate the definitive single standard that has been set out, so here we are.
All existing links were deactivated recently due to a concern of people spamming entire servers with PMs containing child pornography. I don't know what the status is with that now, but if the ban on links is lifted, someone will share a new one shortly, I'm sure.
Your last point, @ravetuba, is definitely where I've been missing the point. I didn't realize that even the livesplit timer will actually rewind to the last checkpoint. I was under the impression that it only ever paused, and counted upwards. I will admit, I didn't look at it that closely, which is why I was maintaining that my accidental reset only lost me time by requiring me to essentially do that entire section again. I was not aware that even livesplit resets my timer to the last checkpoint.
I agree now, 100%, with that reset being rejection worthy. When it comes to my multiple deaths at the end of that run, it does appear that the counter continues going upward. Is it safe to assume that if mutated Wesker keeps tossing me off the rock that retrying is not rejection worthy? In that case, each death is simply losing me time, and it's only in my best interest to "git gud", but in the meantime, nothing unfair is happening, correct?