FarmMod

[Orthone]

You're handicapped if you really think you need an "onActivate event" to make it be called.

That would have nothing to do with that, think about what your saying and if it sounds right and would be true.

It is possible that bricks ignore being clicked unless they actually have an event for them to be clicked.

[Ad Bot]

[Headcrab Zombie]

You're handicapped if you really think you need an "onActivate event" to make it be called.

It's generally a bad idea to call someone who's trying to help you handicapped.

Anyways, I do remember you used to need an onActivate event for the onActivate function to be called

[Superb]

Wow, package player activate stuff, shoot a ray cast from the player, if the raycast is the brick you want, execute code?

[cheese6]

I am completly and utterly sorry, someone has gotten into my account. I have changed my password and all is good

Have a good day
:D

[Uristqwerty]

...
(which I believe also requires an onActivate event on the brick for it to even be called)
...
and some sort of vector that I'm not sure what it means

Did a bit of testing, and with freshly placed, event-free blocks, onActivate was indeed called, and the last argument appeared to the the player's eye vector at the time.

After a few more quick tests, it appears that onActivate is called every time (though I may be missing an obscure corner case or two. Unlikely.), but ProcessInputEvent is only called if the block has at least one input event, which does the actual work of checking any quotas and if there even is a matching event on the block.

So, from my limited empirical evidence, onActivate is reliable regardless of what events the brick actually has.

[Freebuild]

Yeah. OnActivate is already a function, the event doesn't really have a function like that. Its a little different.

[Headcrab Zombie]

Did a bit of testing, and with freshly placed, event-free blocks, onActivate was indeed called, and the last argument appeared to the the player's eye vector at the time.

After a few more quick tests, it appears that onActivate is called every time (though I may be missing an obscure corner case or two. Unlikely.), but ProcessInputEvent is only called if the block has at least one input event, which does the actual work of checking any quotas and if there even is a matching event on the block.

So, from my limited empirical evidence, onActivate is reliable regardless of what events the brick actually has.

Yeah I guess I was thinking of onPlayerTouch

[Freebuild]

That still doesn't matter, any default event like that is already a function for the brick data, the event side a whole side of other crap.

[Freebuild]

Did a bit of testing, and with freshly placed, event-free blocks, onActivate was indeed called, and the last argument appeared to the the player's eye vector at the time.

After a few more quick tests, it appears that onActivate is called every time (though I may be missing an obscure corner case or two. Unlikely.), but ProcessInputEvent is only called if the block has at least one input event, which does the actual work of checking any quotas and if there even is a matching event on the block.

So, from my limited empirical evidence, onActivate is reliable regardless of what events the brick actually has.

You know, I like you. You're not acting like a handicap, not posting drama on this topic, and you're actually helping me. You're one of the rare people I actually find around on the internet. And you're pretty smart.

[Destiny/Zack0Wack0]

You know, I like you. You're not acting like a handicap, not posting drama on this topic, and you're actually helping me. You're one of the rare people I actually find around on the internet. And you're pretty smart.

You know, I think you're a moron. You're acting like a handicap, posting drama in this topic when someone was trying to help you (Headcrab DID NOT say anything rude to you, you came back at him harsh for no reason when he just tried to help). You're one of the most common tier of person on the internet. And you're a dumbass.

Do not come to Coding Help to attack people when they try to help you. There was a point in time when onActivate was not called when there were no events set, so obviously it's been changed.

That still doesn't matter, any default event like that is already a function for the brick data, the event side a whole side of other crap.

No, they are incredibly related.