Skip to content
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.

Repeated nullbot error message after starting a saved game #4409

Closed
wzdev-ci opened this issue May 22, 2016 · 10 comments
Closed

Repeated nullbot error message after starting a saved game #4409

wzdev-ci opened this issue May 22, 2016 · 10 comments

Comments

@wzdev-ci
Copy link
Contributor

resolution_closed type_bug | by darkling


I'd started playing a game on the Vision map using nullbot AI set to hard difficulty. When I came to open a saved game there was an error message that kept repeating in-game and in the log as well:

error |08:08:32: [callFunction:186] 1 : () at -1
info |08:08:32: [callFunction:189] Uncaught exception calling function "updateStatus" at line 617: TypeError: Result of expression 'enemyInfo[i]' [undefined] is not an object.
info |08:08:32: [callFunction:189] Assert in Warzone: qtscript.cpp:189 (false), last script event: 'N/A'

the log from the prior session contained no messages however.
I don't know what effect it had, but the AI was less challenging afterwards.


Issue migrated from trac:4409 at 2022-04-16 11:58:23 -0700

@wzdev-ci
Copy link
Contributor Author

darkling uploaded file visionnew 3.tar.gz (91.1 KiB)

save game

@wzdev-ci
Copy link
Contributor Author

darkling uploaded file nullbot.1.log.old (43.7 KiB)

nullbot log

@wzdev-ci
Copy link
Contributor Author

darkling commented


missed the first line:

error |04:55:12: [callFunction:186] 0 : updateStatus() at multiplay/skirmish/nullbot-main.js.inc:617
error |04:55:12: [callFunction:186] 1 : () at -1
info |04:55:12: [callFunction:189] Uncaught exception calling function "updateStatus" at line 617: TypeError: Result of expression 'enemyInfo[i]' [undefined] is not an object.
info |04:55:12: [callFunction:189] Assert in Warzone: qtscript.cpp:189 (false), last script event: ''

@wzdev-ci
Copy link
Contributor Author

darkling uploaded file WZlog-0522_165449.txt (563.6 KiB)

warzone log

@wzdev-ci
Copy link
Contributor Author

NoQ commented


Hello, thanks for the report! Such reports are very useful, because such error messages indicate crashes of particular sections of the AI scripts, and the AI starts to misbehave. However, i'm planning to push a big update on NullBot (v2 -> v3, the new version is now available as a mod at http://forums.wz2100.net/download/file.php?id=16160) into one of the nearest 3.2_betas, and being a full rewrite, it should fix this particular issue (in a sense, that code would certainly no longer be there anymore), and perhaps open up some new ones; this ticket would probably be closed with "needs re-evaluation on a more recent version", and i'd eagerly listen to any bug reports against the new version of the AI!

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Dec 9, 2017

Berserk Cyborg changed status from new to closed

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Dec 9, 2017

Berserk Cyborg changed resolution from `` to closed

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Dec 9, 2017

Berserk Cyborg changed blocking which not transferred by tractive

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Dec 9, 2017

Berserk Cyborg changed blockedby which not transferred by tractive

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Dec 9, 2017

Berserk Cyborg commented


Nullbot has changed much since this ticket was created. As such, this report no longer is valid. If there are save issues with the current version of Nullbot included with recent releases then feel free to create a new ticket.

@wzdev-ci wzdev-ci closed this as completed Dec 9, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant