Game Crashes During Battle

[Blah_Blee]

Hi there, I'm having an issue with the battles in my game. My character's sprite doesn't appear whatsoever during battle, and every time I press the 'fight' command, the game crashes and this prompt appears.



I am currently using Jet's simple side-view battle system, as well as Yanfly's core battle script, if that means anything. 

 

[Iavra]

Could you link the scripts? Also, since line 318 of Scene_Battle doesn't contain "move_x", can we assume that you changed the default scripts?

 

[Blah_Blee]

That's the problem. I'm not if I changed the default scripts whatsoever. I tried copying the default battle script from another one of my games that use the side view battle system, but the problem still persists. By 'linking the script' you mean the original? Or my slightly modified version? Here's the former just in case.

Side View System:

Yanfly Core Battle

 

[Andar]

neither - we prefer links to the original sites, because those usually include additional comments and bugfixes about the scripts.

And if you modified or rewrote some parts of those scripts, we need to know those changes as well

 

[Blah_Blee]

Oh, my bad. Here are the original sites:

Simple Side View

Ace Battle Engine

Here is a screenshot of where the prompt refers to.

 

[Another Fen]

Does the error occur when you use those original scripts (assuming you modified them)? How did you set up the test battle? If you modified them, what exactly did you do?

The scripts seem to run fine for me.

 

[Blah_Blee]

Oh, it turns out that the Ace party menu script conflicted with the battle system in general. I fixed it.

 

[Andar]

Here is a screenshot of where the prompt refers to.

unfortunately, no - it isn't.
But that screenshot still was very important to localising the bug, because it prooves that your scripts got mixed up...


Go back to the original bug report picture:


It says that method 'move_x' in Scene_Battle line 318 is not defined.


Now look at your own screenshot: it does not contain that move_x anywhere on that line 318.


This prooves that the screenshot is from a different script than the error - somehow you got your scripts mixed or damaged, and you now have to check where the correct scripts are...


Please check if you have two scripts with that name installed

 

[Another Fen]

I think that is just because the exact source location could not be displayed within the next_command method, as that method is defined in an extra eval call in Jets script.