Syntax Error / Unexpected Number

[orges]

When i try to enter in a battle i get this "Syntax Error / Unexpected Number"


can someone help i know i did somthing with the YEP battle engine core......here is the pic of the error

View attachment 32505

View attachment 32506

 

[Andar]

If you get a syntax error, then that usually means that the content of the js file is not what it is intended - you either deleted or added letters or numbers where they don't belong.


Have you downloaded the files directly or did you copy&paste them into an editor file manually? This usually happens if you either copied them or opened them in an editor and changed them there.


Much more rarely it could also be that the file is missing a requirement like a core file, have you checked if you have all needed cores installed?

 

[orges]

When i try to enter in a battle i get this "Syntax Error / Unexpected Number"


can someone help i know i did somthing with the YEP battle engine core......here is the pic of the error

and if i deactivate  or remove the Yep-battle engine core the sprites of my actors/party does not show themselves here is the pic

 

[orges]

If you get a syntax error, then that usually means that the content of the js file is not what it is intended - you either deleted or added letters or numbers where they don't belong.


Have you downloaded the files directly or did you copy&paste them into an editor file manually? This usually happens if you either copied them or opened them in an editor and changed them there.


Much more rarely it could also be that the file is missing a requirement like a core file, have you checked if you have all needed cores installed?

Well thnx for the replay ......in fact i just removed the plugin than added it again now everything works fine ....thnx again   ........was like u said i did mesed up sth in the values of the yep battle engine core

 

[Shaz]

I've moved this thread to JS Plugin Support. Please be sure to post your threads in the correct forum next time. Thank you.


It could also be if you're using an older version of the plugin.  Yanfly has provided frequent updates whenever an issue is found, so making sure you've got the latest and greatest is also a strategy to try when you have issues like this.  I doubt that's the case in this instance though, as something so obvious would have been tested and found (or reported many times already)