Save and Apply

[Twinny]

When working with scripts in RC, there are times when you'd rather just edit a script and save it rather than have it save and run. This could be a nice addition to RC.

[Clarification]: Changing a script with calling the onCreated event

[Inverness]

Originally Posted by Twinny

there are times when you'd rather just edit a script and save it rather than have it save and run.

No, not really.
:D

[Twinny]

Originally Posted by Inverness

No, not really.

I made a script on UN which, when onCreated was called, saved all the players positions, updated the gmap then warped them back to where they were. I wanted to change some of the code without calling the onCreated event

[cbk1994]

Originally Posted by Twinny

I wanted to change some of the code without calling the onCreated event

2BAD4U

[Inverness]

ispaused = true;

Move your stuff out of the onCreated() function and have the new function check if its been run already.

[Inspiration]

Couldn't you just comment out the part of the script you did not want to run?

[Horrified]

SO MANY CHOICES.

PHP Code:

/*

These are comment brackets!

*/

//These are comment lines!

function testPlz(params) //this is a function not executed on default!
{ 
} 


[DustyPorViva]

Then everything inside the onCreated would not function for those who recieve the weapon afterwards, unless he removed the captions and saved it... thus negating the whole process. So there aren't really SO MANY CHOICES.
Only thing I can think of is moving everything outside of the onCreated() to its own function, and calling the function only when it hasn't been called before... which would involved setting something to the player(or in a DBNPC) the first time it is called and checking it, and which would also involve clearing said something if you actually NEED the onCreated() to be called for all players again.

[Twinny]

A wicked part of my script is the ability to simply press reset on the DBNPC to run the script. Makes it alot easier for the less script savvy.

Another example. You have a weapon which creates a gui when onCreated is called clientside. Instead of causing this weapon to popup the gui (causing deaths and angry players), you could just edit the code and save the script. It may be a bit more difficult for clientside though. Id would still have to be sent but not applied.

You can argue that there are many different ways to do this (like calling creategui() from a seperate weapon) but it's just an idea.

[Crow]

You could make a weapon which calls something similar to onCreated() when the weapon itself is created, so you can edit the code of the other weapons, but I have to agree, something like that would be nice ;o

[Inverness]

There is is no reason to be creating GUIs in the onCreated() section unless they're invisible or part of the HUD.

The mechanics of the script updating process don't need to be changed when its rather easy to have a workaround to some commands being called everytime onCreated() is.

For weapons on the serverside, a simple this.variable can be used since when you update weapons, the serverside variables are not cleared.

On clientside the weapon object is deleted and recreated so variables are lost, saving to the player object would be best way for this.