Help Forum |
|
|
Lurhstaap
|
5/28/2017 | |
My current world keeps throwing up an error I've never seen before. I'm not using any new agents or metarooms, except that I figured out how to unlock the second part of Nornhulu for the first time. That could be it, but even so, not 100% sure, because... well, I'll just explain.
The error says: "An agent script is possibly in an infinite loop. Choose Abort to throw an error, so you can see which agent it is and stop it. Choose Retry to let it run for another 1,000,000 instructions. Choose Ignore to let it carry on forever."
This... feels like a sphinx's riddle in a fairy tale. >.>
I'm too afraid to do Ignore, so I've not clicked that yet.
Retry causes the same message to appear within one second.
Abort doesn't bring up an error though like it says it will. Instead, the message goes away and the game goes on normally, not lagging more or anything, as if nothing happened. But within an hour or so, the same message will go up again. I've got a miraculously unlaggy world for how long it's existed, but this error is screwing things up because the world pauses every time it goes up, and I'm not always at the keyboard to Abort and get things going right away again.
Any idea what's causing this? Anyone else see this specifically with Nornhulu room two (the mostly-aquatic part)?
The only thing that it seems to be associated with is eggs hatching. But that may be a coincidence.
Conclude with killer catchphrase.
(Lurhstaap)
"This is not knowledge -
this is information!"
New Model Army, "Courage" |
Fuzzy Dragonhat
Pilla
|
5/28/2017 | |
Can you center on the faulty agent?
Does the thing give you any extra info? A classifier number? A script name?
EDIT:
Also, maybe it'd help to put autokill on? That way the world won't be interrupted I think. (Ctrl+w to open wolfling monitor, ctrl+a to turn autokill on IIRC)
Visit my Creatures blog/website - Pilla's DS Agents
Join us on Discord - Caos Coding Cave
Visit/contribute to the Creatures Wiki |
Lurhstaap
|
5/28/2017 | |
Nope. No such thing is possible. It's SUPPOSED to then go to an error message where I can do that, but that isn't happening. It's just going on like nothing happened. It's bizarre. No classifier, or I could figure out the guilty agent on my own. What I typed is -all- it says. x.x;
And Autokill IS on. That's another weird bit.
EDIT: Oh, I did a couple tests, and it doesn't trigger when eggs hatch. It's just a coincidence it's happened to in the past about when a death/new hatching happened. (Although... maybe it's a death script. But why the heck THAT would be I have no idea. I haven't done a thing to mess with those.)
Conclude with killer catchphrase.
(Lurhstaap)
"This is not knowledge -
this is information!"
New Model Army, "Courage" |
Peppery One
Papriko
|
5/28/2017 | 1 |
Have you tried turning autokill off then? Perhaps it is unable to take care of the infinite loop problem, but then suddenly feels responsible when your second error is supposed to come up.
Lets play plants! Photosynthesis... Photosynthesis... Photosynthesis... |
Lurhstaap
|
5/28/2017 | 1 |
I actually haven't. That's not a bad idea. I'll let y'all know what happens.
EDIT: Hooray! That let the proper error come up next time. At last, some data:
Runtime error in agent 2 15 20111 script 2 15 20111 10 unique id 2916950
ATTR/PERM change caused invalid map position (0.000000)
... o 2 elas 0 fric 100 {@}perm 100 rnge 1000 tick 1 setv ...
Although, I... don't recognize that classifier. Hmmmph. I'll have to look it up or click around a bunch I guess.
Conclude with killer catchphrase.
(Lurhstaap)
"This is not knowledge -
this is information!"
New Model Army, "Courage" |
Geat_Masta
|
5/28/2017 | |
Basically the game needs to wait for an agent to call wait, over, or stop to start processing the next agent's script. So when it's in a loop the game will lock up unless you kill the agent.
When you abort the agent is throwing an error, not the game, and that means it's script ends immediately. |
Fuzzy Dragonhat
Pilla
|
5/28/2017 | |
Lurhstaap:
I did a quick wolfling run and I got the infinite loop thing too.
With me it indeed got something to do with the Nornhulu room: more specifically the Seahorse script.
Visit my Creatures blog/website - Pilla's DS Agents
Join us on Discord - Caos Coding Cave
Visit/contribute to the Creatures Wiki |
Lurhstaap
|
5/28/2017 | |
@GM: It usually throws up a more useful error message when an agent goes kaput (the one I posted in the edit to my reply above), that's all. The one I got was much less helpful. And it confused me that it said aborting would bring up another error message (presumably the usual one), but it never actually did. I can only assume it's because Autokill was simply terminating the faulty agent before its glitch could cause the message to appear.
@Pilla: Thank you. It probably has to do with the seahorse in my case too as that part of Nornhulu is the only new thing in that world that I've never used before.
Conclude with killer catchphrase.
(Lurhstaap)
"This is not knowledge -
this is information!"
New Model Army, "Courage" |
Malkin
Manager
|
5/28/2017 | |
According to the Script Reservations page, you're looking for something by Liam.
My TCR Norns |
|