Well, there could also be a way for the game to do some sort of level balance where it nerfs stats before a match.

Yea, I was thinking about that as well. Basically, which ever calc was player 1, it would have to do a check when they linked up. It would make sure both players had the same characters available. It could either do a data transfer, or simply disallow the ones that were different. Another option would be to only allow the characters on P1 calculator and transfer them to P2's calculator. It really depends on how multiplayer gets set up (via link cable or calcnet) and how calcs handle processing the realtime game data.

Sorry for the lack of answer, I was a bit sick and preferred not to spend too much time on forums.

I don't think I'll implement something that equalizes characters, it seems too much of a Brawl idea. The only good side I see in such a system is if someone with good intentions set all hitbox forces well proportionned between each other, but too high compared to other characters. In that case, maybe there should be a field that reduces hitbox forces if they were set too high by mistake. But I am pretty sure no one will do that on purpose since 1] it would kill all the fun and 2] other players could choose that character too and it would not be so OP against itself I guess.

And yeah, transferring files might be too annoying. Calculating the intersection between both lists is probably a better idea, even though it would still take some time to calculate and would still be some code to write (plus the fact as you mentionned earlier, someone could have a Reuben and someone else could have another Reuben without the algorithm making the difference).

Sorry for the lack of answer, I was a bit sick and preferred not to spend too much time on forums.

I don't think I'll implement something that equalizes characters, it seems too much of a Brawl idea. The only good side I see in such a system is if someone with good intentions set all hitbox forces well proportionned between each other, but too high compared to other characters. In that case, maybe there should be a field that reduces hitbox forces if they were set too high by mistake. But I am pretty sure no one will do that on purpose since 1] it would kill all the fun and 2] other players could choose that character too and it would not be so OP against itself I guess.

And yeah, transferring files might be too annoying. Calculating the intersection between both lists is probably a better idea, even though it would still take some time to calculate and would still be some code to write (plus the fact as you mentionned earlier, someone could have a Reuben and someone else could have another Reuben without the algorithm making the difference).

Yeah my concern was mainly when somebody just uses characters that are OP. But I guess the solution then would just be to disallow characters that are not present on both calcs with identical stats between the two copies.

Any further work on this?

If I remember, I think work was supposed to stop completely once school start, so I guess that progress will be minimal until Summer vacations or Christmas holidays. For the time being, the project is under our hands: We have to create characters.

Is the game (engine) done aside from creating characters?

Are you going to add items?

Cool, what's "FD" mean?

Oh, okay. Will there be moving platforms?