Movement/room changing script works, then causes errors

Foxley · Post by **Foxley** » Mon Jun 15, 2015 3:08 am

I wrote up a room changing script that is actually pretty elegant and easy for me to work with (I surprised myself). However after changing rooms once, I then get a "slicecollidepoint: invalid slice handle 0" error from the "mouse clicked" script when clicking anything.

It's basically James's mouse click script in the other thread with slight modifications. Mostly I removed the "holder" argument.

Code: Select all

script, mouseclicked, slice, begin
	variable&#40;sl&#41;

	sl &#58;= lookup slice &#40;slice&#41;
	if &#40;mouse click&#41; then &#40;
		return &#40;slice collide point &#40;sl, mouse pixel x, mouse pixel y&#41;&#41;
		&#41; else &#40;
		exit returning &#40;false&#41;
		&#41;		
end

I don't know what my change room script is doing to make the error happen. All it does is free the slice tied to the 'currentroom' global variable, load the appropriate new slice collection to 'currentroom', and then update the 'currentroomID' number value. 'currentroomID' is a global variable I made so I can check what the current room is in a switch/case.

Any ideas? Anyone want to look at my .HSS and see if you notice anything wrong?

Foxley · Post by **Foxley** » Mon Jun 15, 2015 3:40 am

Ugh. Nevermind... I found out what was causing it. I put a weird line in the "check HUD clickables" script to check if clicking the room slice container was registering a response. I took it out and now room change/movement is WORKING. Woohoo!

Foxley · Post by **Foxley** » Thu Jun 18, 2015 12:45 am

This error is happening again, but more drastically. I split up my single script check-for-slices-and-do-something-if-it's-there script into separate smaller scripts for the sake of organization, and now this seems to be happening. If I hit "Ignore" when it comes up I seem to have to hit Ignore for as many checks as there were. I'm going to just go ahead and upload the ZIP to my Dropbox, if anyone cares to figure out what's going on here.

https://www.dropbox.com/s/hhdoriia3gpor ... p.zip?dl=0

Foxley · Post by **Foxley** » Thu Jun 18, 2015 1:44 am

It seems that any slice that's clicked that's not in Slice Collection 0 (the one that gets autoloaded in the new game script) then it gives a slice handle 0 error.

.... Does that mean that you can only check for slice lookups that are currently loaded and visible on screen or else it'll be like "derp, that's slice handle 0"? If so, that really sucks, and I don't have enough time to re-plan and re-write the entire first person engine I've implemented so far.

Post by **Bob the Hamster** » Thu Jun 18, 2015 1:53 am

If "lookup slice" cannot find the code, then it returns 0

Slice collections do need to be loaded, but they do not need to be visible

Foxley · Post by **Foxley** » Thu Jun 18, 2015 2:42 am

Is there any way for it to ignore slices it can't find so it at least doesn't cause script errors? I can't have every slice collection in the entire game loaded all at once, that's not going to work.

Foxley · Post by **Foxley** » Thu Jun 18, 2015 3:22 am

Okay. Now that my critical thinking faculties are working a bit better, I think I might have an idea. Maybe I can have situational slice collections like submenus and separate screens that aren't always visible be loaded alongside tags being turned on. Then have if ( conditions related to those tags so it only checks relevant slice collections.

I really think that returning slice handle 0, game.exe should just be "okay, it's slice handle 0, I'm not gonna freak out" instead of making a script error interrupt the game, though. Really, the only reason this is even an issue is because of the script error popping up. Nothing bad or unintended even happens if I mash "Ignore".

Post by **Bob the Hamster** » Thu Jun 18, 2015 3:25 am

What you want to do is actually super easy

Code: Select all

sl &#58;= lookup slice&#40;sli&#58;foo&#41;
if &#40;sl&#41; then&#40;
  #do things that only happen if the slice is found
&#41;

Foxley · Post by **Foxley** » Thu Jun 18, 2015 3:39 am

Funny, I actually figured that out a minute ago, then F5ed the webpage and saw you had posted that exact thing I just did. Thanks again.

Post by **TMC** » Thu Jun 18, 2015 4:03 am

It really is very useful to show a script error immediately when you make a small mistake. New programmers usually don't realise it, but after years programming you understand that the sooner you find out about a mistake, the less time you will spend in the long run fixing it.

However, I ALSO agree that getting script error messages in the middle of a game is a bad thing. And unfortunately error messages pop up in some old games even though they don't seem to be broken and didn't show errors previously, because of something that changed in the engine at some point. So I want to make a change to script error reporting in existing games.