Well, no not really. But here's an odd thing.
You know me from when I log on because of my herlading, bold yellow "on entry script error"...
Well, that's because I walk around with multiples of every useless piece of schwag I can get my hands on hoping to stumble across the secrets to a new weapon recipe.
In the last few days, when I've *tried* to make Cinder the anvil actually allows me to make the attempt and then spews out a script error along the lines of "too many instructions"... What does it all mean ???
Do I, in my plethora of bags and pouches, hold the secret to Cinder...?
Probably not.
The ATS System never takes away any ore of any kind or tells me any other ingredient that's been consumed.
But when it even gives you a CHANCE to make the attempt you feel as giddy as a schoolgirl... Then you realize you're wearing the the velcro-stitched prom dress and ATS as leering at you.
The Secret of Cinder revealed
Moderator: Lords of The Realm
-
NebUnderfoot
- Dasarian Hero
- Posts: 377
- Joined: Thu Oct 03, 2002 2:20 pm
The Secret of Cinder revealed
If there's going to be crime in Dasaria, it may as well be roganized
No, it means you have the components. You simply have too many items in your inventory though.
The same problem appears with other trade skills when you're too full, sometimes even though you get the script error you are able to make the item, sometimes you are not. But you certainly have the components.
The same problem appears with other trade skills when you're too full, sometimes even though you get the script error you are able to make the item, sometimes you are not. But you certainly have the components.
-
Melthavion
- Site Admin
- Posts: 765
- Joined: Mon Sep 23, 2002 11:11 pm
- Location: Atlanta, GA
TMI error...."Too Many Instructions"
This error is an alternative to either the server crashing or your client crashing. You see, bad code CAN implement a situation where an infinite loop is created. Say, I told it to look for item x in your inventory, and as long as it finds item X, to go back to the top of your inventory and look for item X. A stupid example, but you get the point. The script would never exit, and the engine would eventually crash, which is a Bad Thing ®. Fortunately guys like those who wrote NWScript (and most scripting and programming languages) forsaw the need to put in failsafes against such things. If a particular script gets stuck in a loop, the NWScript engine tells it to eventually terminate after a certain number of iterations, to prevent the Bad Things ® from happening. The script is terminated, and whatever it was doing is stopped, finished, with no result. Now the down side to this is, where do you put that cut off point where the script engine tells the script to terminate if it's in a loop? Too long and a the Bad Things ® happen, too short and normal functions like a looping function to search a large inventory prematuraly terminates.
So basically, the ATS scripts are searching your inventory, but terminating because the max loop iteration limit is hit before it's done. The functions to remove items and do a skill check, etc are probably called later in the script, and thus never fire becuase it terminates. Paring down your inventory will get rid of the TMI errors, both in the ATS functions and in the onEnter functions (I know this for a fact because I've tried it first hand). But, you may accidentally get rid of one of the key ingredients as well....
Hope this helps, and feel free to point anyone else asking about TMI errors to this post...
Thanks,
-Mel
This error is an alternative to either the server crashing or your client crashing. You see, bad code CAN implement a situation where an infinite loop is created. Say, I told it to look for item x in your inventory, and as long as it finds item X, to go back to the top of your inventory and look for item X. A stupid example, but you get the point. The script would never exit, and the engine would eventually crash, which is a Bad Thing ®. Fortunately guys like those who wrote NWScript (and most scripting and programming languages) forsaw the need to put in failsafes against such things. If a particular script gets stuck in a loop, the NWScript engine tells it to eventually terminate after a certain number of iterations, to prevent the Bad Things ® from happening. The script is terminated, and whatever it was doing is stopped, finished, with no result. Now the down side to this is, where do you put that cut off point where the script engine tells the script to terminate if it's in a loop? Too long and a the Bad Things ® happen, too short and normal functions like a looping function to search a large inventory prematuraly terminates.
So basically, the ATS scripts are searching your inventory, but terminating because the max loop iteration limit is hit before it's done. The functions to remove items and do a skill check, etc are probably called later in the script, and thus never fire becuase it terminates. Paring down your inventory will get rid of the TMI errors, both in the ATS functions and in the onEnter functions (I know this for a fact because I've tried it first hand). But, you may accidentally get rid of one of the key ingredients as well....
Hope this helps, and feel free to point anyone else asking about TMI errors to this post...
Thanks,
-Mel