Objects won't take my variables?

[Epic_SkyPilot]

So I'm trying to make a spawn engine, only I have one problem. Most of my objects won't accept any scripting! I've just recently made an engine, and i'm using the same exact scripts for this one.

For instance, I have one laser that has "onLaserHit = e=>{ scene.my.rpm > 15 ? {} : { scene.my.imode = 4 }" so that basically means that while my engine is rotating slowly, a circle has it's collision to 4, or C. However, when I try to go to that circle and in collideSet type in scene.my.imode, it just deletes and in the console it says "collideSet was bound to bad type."

This is driving me absolutely crazy. It took me so long to make my first engine because of problems similar to this, only this time it's even worse. So often it seems like I just have a variable in the scene, and it's a 50/50 shot whether the geom will actually take it.

Please someone help me and explain what this problem is. And before I'm bombarded by the obvious suggestions, I'll just tell you: NO, it's not just the scripting wrong. I'm doing it the same exact way as in the other engine, which works 100% perfectly. And NO, I'm not typing the variable in wrong. I've tried at least a dozen times.

Thanks for the help guys.

[electronicboy]

if thats an exact copy and paste of what is in the box, you're missing a } at the end

[Epic_SkyPilot]

Thank you for the reply electronicboy, but no that's not the problem. I just took pictures of my scripts and type them in, I don't copy/paste.

[homieeee]

"collideSet was bound to bad type." means you aren't using an integer when attempting to set the collideSet. Either the variable is being set to something else without you knowing or you need to make sure you are using integers and not floats. EX: "CollideSet = math.toint(scene.my.var)

You should avoid using global variables like "scene.my." since you might have used it for something else and forgot. If you have any other questions just ask.

[Xray]

Epic_SkyPilot - Did you get your question resolved yet? If not, could you post an example scene that shows the problem you are having? Sometimes (usually) it's a lot easier for us to figure out a problem when we have an example to test, rather than trying to go by a verbal explanation of it.

[T'wind_]

First initialize your variable in the console. Just type in the console scene.my.imode = 0; or another value.
The reason it just deletes is probably because scene.my.imode has no value while you type it.

[FRA32]

Teh reason you have the problem is because when having a fresh scene(time wasnt runnign yet, or no update methods were changing your scene.my variables) all the new variables hav eno value. If you try to set an objects collideset to something that isnt a value at all it spits out an error because it needs a value to specify the collideset. The best solution is to call up the console using f10 and then typing in
"scene.my.imode = 0"
this way you add a default value to it at the start so everything is working.