Pilot, those aren't really errors there. The extra set of parentheses won't make a difference to the expression's value.
It's not a good idea to assume that a sleep at startup will fix everything. But in this case, I think a sleep of a second is needed.
The real problem here may be with the concept of lookvectors. A lookvector is simply a direction. When JK gives a thing a lookvector, it has to make the thing look in that direction as it naturally should. It is JK, and not the lookvector, that makes the thing stand upright as it looks in a direction. This is why you cannot make a thing look upside-down with a lookvector.
So I think your problem, Gel, is that the original thing is upside-down somehow.
As for the cog, I see several problems with it:
- console is given a mask which should be in hexadecimal, but the '0x' is missing.
- walkwaytemp isn't being used.
- The sender of activated: is not checked.
- x is set to two twice, but is assigned again before that value is used.
- The returns inside the pulse's if statements are unnecessary.
- The code that is run depending on whether x is 0 or 1 is the same except for one line.
This redundancy could be fixed by using an if statement in the for loop such as:
Besides those, I am curious about the system you have of creating a new thing, attaching it, rotating it, and then waiting for a while before beginning again. Does this system work as you intented it to?
------------------
Author of the
JK DataMaster,
Parsec,
Scribe, and the
EditPlus Cog Files.