Custom Scripts......

[Spartan-117]

Good morning, aftrnoon, evening or watever is in where are you.
There is some triggers with this trigger action "Custom Script".
1) What is that???

2)I put this Custom Scripts in my WE and it disable my triggers.

Thanks for the attention....And the pacience......

 

[jk2pach]

1-It's a way to use a jass line of code
2-Cause then your custom scripts are false?

 

[Spartan-117]

I download a map with then the bag sistem from here....
It only has good comments.

 

[Pharaoh_]

2) You need to copy every variable in your map, so that the Custom script responds exactly to. There is a possibility that the custom script contains data from the map's header. Make sure you copy and paste everything from it.

 

[defskull]

The function of Custom Script is writing JASS language (not user-friendly programming language) OR to clean leaks in GUI
This action requires KNOWLEDGE about the syntax of the language and it is VERY sensitive (one false typo, and you're out~)
The cause of error in your trigger because you must've wrote an undefined Custom Script that ended up as a null result which can produce system errors on your map or cause your trigger to malfunction
I believe that Custom Script action also supports a non-leak trigger (I guess..)
All the language seems to clean the leak itself

 

[MGCǂSpectre]

and whenever you use variables you always put a custom script to destroy these variables to prevent leaks in your map that may lead to lag in the map if too much memory is leaked.

Example: you set a group, you put a : Custom script: call DestroyGroup(udg_*name of your group variable*)
you set a point variable you put a: Custom script: call RemoveLocation(udg_*name of point variable*)

And im not sure if you have to destroy a Real variable as I dont know a code for reals

 

[Pharaoh_]

Reals and Integers don't leak.

 

[defskull]

Regions do leak, right ?
And the leak-clean ritual is performed by: call RemoveRect(udg_var)
Also, I have seen this: ForceDestroy(udg_var), well, what is it ?
AND 1 more thing, do Player Group leaks ?

 

[Pharaoh_]

Your last question answers your previous one: DestroyForce() (not ForceDestroy()), cleans the leak of Player Groups.

 

[Berb]

The function of Custom Script is writing JASS language (not user-friendly programming language) OR to clean leaks in GUI
This action requires KNOWLEDGE about the syntax of the language and it is VERY sensitive (one false typo, and you're out~)

JASS is a very user-friendly programming language. Pretty much every keyword must be typed out in full, to extend its readability. It should be fairly straight forward what JASS code does (if it is written properly) just because all of the keywords are structured almost like a sentence.

function AddTwoIntegers takes integer a, integer b returns integer
    return a + b
endfunction

There's a really straight forward example, and of course you can't make any mistakes these commands are translated to machine-code; I don't know how you would expect your code to operate properly with typos and incorrect syntax every where. Not even Visual Basics allows you to mistype words.

 

[defskull]

My words meant for User-Friendly were: User can see WHAT is actually going on in that programming, meaning it has icons / straight-forward words / commands / directories / etc
THESE are the words that best describes USER-FRIENDLY

 

[PurplePoot]

My words meant for User-Friendly were: User can see WHAT is actually going on in that programming, meaning it has icons

Icons are required to make something readable? Do you put icons in your essays?

straight-forward words

You mean like function, destroy group, integer, etc? These are very straight forward.

commands

You mean like function calls and variable declarations/sets?

directories

You mean like functions?

THESE are the words that best describes USER-FRIENDLY

No, they really aren't.

--

The "do I destroy it?" flowchart (in list form!):

• Is it an object (everything but integer, real, boolean, string, code)? If yes, go to B. Otherwise go to E.
• Did you create it in this function? If yes, go to C. Otherwise go to E.
• Do you or the user need to use it after this function? If no, go to D. Otherwise go to E.
• You need to destroy it.
• You don't need to destroy it.

 

[defskull]

*hands down*