YesNoOk
avatar

MUGEN Crashes Compilation (Read 12829 times)

Started by Noctis, February 22, 2016, 08:08:27 pm
Share this topic:
MUGEN Crashes Compilation
#1  February 22, 2016, 08:08:27 pm
  • ****
  • Hey, I'm Grump!
    • USA
    • soldier.ucoz.net/
This thread will be used for discussing and compiling all the known and newly found reasons for MUGEN crashing. Anyone willing to contribute, go right ahead and post. It can be what caused your MUGEN to crash or a new type of MUGEN crash not yet compiled here. Thanks!
I'll update this post as often as I can.

Types of known crashes
  • Typo's
  • Missing files
  • Broken or corrupted files
  • Infinite changestates
  • Non-existent coding (i.e wrong MUGEN version)
  • Broken limits (commands, group number, etc.)
  • Improper coding
  • Clashing coding

Examples


Typo (You absolutely must have trigger1. Always.)
Code:
[state 0, velset]
type = velset
trigger2 = !time
x = 1
y = 1



Missing files (You absolutely must have 1 of these files available even if it's gonna be blank.)
Code:
[Files]
Cmd      = Player.cmd
Cns      =
St       = Player.cns
StCommon = Basics.cns
Sprite   = Player.sff
Anim     = Player.air
Sound    = Player.snd



Broken or corrupted files (Example is unavailable. If anyone has an image perhaps of a broken or corrupted file, leave a post below.)
Code:
Broken or corrupted files have practically become a thing of the past with the release of Fighter Factory 3



Infinite Changestates (This can be difficult to explain because there's so many ways for this to occur, but basically one way to avoid this is do NOT send yourself into a state with a command that continuously triggers if that state is going to send you back to the state you were just in.)
Code:
;---------------------------------------------------------------------------
; stand
[statedef 0]
type = s
physics = s
sprpriority = 0

[state 0, changestate]
type = changestate
trigger1 = command = "holddown"
value = 10

;---------------------------------------------------------------------------
; stand to crouch
[statedef 10]
type    = c
physics = c
anim = 10

[state 10, changestate]
type = changestate
trigger1 = command = "holddown"
value = 0



Non-existent coding (A piece of coding being used in the wrong version of MUGEN is just one type of example for this type of crash. VolumeScale was not implemented until MUGEN 1.0 hence the crash when used in WinMugen.)
Code:
MUGEN Version used = WinMugen

[state 0, playsnd]
type = playsnd
trigger1 = !time
value = s0,0
volumescale = 255



Broken limits (There are many limits to break in MUGEN. One of which is having too many commands. Keep it to a minimum to avoid crashing and if you NEED said many commands, then your character probably needs to be scaled down a bit. :D)
Code:
[command]
name = "AI-0"
command = a, a
time = 0

[command]
name = "AI-1"
command = a, b
time = 0

[command]
name = "AI-2"
command = a, c
time = 0
.
.
.
.
[command]
name = "AI-299"
command = a, b, c, x, y, x, U, D, F, B
time = 0



Improper coding (Many examples can be made, but the easiest one to notice is the difference between Vars and FVars. Vars are for whole numbers ONLY much like most of everything else number related in MUGEN. FVars are for decimals AND whole numbers and can be used without much of anything breaking, but most of the time it will need to be floored because while FVars can be used for either type of number, it greatly depends on what it's being used for. Like Power for example. Power does not use decimals so the FVar would need to be floored.)
Code:
[state 0, varset]
type = varset
trigger1 = !var(0)
var(0) = 1.1

[state 0, varset]
type = varset
trigger1 = !fvar(0)
fvar(1) = 1001.9514

[state 0, powerset]
type = powerset
trigger1 = !fvar(0)
value = fvar(1)



Clashing coding (Basically, there's seemingly no reason for the crash and sometimes there won't even be an error message. The only way to find it is to backtrack as far as you can by removing everything you recently added until it stops crashing. Then you add it all back one by one while also testing testing out MUGEN each time something is added until it crashes. Once you've found the culprit and nothing's wrong with the culprit itself, then it's related to an interfering piece of coding somewhere else. Now, we leave what we think is the culprit and repeat the process again. Remove, add back one by one, test in MUGEN one code at a time until culprit is found, repeat. Once you've found the clashes, figure out why it clashes.)
Code:
In the current build of PCEA (Project Catch 'Em All),
the game crashes without error whenever we try to use a SuperPause or Pause.
I'm not sure why this is yet,
but it could have something to do with having a heavily-edited common1.cns file.
I've seen most of this kind of stuff in full games and the causes are extremely hard to track down because,
there's no error message or anything guiding you.

(Youtube) (WIP) (Mediafire) (New Anime Shop) My Manga Reviews! Personal favorite Patreon! Check her out!

"There is nothing either good or bad, but thinking makes it so."
Last Edit: May 10, 2016, 03:39:59 pm by Noctis
Re: MUGEN Crashes Compilation
#2  February 22, 2016, 08:41:05 pm
  • ****
  • Target Acquired.
    • Ukraine
    • mugencoder.com
In the current build of PCEA (Project Catch 'Em All), the game crashes without error whenever we try to use a SuperPause or Pause. I'm not sure why this is yet, but it could have something to do with having a heavily-edited common1.cns file. I've seen most of this kind of stuff in full games and the causes are extremely hard to track down because there's no error message or anything guiding you.

-[Все слова это только слова.]-
Re: MUGEN Crashes Compilation
#3  February 23, 2016, 04:58:56 pm
  • ****
  • Hey, I'm Grump!
    • USA
    • soldier.ucoz.net/
Setting power to 0 under Data crashes MUGEN without an error message. However, setting it to -1 doesn't crash MUGEN and the powerbar is considered full. I'm not sure how this interferes with characters attempting to control your powerbar. I released a character with -1 power yesterday. Now we wait for the results.

Also, setting Life to anything less than or equal to 0 crashes MUGEN without warning.

Actually, pretty much doing anything out of the ordinary under Data creates weird results or unannounced crashes.

(Youtube) (WIP) (Mediafire) (New Anime Shop) My Manga Reviews! Personal favorite Patreon! Check her out!

"There is nothing either good or bad, but thinking makes it so."
Re: MUGEN Crashes Compilation
#4  March 06, 2016, 08:50:42 am
  • ****
  • stillRetired.
  • Formerly Known As Genesis
    • www.mediafire.com/folder/7j1slkpa7lm0w/Public_Works
idk how to word this properly, but from my recent screenpack testing, having the cursor start on a cell thats technically non-existent will make mugen crash without error once you try to move, or even sometimes as soon as you reach the select screen. I even got it to crash once i moved down on the main menu.
I should mention you can have the option to move over empty boxes on and it'll still happen.

2OS had a thread with things that cause crashes in 1.0 without errors and how to fix them somewhere. Might be worth adding to this thread.
Re: MUGEN Crashes Compilation
#5  April 04, 2016, 10:38:46 pm
  • *****
  • Gaps? Where we're going, we don't need gaps...
    • USA
    • ricepigeon.neocities.org
In Mugen 1.0, setting the character's internal name (not the displayname parameter) past a certain character limit will cause the character to be automatically KOed at the beginning of a match, among other issues.

Typo example: forgetting to close parenthesis in triggers:
Code:
[State 200, CS]
type = changestate
trigger1 = (var(20)=1 ;note that the first set of parenthesis is left often
value = 0
Last Edit: April 04, 2016, 10:42:38 pm by Ricepigeon
Re: MUGEN Crashes Compilation
#6  April 05, 2016, 09:43:54 am
  • ******
  • Legendary XIII
  • I am the eye of the storm to come!
    • New Zealand
    • network.mugenguild.com/cyanide/
In the current build of PCEA (Project Catch 'Em All), the game crashes without error whenever we try to use a SuperPause or Pause. I'm not sure why this is yet, but it could have something to do with having a heavily-edited common1.cns file. I've seen most of this kind of stuff in full games and the causes are extremely hard to track down because there's no error message or anything guiding you.

What happens if you just run with the regular common1.cns in a standard game of mugen? That narrows it down, you can then add in the fancy one. Here i wouldn't be overly surprised if someone used the elecbyte template and is experiencing that particular issue.


In M.U.G.E.N there is no magic button

They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance.
Re: MUGEN Crashes Compilation
#7  April 22, 2016, 05:44:25 pm
  • ****
  • Hey, I'm Grump!
    • USA
    • soldier.ucoz.net/
In Mugen 1.0, setting the character's internal name (not the displayname parameter) past a certain character limit will cause the character to be automatically KOed at the beginning of a match, among other issues.

Typo example: forgetting to close parenthesis in triggers:
Code:
[State 200, CS]
type = changestate
trigger1 = (var(20)=1 ;note that the first set of parenthesis is left often
value = 0

I've had situations where I have one worthless parenthesis in a bit of coding and it doesn't crash MUGEN and it work's just fine as well without error.
Kinda like what you've got written up there now, but with a lot more codes and shit.
Also, you mean
Code:
[Info]
name        = "Alena" ;<-- this one?
displayname = "Alena"

Edit:
Haha that's weird. Added about 100 A's and my character became invincible. She could only be killed through the Mugen's F commands. She remained at 1 hp no matter what I did.
I wonder if this could be used in some way to our benefit... what happens in Training Mode I wonder.

(Youtube) (WIP) (Mediafire) (New Anime Shop) My Manga Reviews! Personal favorite Patreon! Check her out!

"There is nothing either good or bad, but thinking makes it so."
Re: MUGEN Crashes Compilation
#8  April 23, 2016, 03:22:57 am
  • ******
  • Legendary XIII
  • I am the eye of the storm to come!
    • New Zealand
    • network.mugenguild.com/cyanide/
Nope, totally useless. It does that for YOU. For someone else, the character just died. I saw one where the lifebar duplicated for them, but when i tried it i had 1 health and died after a single hit. Same character.


In M.U.G.E.N there is no magic button

They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance.
Re: MUGEN Crashes Compilation
#9  July 05, 2017, 11:35:56 pm
  • ******
    • www.justnopoint.com/
Using a command that doesn't exist outside of the .cmd will crash MUGEN without error.

ink

Re: MUGEN Crashes Compilation
#10  January 21, 2018, 10:02:52 pm
  • ****
  • inktrebuchet
    • USA
    • s236.photobucket.com/albums/ff271/inktrebuchet/?
This is an old topic but I finally made a piece of code that crashes MUGEN 1.0 with no errors. The idea is to use this in a pause menu. Quit Game

Code:
;Crash Game with no errors by Inktrebuchet
[state -2, Quit Game]
type = DisplayToClipboard
trigger1 = command = "s" ; test trigger
text = "99999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999%d "
params =  0
Last Edit: January 21, 2018, 10:43:44 pm by ink
Re: MUGEN Crashes Compilation
#11  January 30, 2018, 03:53:40 am
  • **
    • mugen.wikia.com/User:Jenngra505
Hopefully someday I'll be able to make the little puffball on my profile pic.
(Sprite edited from Scrollboss' sprite)