Character Frustration

[Toasty]

I just got done re-building my whole Mugen roster of over 500 characters in without the DBZ characters this time around, and after all that my WinMugen crashed. I used the 500+ character slot patch from the site that also has Mugen Fighting Jam in it, but I'm sure it wasn't the issue, cause I added everything correctly from the screenpack into the winmugen data folder and font folder. I'm assuming that this is another character issue.

There should be a list of characters that are known to crash WinMugen so everybody can safely run Mugen without any crashes.

[dennis872005]

I just got done re-building my whole Mugen roster of over 500 characters in without the DBZ characters this time around, and after all that my WinMugen crashed. I used the 500+ character slot patch from the site that also has Mugen Fighting Jam in it, but I'm sure it wasn't the issue, cause I added everything correctly from the screenpack into the winmugen data folder and font folder. I'm assuming that this is another character issue.

There should be a list of characters that are known to crash WinMugen so everybody can safely run Mugen without any crashes.

well then you do it. cause no one else is gonna try the thousands of chars, really why do you need 500

[eg6gsr]

when it crashes it should tell you what the problem is and what needs to be fixed.....as for the char thing.....it would be nice but most of the time it can be fixed so there is really no need to have that list

[Toasty]

500 characters to put up any dream match I have ever thought of when I was playing all the fighting games before Mugen came, and basically to see a character I hate get his butt kicked and pretty much any characters made off of shows and what not triggers the question "what if this guy were to fight this guy, who would win?", so basically that kind of question is obviously easy to answer, why bother having about 30? or 10 even?  :

As for the error, as soon as I tried running it i got the "winmugen has created a problem and needs to close" error, before that error I got errors like "cannot find system.sff" and "cannot load system.def" which meant that I wasn't putting the screenpack in correctly and those were fixed.