To night hawk

[Darksaber2213]

Because I can't PM, I'm posting this here.

In this topic: http://forum.blockland.us/index.php?topic=272741.0, I believe that I may have solved your problem. Instead of calling the schedule like you are currently doing, use this.

%obj.schedule(500, boltSpeedCheck)

The way that you are currently calling it tells the game that it is not an object schedule. I believe that this is the solution.

if anyone would be so kind as to PM night hawk and link him to this topic that would be great.

This is why topics in Coding Help shouldn't be locked.

But on another note, you're totally wrong about this.
Look at the function declaration:

Code: [Select]

function BoltSpeedCheck(%this, %obj)
It's not a method on an object, it's just a regular function.
You'd be right if it was like this:

Code: [Select]

function wheeledVehicle::BoltSpeedCheck(%this, %obj)
(Not sure if wheeledVehicle is the right class name, but it's just an example)

nevermind dont listen to me im dum :^P

[Ad Bot]

[jes00]

This is why topics in Coding Help shouldn't be locked.

But on another note, you're totally wrong about this.
Look at the function declaration:

Code: [Select]

function BoltSpeedCheck(%this, %obj)
It's not a method on an object, it's just a regular function.
You'd be right if it was like this:

Code: [Select]

function wheeledVehicle::BoltSpeedCheck(%this, %obj)
(Not sure if wheeledVehicle is the right class name, but it's just an example)

[Night_Hawk]

Thank you for that man! I'm thinking of reopening that topic so people can reply.

I locked it because I wasn't getting replies even though I'd say what was going on for a while, but I've opened it back up to users who have a solution. I now know I shouldn't do stupid things like this, and instead just to wait and see if someone can help?

[$trinick]

Thank you for that man! I'm thinking of reopening that topic so people can reply.

I locked it because I wasn't getting replies even though I'd say what was going on for a while, but I've opened it back up to users who have a solution. I now know I shouldn't do stupid things like this, and instead just to wait and see if someone can help?

Never lock Coding Help topics. Not infrequently are incorrect answers corrected, inefficient answers improved, or more general knowledge added on topics. This results in a better learning environment for everyone: the OP who needs the help, future coders who find your topic through searches, and Coding Help perusers who don't have a specific question but are soaking up the available information on the board. Locking the topic is inherently selfish because it deprives everyone else of possible learning value. Coding Help topics rarely go off topic or become derailed, so there's no reason to preemptively lock it, and even if they do devolve into a fight or something that provides a medium for learning between the engaged parties as whoever is correct will teach the incorrect person the proper ways. Only in the case of active informationless mudslinging is locking help topics really appropriate.

[Night_Hawk]

Never lock Coding Help topics. Not infrequently are incorrect answers corrected, inefficient answers improved, or more general knowledge added on topics. This results in a better learning environment for everyone: the OP who needs the help, future coders who find your topic through searches, and Coding Help perusers who don't have a specific question but are soaking up the available information on the board. Locking the topic is inherently selfish because it deprives everyone else of possible learning value. Coding Help topics rarely go off topic or become derailed, so there's no reason to preemptively lock it, and even if they do devolve into a fight or something that provides a medium for learning between the engaged parties as whoever is correct will teach the incorrect person the proper ways. Only in the case of active informationless mudslinging is locking help topics really appropriate.

Alright alright!!! I didn't know ok?

[$trinick]

Alright alright!!! I didn't know ok?

That wasn't meant to be aggressive, it was meant to be informational. Sorry if it came off that way.