wtf is this error? I can only assume that think is some kind of timing routine in the scripting virtual machine, but what would cause the game to bomb with this error?
Is it because I called too many entites from the script? The area it died in was just at the point where I call about 16 different entites (using 4 different names) at the same time. Is that it?
Methinks bob will be the only one who can answer this.
Oh bob, where are thou?
perhaps (looking for the obvious) you’re pointing to a info_null with an entity that needs an info_notnull?
[edit because a new reply would be spam]
HTH :fiesta:
Aha, found it 
It seems that if you have a target_rumble, you have to wait until it has completed it’s rumblings before you can trigger it again. You can’t restart the rumble while it is still rumbling or you get the “null ent->think” error
Ironically Irellevant, your post made me double check and I did find three null entities left over from something I had removed 