They shouldn't, which makes the whole thing highly unusual. I know for a fact that using "player"->Stuff works in regular and MWSE scripts. It's possible it was interacting with something else and breaking the VM or MWSE, but how... odd odd.


Not a fan of its syntax.


If you want to use OnActivate more than once or store it for some odd reason, just do:

Set wasActivated To OnActiiveif ( wasActivated )    ...

That will store the value and let you work with it as you like (including resetting it part way through your script).

Edit: Oh, and there's also a bug with the default MWScript compiler (CS), where you can start a block with elseif (or possibly else) and it won't give any errors, but can break in the game. Be careful with that.

Try it out. I think the structure would work, but as I explain later, I think the activate is the problem. RAK's examples would work fine, but I want to point out that you can use else after and endif. Anything after an else will only be executed if all previous conditions are false. MWSE has a good explanation of it.


I mean that the problem seems to lie with activate and adding the item to inventory in both cases.


It should. You should try it. I don't see much reason to use activate unless it isn't going to go into your inventory. I suspect the problem is that the item is added to inventory and then tried to activate from within the inventory. I think activate doesn't work within the inventory, but I could be wrong.

That makes sense, how can it activate it when it's already in your inventory? (hypothetical question). But Everything seem's to run smoothly now, of course I'll probably be back in an hour with some new horrendous over simplified problem. Oh well, I'm trying to learn atleast haha =p

It's quite silly that I did not think of this, especially since I should know this. If you still need, you can just click on something with the console open, and type "getdistance, player".
So obvious... :facepalm:

:facepalm: Thanks for the tip though, that will be useful