A quick necro post on how to read and understand the instructions:
CODE
add_faction("name", max_value, *start_value, "*help_text", "*pic", *display)
This will add a faction to the system. Value's that must be insert are;
- name (name of the faction)
- max_value (the heighest amount of reputation the faction can get)
Value's that could be insert for a personal touch are;
- start_value (the reputation of the faction when entered in the system)
- help_text (the text that will be displayed when the faction is selected
in the menu (add ## to go the second line))
- pic (the picture that can be shown in the menu)
- display (option to show the faction in the faction-window or not)
So the first line is always the string you need to put in the call-script event block.
The parts inbetween the brackets are the variables that determin how the script will opperate.
The variables with quotes, are strings.
If a variable has a asterix (* star *) before it, it meens that these variables are optional and don't need to be added.
They will be using the default values.
!!Though, if you want to have a variable set, you must always set all the previous variables as well (in the example, if you want to set the "help_test" you will also need to set the optional "start_value").
The second line holds a short description of the function.
Values that must be inserted are the ones without a asterix (* star *) and are allways the first values in the functioncall (if any).
The next lines will describe for each variable and what it stands/what it will do (the part in brackets).
After the variables, the optional variables are described just as the non-optional ones.
Now the function calls are sorted on functionalty and are obviously labeled with a block that looks like this
CODE
>>>>>>>>>>>>>>>>
Faction startup:
>>>>>>>>>>>>>>>>
Where the text in the middle displays the category/functionality.
Now the naming can be a bit odd at some places, but if you read the functions themselfs, you might understand the decisions I made on the category naming.
Conditions and other extra features have their own section in the script's description and are read pretty much the same as the function calls (only applied on a different location).
About the demo, I'm not sure if I still have it somewhere.
I might need to dust of my old laptop and see if I still have it there.
I won't be doing this soon though, so my appologies for this.
I hope this explanation will help people to understand the descriptions (or rather encryptions?) in the future.
Greatzz,
SojaBird.
A quick necro post on how to read and understand the instructions:
CODE
add_faction("name", max_value, *start_value, "*help_text", "*pic", *display)
This will add a faction to the system. Value's that must be insert are;
- name (name of the faction)
- max_value (the heighest amount of reputation the faction can get)
Value's that could be insert for a personal touch are;
- start_value (the reputation of the faction when entered in the system)
- help_text (the text that will be displayed when the faction is selected
in the menu (add ## to go the second line))
- pic (the picture that can be shown in the menu)
- display (option to show the faction in the faction-window or not)
So the first line is always the string you need to put in the call-script event block.
The parts inbetween the brackets are the variables that determin how the script will opperate.
The variables with quotes, are strings.
If a variable has a asterix (* star *) before it, it meens that these variables are optional and don't need to be added.
They will be using the default values.
!!Though, if you want to have a variable set, you must always set all the previous variables as well (in the example, if you want to set the "help_test" you will also need to set the optional "start_value").
The second line holds a short description of the function.
Values that must be inserted are the ones without a asterix (* star *) and are allways the first values in the functioncall (if any).
The next lines will describe for each variable and what it stands/what it will do (the part in brackets).
After the variables, the optional variables are described just as the non-optional ones.
Now the function calls are sorted on functionalty and are obviously labeled with a block that looks like this
CODE
>>>>>>>>>>>>>>>>
Faction startup:
>>>>>>>>>>>>>>>>
Where the text in the middle displays the category/functionality.
Now the naming can be a bit odd at some places, but if you read the functions themselfs, you might understand the decisions I made on the category naming.
Conditions and other extra features have their own section in the script's description and are read pretty much the same as the function calls (only applied on a different location).
About the demo, I'm not sure if I still have it somewhere.
I might need to dust of my old laptop and see if I still have it there.
I won't be doing this soon though, so my appologies for this.
I hope this explanation will help people to understand the descriptions (or rather encryptions?) in the future.
Greatzz,
SojaBird.