WanderingScholar Posted December 1, 2023 Share Posted December 1, 2023 How do I diagnose this type of error? What does (state 970) and [0] EOF mean? Is there an index for these codes. I made some edits in mage.tpa, but when I look at this file, it doesn't seem like there's anything going on at line 633. Spoiler Reading in data: stats Copying 1 file ... Copying and patching 1 file ... Copying and patching 1 file ... Appending to files ... Appending to files ... Appending to files ... Appending to files ... Copying and patching 1 file ... Appending to files ... Including and running function(s) mage Copying and patching 1 file ... In state 970, I expected one of these tokens: [0] EOF Parse error (state 970) at END [stratagems_external/workspace/mage.tpa] PARSE ERROR at line 633 column 1-3 Near Text: END GLR parse error [stratagems_external/workspace/mage.tpa] ERROR at line 633 column 1-3 Near Text: END Parsing.Parse_error ERROR: parsing [stratagems_external/workspace/mage.tpa]: Parsing.Parse_error Stopping installation because of error. Stopping installation because of error. Stopping installation because of error. ERROR Installing [Smarter Mages -> Mages cast some short-duration spells instantly at start of combat, to simulate pre-battle casting], rolling back to previous state Will uninstall 7 files for [STRATAGEMS/SETUP-STRATAGEMS.TP2] component 6030. Uninstalled 7 files for [STRATAGEMS/SETUP-STRATAGEMS.TP2] component 6030. ERROR: Parsing.Parse_error mage.tpa Quote Link to comment
DavidW Posted December 1, 2023 Share Posted December 1, 2023 EOF means end of file. It probably means you haven’t closed a loop. Quote Link to comment
WanderingScholar Posted December 1, 2023 Author Share Posted December 1, 2023 16 minutes ago, DavidW said: EOF means end of file. It probably means you haven’t closed a loop. Any idea where I should start looking to narrow it down? Is it possible the error is in one of the setup files being included? Quote Link to comment
DavidW Posted December 2, 2023 Share Posted December 2, 2023 Almost certainly not. This is just a standard programming syntax error; you will have forgotten to close something. Quote Link to comment
jmerry Posted December 2, 2023 Share Posted December 2, 2023 And on that error location ... when it says something happened on line 633, the place to look is before line 633. That's just where the error became impossible to work around, not where the error is. Quote Link to comment
WanderingScholar Posted December 2, 2023 Author Share Posted December 2, 2023 Thanks, I tracked this down. It was the "END" at line 546 I found if I add blank rows within the code I can narrow things down by re-installing and checking the number. Quote Link to comment
Recommended Posts
Join the conversation
You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.