u/Sneakytako99

First of all, yougame is not a mod of any game, but a browser based game platform that can be used to host online matches for retro games and mods including project plus.

This makes it closer to things like parsec and fightcade rather than brawlback.

Secondly, unlike fightcade, yougame does not use ggpo IE rollback. (Probably)

To get into weeds, yougame hosts their platform on a browser as opposed to fightcade having the emulation done via the client.

The benefit of doing this browser based that its a less heavy load so packet losses are less common.

However I don't see anything about yougame using predictive inputs and rolling back gamestates if the prediction was wrong. Since the browser itself is running the game, I'm thinking its not trying to rollback but simply there to stabilize the connection. I'm not actually sure how it solves discrepancies between two instances of a game tbh, yougame isn't open source and I don't see any literature.

Could yougame be an improvement to what we currently have? Very possibly, but it will probably depend on how well it runs on both browsers.

Does yougame use ggpo rollback? Probably not but I can't say for 100% certainty. Based on the context of how its hosted its highly unlikely imo. Edit there was a github i missed it totally does

Is yougame AI slop specifically made to spite brawlback? Absolutely not. Its a game hosting platform that could possibly be useful for P plus.

Don't jump to conclusions. Do your own research.

Scenario - You enter a tournament where you've never played on this setup, and you have to reset your controller scheme.

You fiddle through the control menus, trying to remember exactly where everything is, and the values you used.

Instead of trying to memorize 20+ things, could the menu just spit out a 4 digit signature after inputting your control scheme at home that you could enter in every setup so that it replicates the same controller setup? This would be a huge especially for bigger tournaments.

EDIT: I wrote a sample code in javascript that's pretty basic, it covers all the non-controller bindings because I don't really understand the gcube/keyboard/xbox controller differences (and that part is pretty easy for the player).

https://github.com/Sneakytako/Rivals-2-control-scheme-code/tree/main

I got beef with the lox dair change.

This is the change in question:

• Down Air's feet are no longer intangible during the active frames
  • This made the move too easy to hit against recovering opponents, since it could not be challenged from below, so we're reverting this change. This also allows Loxodont to trade with recovery moves, which can end up saving him in certain deep offstage interactions.

The problem is two fold:

First the change doesn't really meaningfully impact using dair against recoveries. Yes it may create scenarios where there will be more trades, but most of the time the character recovering will still die regardless of whether it's traded or not. Extending the Lox's hurtbox down means that it's slightly harder to use the disjointed part of the hitbox but it's not like Lox could really outspace most character's up-b to recover like olympia or clarian.

The main way you land lox dair off the stage is hitting with dair before they can up-b, since the size of the hitbox doesn't change it doesn't actually allow for more scenarios where the recovering character survives.

This probably only effects the recoveries that grab like lox side-b or la reina up-b, but la reina up-b got nerfed at the top of the recovery so it's probably a wash.

What this actually changes and where I have the biggest beef is the effect on platform tech chasing. Upthrow -> dair as a platform tech chase was effective partly because the disjoint allowed for beating fast getup options by using the disjointed part of the hitbox. Now there's more of a chance that it will trade, which eliminates a follow up on the dair tech chase and causing a scramble situation.

Boo this change sucks, gimme my platform tech chase back. Up-b nerf for having more landing frames is probably fine.

EDIT: I'm not personally that salty, but I am concerned that when changes don't match the intent of the change posted.