Watch
-
Add Favorite
At the very top of the es_rpgmaker.txt file there is something called 'block configure' there are comments detailing what each of the vars do. Read through them to find what each one does.
Creating Characters:
The Outline for creating a character in the es_rpgmc_db.txt is the following:
In this example the name is 'Werewolf'
First let me explain the weaponrestricttype, weapons, and numberofweapons lines
weaponrestricttype determins whether you want to character to only be able to use the listed weapons or not use the restricted weapons.
If set to 'allowonly' then they will only be able to hold weapons you list
These are three optional lines you may include when building a character to limit the types of weapons they are allowed to hold
Example 2:
Seperate each weapon name with a ',' and then set the numberofweapons to the number of weapons in your weapons value
In this example 'weaponrestricttype' is set to 'restrict' so this character will not be able to hold the restricted weapon but he will be able to hold all others
Next value 'spawn' is also an optional value. This is a command that is run when the users spawns reguardless of level.
After 'spawn' comes the value 'requiredlevel' this is the minimum level the user must have in at least one other character before they are able to play as this character.
Each skill you give a character needs 3 values each value starts with the level you want the skill gained.
cfg - when you want the skill run(see below for events skills can trigger on)
description - this is what shows up in the !info menu, keep it short
cmd - What you want to run when this skill triggers
The possible different cfgs for skills are:
Runs when ever user hits someone with an attack
attacker
Runs when ever user gets hit
victim
Runs whenever the users spawns
spawn
Runs whenever the users says something
say
Runs when the user jumps
jump
Runs when the user dies.
victimdeath
Runs when the user kills someone
attackerkill
Runs when a user gets hit by a flashbang
blind
You can make any number of level skills for each character
Custom RPG Maker Commands:
Deals damage to the target from the attacker:
rpg_damage Usage: rpg_damage
Gives the user xp into their current class == to the given amount
rpg_givexp Usage: rpg_givexp
Gives the user level into their current class == to the amount stated
rpg_levelup Usage: rpg_levelup
Stops a player from walking for the x seconds
rpg_stun Usage: rpg_stun
Blacks out a the targets screen for x seconds
rpg_blind Usage: rpg_blind
Makes a player immune to damage for x seconds
rpg_god Usage: rpg_god
Burn the target for x seconds
rpg_burn Usage: rpg_burn
Affects the players gravity by the amount, negative numbers lower it postive raise it
rpg_gravity Usage: rpg_gravity
Affects the players speed by the amount, positive raise speed negative lower it
rpg_speed Usage: rpg_speed
Sets the player to the color of you choice
rpg_color Usage : rpg_color
Colors that are supported:
#blue
#green
#red
#teal
#yellow
#purple
#black
#pink
#orange
#normal (standard colors)
Sets the target to the visiblity % you choose
rpg_visible Usage: rpg_visible
Turns a user back to 100 visible for the duration amount of seconds, 0 will leave them visible until you run rpg_stealth_on
rpg_stealth_off Usage: rpg_stealth_off
Colors a users base on their color value which is affected by the rpg_color command
rpg_stealth_on Usage: rpg_stealth_on
If value is postive adds health if it is negative subtracts health
rpg_health Usage: rpg_health
This command may raise some questions with the last value 'Affect Maxhealth' there in an internal var in the RPGTemp keygroup for each users storing a value known as 'maxhealth' if you use the rpg_health command with a 0 at the end and the value you are boosting the health by would put the user beyond his or her 'maxhealth' they are instead set to their 'maxhealth'. This makes it useful when 'healing' players
If value is postive adds cash if it is negative subtracts cash
rpg_cash Usage: rpg_cash
Blurs your targets screen so they can't see well for x seconds
rpg_drug Usage: rpg_drug
Sets the model of a user
rpg_model Usage: rpg_model
These following three commands are not 100% supported yet and may or may not work:
Gives your taget health every so many seconds
rpg_regen Usage: rpg_regen
Slowly drains the target every x seconds for the duration
rpg_drain Usage: rpg_drain
Heals the target and all allies with the radius around him at every delay amount of seconds
rpg_arearegen Usage: rpg_arearegen
Adding Admins(es_rpgadmins_db.txt):
Admin Key:
Just add a key like this one but change the steamid to the ID of the player you wish to have adminship. Admins can kick, ban, and give levels. The name value is no used for anything within the mod. It is just for keeping track of which id belongs to who.
Adding Items(es_rpgshop_db.txt):
The three needed lines are:
cost - How much money the item costs
cfg - When the item's effect triggers
cmd - What it runs when the item triggers
description - What it tells the user the item does when it is purchased
Items in the shop can use all the same cfg's as character skills plus the 'onbuy' cfg which means the item will run when it is purchased and then dissapear not holding a slot.(Good for items the you can purchase to gain xp or to gain health back.)
Extra Shop example:
*Note: When using the 'onbuy' cfg that the userid of the person purchasing the item is: server_var(_popup_userid) not event_var(userid)
Shop example 3:
Note the extra value 'onbuycmd' this line runs only when the item is purchased and then never again. This way you are able to have an item that would say only happen on spawn also happen when it is purchased like my ring of regeneration does in this example.
Also it is a good idea to include the cost of the item at the end of its name so they users will know how much it costs
Note for advance users:
There is a temporary keygroup you can save values to that do not need to be permant for skills, (for such as numbering the amount of times something can be used) The keygroup is called RPGTemp each player has a key in the RPGTemp key that is their userid
A var called 'rpg_random' can be used for es_rand checks to generate random numbers
Also there are 5 vars with the following names: rpg_var1. rpg_var2, rpg_var3, rpg_var4, and rpg_var5 that are not used that can be used in skills for character. Also there are 3 vars: rpg_x, rpg_y, and rpg_z to use for locations.(and then if you need a second set these are also included: rpg_x2, rpg_y2, and rpg_z2)
Now the new stuff(And quicker/more flexiable!) RPGMaker Python Guide:
These are the values at the top of your rpgmaker.py that will determin many things for you read the comments above each for more info:
Creating Characters:
The Outline for creating a character in the rpgmc.py is the following:
A few key things to note:
First - Notice the , at the end of each line if there is a line following it. This is important if it is not there it will feed you an error message.
Second - All character entries much have a 'Menu Place' value.
Option values you can put in the main key of your character for different effects:
'weapon restrict' and 'restriction type' these will limmit the weapons your character is able to use. 'restriction type' can have one of two values 'restrict' or 'allow only' if set to restrict the character will not be able to hold the listed guns, if set to allow only they will only be able to hold the listed guns.
'required level' - this determines the level a user must have in at least one other character before being able to play as this character.
'team allowed' - setting to 2 will make it so you may only play the character as a terrorist, setting it to a 3 will do the same for CT
Next lets look at this inside point:
The number is the level need in the character to obtain the skill, then there are 4 different values within the skill:
'name' - this can be anything you want it is what you want to call your skill
'cfg' - this determines when the skill cmd will be run values can be - spawn, jump, say, attacker, victim, death, kill, blind
'description' - this is a broad description of the skill your users will see when they look it up in game
'cmd' - this is code that will be run when cfg activates, it use ESS(event scripts shell) code. If you need to use code that needs more than a single line you can store it in addons/eventscripts/rpgmaker/skills/es_skills.txt and then call it up using an es_doblock rpgmaker/skills/BLOCK_NAME
Next these are a few option values you may include in the top level of your character key they are different things that can run extra commands without the user neededing any extra levels:
'spawn' : 'commands to run'
'jump' : 'commands to run'
'victim' : 'commands to run'
'attacker' : 'commands to run'
'kill' : 'commands to run'
'death' : 'commands to run'
'blind' : 'commands to run'
'say' : 'commands to run'
Custom rpg commands you have access to use in your cmd's
'rpg damage '
'rpg health '
'rpg givexp '
'rpg stun '
'rpg god '
'rpg blind '
'rpg burn '
'rpg gravity or rpg gravity set '
'rpg speed '
'rpg color '
Colors that are supported:
#blue
#green
#red
#teal
#yellow
#purple
#black
#pink
#orange
#normal (standard colors)
'rpg visible or rpg visible math '
'rpg stealth on '
'rpg stealth off '
'rpg cash '
'rpg drug '
'rpg model '
'rpg regen '
'rpg arearegen '
These commands are used for storing data kinda like keygroups, only they provide direct access to a python dic(faster than keygroups) and they already contain a userkey(by userid) for each user in the server. - Note this is perminat storage for information
'rpg set '
'rpg get '
'rpg cleanuserfile'
Adding items(rpgshop.py):
The three needed lines are:
menu place - Where the item will appear in the menu
cost - How much money the item costs
cfg - When the item's effect triggers
cmd - What it runs when the item triggers
description - What it tells the user the item does when it is purchased
Items in the shop can use all the same cfg's as character skills plus the 'onbuy' cfg which means the item will run when it is purchased and then dissapear not holding a slot.(Good for items the you can purchase to gain xp or to gain health back.)
Extra Shop example:
*Note: When using the 'onbuy' cfg that the userid of the person purchasing the item is: server_var(_popup_userid) not event_var(userid)
Shop example 3:
Note the extra value 'onbuycmd' this line runs only when the item is purchased and then never again. This way you are able to have an item that would say only happen on spawn also happen when it is purchased like my ring of regeneration does in this example.
Lastly let's configure your admins Line 38 in the rpgmaker.py -
#The list of steamid's in here determines your users whom can access the rpg commands through chat
adminlist = ['STEAM_ID_LAN', 'STEAM_0:0:7663580']
Add your steamids to you admin list and you are done! With version 2 there is no longer a full admin menu.(If you are looking for a full amdin menu check out my j3ffpluggin: http://addons.eventscripts.com/addons/view/j3ffpluggin) Now admins simply have full access to all rpg commands via typing them into chat. for instance if one of your admins types rpg cleanuserfile in chat it will clean out your user file for you.
Vars for storing information in:
rpg_random
rpg_var1
rpg_var2
rpg_var3
rpg_var4
rpg_var5
rpg_var6
rpg_var7
rpg_var8
rpg_var9
rpg_var10
~J3ff
Small bug fixes, updates to the included mod!
~J3ff
( Previous Versions )
Description
Information for ES1.5 Version for RPGMaker:At the very top of the es_rpgmaker.txt file there is something called 'block configure' there are comments detailing what each of the vars do. Read through them to find what each one does.
block configure |
Creating Characters:
The Outline for creating a character in the es_rpgmc_db.txt is the following:
"Werewolf" |
In this example the name is 'Werewolf'
First let me explain the weaponrestricttype, weapons, and numberofweapons lines
weaponrestricttype determins whether you want to character to only be able to use the listed weapons or not use the restricted weapons.
If set to 'allowonly' then they will only be able to hold weapons you list
These are three optional lines you may include when building a character to limit the types of weapons they are allowed to hold
Example 2:
"Vampire" |
Seperate each weapon name with a ',' and then set the numberofweapons to the number of weapons in your weapons value
In this example 'weaponrestricttype' is set to 'restrict' so this character will not be able to hold the restricted weapon but he will be able to hold all others
"Werewolf Tracker" |
Next value 'spawn' is also an optional value. This is a command that is run when the users spawns reguardless of level.
After 'spawn' comes the value 'requiredlevel' this is the minimum level the user must have in at least one other character before they are able to play as this character.
Each skill you give a character needs 3 values each value starts with the level you want the skill gained.
cfg - when you want the skill run(see below for events skills can trigger on)
description - this is what shows up in the !info menu, keep it short
cmd - What you want to run when this skill triggers
The possible different cfgs for skills are:
Runs when ever user hits someone with an attack
attacker
Runs when ever user gets hit
victim
Runs whenever the users spawns
spawn
Runs whenever the users says something
say
Runs when the user jumps
jump
Runs when the user dies.
victimdeath
Runs when the user kills someone
attackerkill
Runs when a user gets hit by a flashbang
blind
You can make any number of level skills for each character
Custom RPG Maker Commands:
Deals damage to the target from the attacker:
rpg_damage Usage: rpg_damage
Gives the user xp into their current class == to the given amount
rpg_givexp Usage: rpg_givexp
Gives the user level into their current class == to the amount stated
rpg_levelup Usage: rpg_levelup
Stops a player from walking for the x seconds
rpg_stun Usage: rpg_stun
Blacks out a the targets screen for x seconds
rpg_blind Usage: rpg_blind
Makes a player immune to damage for x seconds
rpg_god Usage: rpg_god
Burn the target for x seconds
rpg_burn Usage: rpg_burn
Affects the players gravity by the amount, negative numbers lower it postive raise it
rpg_gravity Usage: rpg_gravity
Affects the players speed by the amount, positive raise speed negative lower it
rpg_speed Usage: rpg_speed
Sets the player to the color of you choice
rpg_color Usage : rpg_color
Colors that are supported:
#blue
#green
#red
#teal
#yellow
#purple
#black
#pink
#orange
#normal (standard colors)
Sets the target to the visiblity % you choose
rpg_visible Usage: rpg_visible
Turns a user back to 100 visible for the duration amount of seconds, 0 will leave them visible until you run rpg_stealth_on
rpg_stealth_off Usage: rpg_stealth_off
Colors a users base on their color value which is affected by the rpg_color command
rpg_stealth_on Usage: rpg_stealth_on
If value is postive adds health if it is negative subtracts health
rpg_health Usage: rpg_health
This command may raise some questions with the last value 'Affect Maxhealth' there in an internal var in the RPGTemp keygroup for each users storing a value known as 'maxhealth' if you use the rpg_health command with a 0 at the end and the value you are boosting the health by would put the user beyond his or her 'maxhealth' they are instead set to their 'maxhealth'. This makes it useful when 'healing' players
If value is postive adds cash if it is negative subtracts cash
rpg_cash Usage: rpg_cash
Blurs your targets screen so they can't see well for x seconds
rpg_drug Usage: rpg_drug
Sets the model of a user
rpg_model Usage: rpg_model
These following three commands are not 100% supported yet and may or may not work:
Gives your taget health every so many seconds
rpg_regen Usage: rpg_regen
Slowly drains the target every x seconds for the duration
rpg_drain Usage: rpg_drain
Heals the target and all allies with the radius around him at every delay amount of seconds
rpg_arearegen Usage: rpg_arearegen
Adding Admins(es_rpgadmins_db.txt):
Admin Key:
"STEAM_0:0:7663580" |
Just add a key like this one but change the steamid to the ID of the player you wish to have adminship. Admins can kick, ban, and give levels. The name value is no used for anything within the mod. It is just for keeping track of which id belongs to who.
Adding Items(es_rpgshop_db.txt):
"Silver Stake ($1600)" |
The three needed lines are:
cost - How much money the item costs
cfg - When the item's effect triggers
cmd - What it runs when the item triggers
description - What it tells the user the item does when it is purchased
Items in the shop can use all the same cfg's as character skills plus the 'onbuy' cfg which means the item will run when it is purchased and then dissapear not holding a slot.(Good for items the you can purchase to gain xp or to gain health back.)
Extra Shop example:
"Potion of Xp ($5000)" |
*Note: When using the 'onbuy' cfg that the userid of the person purchasing the item is: server_var(_popup_userid) not event_var(userid)
Shop example 3:
"Ring of Regeneration ($3000)" |
Note the extra value 'onbuycmd' this line runs only when the item is purchased and then never again. This way you are able to have an item that would say only happen on spawn also happen when it is purchased like my ring of regeneration does in this example.
Also it is a good idea to include the cost of the item at the end of its name so they users will know how much it costs
Note for advance users:
There is a temporary keygroup you can save values to that do not need to be permant for skills, (for such as numbering the amount of times something can be used) The keygroup is called RPGTemp each player has a key in the RPGTemp key that is their userid
A var called 'rpg_random' can be used for es_rand checks to generate random numbers
Also there are 5 vars with the following names: rpg_var1. rpg_var2, rpg_var3, rpg_var4, and rpg_var5 that are not used that can be used in skills for character. Also there are 3 vars: rpg_x, rpg_y, and rpg_z to use for locations.(and then if you need a second set these are also included: rpg_x2, rpg_y2, and rpg_z2)
Now the new stuff(And quicker/more flexiable!) RPGMaker Python Guide:
These are the values at the top of your rpgmaker.py that will determin many things for you read the comments above each for more info:
|
Creating Characters:
The Outline for creating a character in the rpgmc.py is the following:
|
A few key things to note:
First - Notice the , at the end of each line if there is a line following it. This is important if it is not there it will feed you an error message.
Second - All character entries much have a 'Menu Place' value.
Option values you can put in the main key of your character for different effects:
'weapon restrict' and 'restriction type' these will limmit the weapons your character is able to use. 'restriction type' can have one of two values 'restrict' or 'allow only' if set to restrict the character will not be able to hold the listed guns, if set to allow only they will only be able to hold the listed guns.
'required level' - this determines the level a user must have in at least one other character before being able to play as this character.
'team allowed' - setting to 2 will make it so you may only play the character as a terrorist, setting it to a 3 will do the same for CT
Next lets look at this inside point:
'skills' : |
The number is the level need in the character to obtain the skill, then there are 4 different values within the skill:
'name' - this can be anything you want it is what you want to call your skill
'cfg' - this determines when the skill cmd will be run values can be - spawn, jump, say, attacker, victim, death, kill, blind
'description' - this is a broad description of the skill your users will see when they look it up in game
'cmd' - this is code that will be run when cfg activates, it use ESS(event scripts shell) code. If you need to use code that needs more than a single line you can store it in addons/eventscripts/rpgmaker/skills/es_skills.txt and then call it up using an es_doblock rpgmaker/skills/BLOCK_NAME
Next these are a few option values you may include in the top level of your character key they are different things that can run extra commands without the user neededing any extra levels:
'spawn' : 'commands to run'
'jump' : 'commands to run'
'victim' : 'commands to run'
'attacker' : 'commands to run'
'kill' : 'commands to run'
'death' : 'commands to run'
'blind' : 'commands to run'
'say' : 'commands to run'
Custom rpg commands you have access to use in your cmd's
'rpg damage '
'rpg health '
'rpg givexp '
'rpg stun '
'rpg god '
'rpg blind '
'rpg burn '
'rpg gravity or rpg gravity set '
'rpg speed '
'rpg color '
Colors that are supported:
#blue
#green
#red
#teal
#yellow
#purple
#black
#pink
#orange
#normal (standard colors)
'rpg visible or rpg visible math '
'rpg stealth on '
'rpg stealth off '
'rpg cash '
'rpg drug '
'rpg model '
'rpg regen '
'rpg arearegen '
These commands are used for storing data kinda like keygroups, only they provide direct access to a python dic(faster than keygroups) and they already contain a userkey(by userid) for each user in the server. - Note this is perminat storage for information
'rpg set '
'rpg get '
'rpg cleanuserfile'
Adding items(rpgshop.py):
'Belt of Strength' : |
The three needed lines are:
menu place - Where the item will appear in the menu
cost - How much money the item costs
cfg - When the item's effect triggers
cmd - What it runs when the item triggers
description - What it tells the user the item does when it is purchased
Items in the shop can use all the same cfg's as character skills plus the 'onbuy' cfg which means the item will run when it is purchased and then dissapear not holding a slot.(Good for items the you can purchase to gain xp or to gain health back.)
Extra Shop example:
'Potion of Healing' : |
*Note: When using the 'onbuy' cfg that the userid of the person purchasing the item is: server_var(_popup_userid) not event_var(userid)
Shop example 3:
'Ring of Regeneration' : |
Note the extra value 'onbuycmd' this line runs only when the item is purchased and then never again. This way you are able to have an item that would say only happen on spawn also happen when it is purchased like my ring of regeneration does in this example.
Lastly let's configure your admins Line 38 in the rpgmaker.py -
#The list of steamid's in here determines your users whom can access the rpg commands through chat
adminlist = ['STEAM_ID_LAN', 'STEAM_0:0:7663580']
Add your steamids to you admin list and you are done! With version 2 there is no longer a full admin menu.(If you are looking for a full amdin menu check out my j3ffpluggin: http://addons.eventscripts.com/addons/view/j3ffpluggin) Now admins simply have full access to all rpg commands via typing them into chat. for instance if one of your admins types rpg cleanuserfile in chat it will clean out your user file for you.
Vars for storing information in:
rpg_random
rpg_var1
rpg_var2
rpg_var3
rpg_var4
rpg_var5
rpg_var6
rpg_var7
rpg_var8
rpg_var9
rpg_var10
~J3ff
Version Notes For Version v1.0 and Python Beta0.55 (Announce this update)
Updated on: 2008-01-27 23:23:48 ESTSmall bug fixes, updates to the included mod!
~J3ff
( Previous Versions )
Find Servers
Servers running this addon.
Addon Details
Upload Addon