HeRO Wiki - User contributions [en]

Talk:Server rules

2010-04-25T15:06:02Z

Revenant: New page: ==English== To play this server everyone must be able to understand and write comprehensible English. If a GM addresses you, you must be able to understand them, answer appropriately and c...

==English==
To play this server everyone must be able to understand and write comprehensible English. If a GM addresses you, you must be able to understand them, answer appropriately and comply to their requests. Those whose have problems using English should make their best attempts; we're obviously not asking for absolute fluency, but instead enough to allow basic communication.

==Be respectful to everyone==
Insulting other players or staff via swearing, general discrimination, racism, sexism or other offending ways may result in punishment. This applies to absolutely everyone, including those using the Main chat channel in-game. Do not deliberately interfere with other players' gameplay outside of PvP/GvG maps in a negative manner, such as healing/buffing/protecting monsters, killstealing, etc, unless explicitly requested to by the player in question. Adhere to the MVP Domination rules when dealing with MVPs.

==Use English on Main==
You must use English on the Main chat channel. Outside of main, you may use any languages, such as through party or guild chat.

==Do Not Spoil Custom Quests in Public==

Details/Locations on any heRO custom additions or quests are not to be mentioned using @main or public forums. However, players are allowed to ask questions regarding these heRO custom quests in public, but answers must be given through other communication mediums, such as Pms or in private guild forums.

==Restriction in Naming Conventions==
Below is the list of letters/numbers/symbols allowed in creation of a character's name. Make sure to also choose a name that is appropriate (aka no slander, profanity, insult, etc!). Player names who do not respect this rule will be sent to jail until a new name is chosen, the character can also be deleted if the name is too offensive. Using similar name as an existing player to carry out malicious act or to purposely ruin the player's reputation is also a punished offense.

 Allowed characters:
 ABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890_-~^().:!?@$%&+='

 You cannot make character whose name starts with "GM-", "GM", "Event-" or "Event" (or similar variations, such as capitalization). These are reserved for GM use.

 The "appropriate" rule also goes for anything else a player has to choose a name for, such as party name, guild name, guild title, pet/homunculus name, shop name, chat room name, etc.

==Kill Steal (KS) for Non-MvP Monsters==
Do not hit a monsters that "belongs" to another players. Any monster that is attacking/chasing the player, or if the player is also attacking the target in question, counts as "belonging" to that player. KS rules do not apply in any public DB room or any GM hosted events unless stated otherwise by the GMs.

==MvP Domination Rule==
 All of the MVPs are free to be attacked by any player, included MVPs summoned by Quest. However, the first one/first party present at a MvP will be considered the "dominating party." To elaborate, this means engaging the MvP so that either the player/party are attacking the MvP, or the MvP is attacking (or clearly chasing) that player/party.

 Participation in MVP battles must not interfere in the strategy that the dominating player/party is using and must try to adhere to it.

 Based on the above, the following are disallowed:
*Your presence in killing the MVP interferes with the strategy of the dominating player/party
*Your attacks on the MVP repeatedly cause the use of "Teleport" beyond the frequency of accidental human error.
*Your interference causes the death of the others competing for the MVP if you bring alien mobs to the MVP or don’t know how to control the slaves of the MVP.
*Your attack causes no effect or real damage to the MVP aside from causing it to change target.
*You pretend ignorance regarding a strategy, MVP's slave control or other MVP related knowledge. You are held responsible in that if you decide to MVP, you understand all aspects of the MVP's behavior. Ignorance will not be accepted as a reason to violate MVP Domination rule *EXCEPT* for newly released MVPs, where there will be a 2 week grace period starting from time of release for all players to learn and figure out aspects of new MVPs.

 “Strategic MVP Support” may be use to eliminate the MVP, as long as the strategy is justified and does not solely intended to prevent others to come and kill it. This includes using Safety Wall to prevent the MvP's Pneuma (and vice versa), or land protector, but is not limited to only these spells.

 Any spells that can boost a MVP's offensive power or restore their Hit Points cannot be used on the MVP by anyone except members of the dominating party.

 A dominating party loses its status when the party dies or no longer engages the MVP (that is, no longer attacking the MVP and/or no longer being attacked by the MVP.) Even if the previous party returns, they do not regain their dominating status. Should the MVP be the one who teleports away, then domination status is reset, and whoever engages the MVP first becomes the new dominating party.

 These rules do not apply to a MVP's slaves, any MVP in GM events or MVPs public DB room unless stated otherwise by a GM.

==Do Not Beg==
Players on the server earned their items and zenny via practical work and intelligence. Follow suit, and don't go around begging people for items or money.

==Do Not Bot/Macro==
Botting will result in a permanent ban of all accounts and any type of macro will result in a permanent account ban, no exceptions. Failure to pass the botting/macro test from GMs, regardless of "actual reasons," will be treated as using bots or macro programs.

==No AFK Leveling/Hunting==
No one is allowed in anyway or form to level/hunt AFK with the means of any pet, homunculus, @autotrade, item, skill or card.

==Do Not Loot Steal==
Do not steal the loots of other people, be it from monsters or when a player is unloading pets. Items on the ground, especially if unloaded from the pet, still count as the player's property.

==Vending Shops and Chatrooms==
Do no set vending shops or chat within a 7x7 area (3 cell radius) of any NPC, including warps. Only one vender can occupy one cell. In Prontera, shops and chat boxes can only be set up on the side walks. Vending Shops can only be put up in a town (except for Niflheim) or maps without *any* monsters.

==Do Not Cheat==
If you find a bug or exploit, report it immediately to the GM Team via PM on the forum or ticket support system. Failure to report a bug or abuse is considered a violation of this rule and the offenders will be seriously punished.

==Do Not Advertise Any Other Server/Website/Game==
Do not advertise any other server/website/game. Mentioning another server by name can be considered advertising. Mentioning official server names are allowed.

==Do Not Break DB/BB Randomly Anywhere/Everywhere==
Do not break DB/BB outside of DB Rooms. Take care of your accidental DB/BB, or transformed monsters due to equipment effects. Ask for help immediately on @main if the monster(s)in question are too strong for you to handle alone (including if it is in a town or no-exp loss map).

==Do Not Block Castles' Entrances==
During WoE it is forbidden to cast '''Ice Wall''', or any other skill or item that would prevent players from entering a castle. /notrade is available to all players.

==Double-clienting is Forbidden==
That is: you're only allowed to ever have 1 RO client open per real, physical, actual person. You are not allowed to log more than 1 RO client be it on the same computer or on two separate computers. (2 separate real people playing in the same house is fine however.)

==Mushroom/Plant Limit==
When using the creator skill to create mushrooms or plants you must not go over 200 total at the same time. 200 mushrooms=ok, 201 mushrooms= not ok, 100 mushrooms+100 plants=ok 101 mushrooms+100 plants= not ok because it makes a total of 201.

==No Trans/Extended Classes in Aldebaran Castle==
No Trans (Reborn) or Extended classes (Ninja, Gunslinger, Taekwon treee) are allowed in Aldebaran Castle. If a such a class ends up in it due to the Guild Recall skill, then they must leave immediately, by using a butterfly wing or logging out. Merely walking out is not an option to leave the castle, and attacking players is cpnsidered a punishable offense.

==Regarding Alchemist/Creator's Homunculus==
The heRO AI is designed to comply with our specific rules regarding homunculus, and it is recommended to use it.
 http://www.pandoraonline.net/AI.zip
 Players are also free to use their own written AI, as long as they follow the server rules

 - No Killstealing!
 The homunculus is bound by the same rules as its owner, and must not attack a monster that belongs to another player.
 - No auto-Alchemist skills.
 The AI is meant to control the homunculus only, you are not allowed to use it to control your alchemist/creator character.
 - No AFK leveling.
 AFK leveling will be treat the same as botting, if you must go away from your computer, do so in a monsterless map or send your homunculus to sleep.

==Regarding Shared Accounts==
Account sharing is not our responsibility and is not encouraged by the GM team. The GM team will not consider movement of items due to account sharing as an act of stealing. The selling/trading of an entire account counts as a form of account sharing.

==Regarding Stolen Items Outside of Shared Accounts==
If you have an unmodified screenshot of an item(s) being lended and yet failed to get the item back, this is considered stealing and the items will be returned back to the owner. The report needs to be as clear as possible with a precice time frame. Item retrieval does NOT apply if the other person is banned - any items regardless of origin are always permanently locked with the banned account (unless the account is banned precisely due to stealing in the first place.)

==Do Not Tolerate/Assist in Rule-breaking Activities==
Inaction to cover up a rule-breaking act committed by someone else, such as not reporting a bot due to being in the same guild/friends, not reporting fully banned member returning to heRO*, can also count as an offense. You should report on rule breakers as soon as possible.

 *Note: Normally when a player is banned, they are allowed to start totally fresh. However, there are completely banned players who are not welcome in heRO and are not allowed to play even if they are willing to start fresh:

List of completely banned players:

*"Silvanel"
*"Ryan/Rain"
*"Amil Gaul/Makachuk"
*"Mane"
*"Kohaku"

==Final Rule==
Lastly, if by your action(s) or inaction(s) you cause harm or seriously hinder another player's game & community experience, punishments may be given according to the severity of the action(s) or inaction(s).

File:MySQL Administrator 1.jpg

2010-04-15T11:44:41Z

Revenant:

File:MySQL Query Browser 1.jpg

2010-04-15T11:44:36Z

Revenant:

File:Visual C++ 1.jpg

2010-04-15T11:44:32Z

Revenant:

File:TortoiseSVN 1.jpg

2010-04-15T11:44:27Z

Revenant:

User:Revenant

2010-04-15T11:44:10Z

Revenant:

=How To Set Up a Local Test Server=

==Step 1: Compiling your Server==

In order to compile (set-up) an eAthena server, you will need 2 things;

*The eAthena base code.
*A program to actually compile the above code.

Before you can actually attempt to compile the code, you're going to have to obtain it - Which we will be doing via a program called [http://tortoisesvn.net/downloads Tortoise SVN]. You're going to want the 32 bit installer - If you have to ask the difference, then you don't need to worry about it anyway. When installing, the only thing you need is the actual program, but registering .diff files can be useful later on.

Once you've installed TortoiseSVN, you will be able to download the eAthena code from the official SVN. First off, find create a folder somewhere on your computer, and create a repository within it using TortoiseSVN's right-click menu, as seen in the image to the right. [[Image:TortoiseSVN 1.jpg|thumb|The name of the folder doesn't matter.|212px]] Once you've done this, click 'SVN Checkout', and choose the options 'HEAD revision' & fully recursive, putting in <nowiki>http://svn.eathena.ws/svn/ea/stable/</nowiki> as the URL. What this does is download the SVN files directly from eAthena's repository, ensuring that you've got the absolute latest files, including updates & bug-fixes.

heRO currently runs on '''Stable''', but you can have multiple SVNs; I'd recommend working with '''Trunk''', too.

Now that you have the actual code on your computer, you need to download a compiler to actually manufacture the raw code into the base of your test server. The compiler many people use is [http://www.microsoft.com/express/vc/ Microsoft's Visual C++ 2008 Express Edition]. This is free with online registration, and it is recommended you do such straight away just to save yourself the time later on. You will also have to use this to re-compile your server later on should you do any degree of source-editing.

[[Image:Visual C++ 1.jpg|left|thumb|As shown|163px]]
Once you've gotten VC++ installed, head to your test server folder and look for the file labeled 'eAthena-9', and double-click it. The window on the left will show up - right click 'Batch Build', and select all of them, then 'Build'. It'll probably take a while, so you may want to start on the next step. Congratulations! Assuming you've followed this guide properly, you've just compiled your first test server. Now you need to prepare the database for your server to store data in. The two types of database to choose from are TXT and MySQL - Technically, if you use TXT, you're done setting up entirely - But we're not using TXT, nope. It's just not as good as MySQL, and is looked down upon by many due to how simplistic it is in comparison. MySQL offers a number of things that TXT cannot such as script integration and automated back-ups.

==Step 2: Installing and Configuring MySQL==
As mentioned in the previous step of this guide, MySQL is vastly superior to use compared a plain TXT database, and is nowhere near as complicated to use as people think. While it's true that MySQL can be difficult and complex at times, when using it with eAthena servers, you rarely if ever have to touch it at all, past initial configuration and use, aside from perhaps when manually registering accounts via script query (Command line). Since this is a local server, you will probably be just using an easier method for test accounts. You need the following two things; the first of which is absolutely neccesary, as it is your actual server, the second being although optional, I consider absolutely essential, as it makes everything much easier.

*[http://dev.mysql.com/downloads/mysql/5.1.html MySQL Community Server]
*[http://dev.mysql.com/downloads/gui-tools/5.0.html MySQL GUI Tools]

[[Image:MySQL Administrator 1.jpg|thumb|Self-explanatory|163px]]

Installation should be fairly straightforward - I made a little bit more complicated for myself because I had to choose custom installation directories due to the fact I organize my computer rather meticulously via partitions. When installing the server, at some stage you should be asked to enter a password for the root account of the server - Note this down, as you'll need it. Once everything's been installed, boot up the MySQL Administrator program, located in your MySQL directory. By default, the Server Host should be 'localhost' (your computer), and the Username 'root' (Whose password you defined earlier). Put in the password, and click OK.

First of all, we have to create a new user. While we COULD use the root MySQL account for this, it's unneccesary and could be considered unsafe. Click 'User Administration' and then 'Add a New User' (As shown in the right picture). You may notice the additional tab at the top called 'Schema Priviledges' - We'll get to that in a moment. Click the 'Catalogs' option in the left bar. A listing of schemata will come up (There will probably be 3 default ones; you don't have to worry about those). Schemata is basically a fancy way of saying 'This is a particular database for something'. It's kind of like a folder, except with data. Right click the white space at the bottom left of the screen, under the pre-existing schemata, and click 'Create New Schema', naming it whatever you want. Note this name down. Head back to User Administration, click on the user you created earlier, and then the 'Schema Priviledges'. From there, click on your newly created database, then the '<<' button in the middle of your screen, and then finally apply changes.

What you've done so far is:
[[Image:MySQL Query Browser 1.jpg|thumb|left|I know it's scary|163px]]
#Create a new MySQL user.
#Create a new MySQL database.
#Link the MySQL user with the MySQL database.

You can close MySQL Administrator now. Open up MySQL Query Browser, and put in the details for the user you created; the host is still 'localhost'. For the default schema, use the name of the one you'd created earlier, which for me was 'eAthena'. The screen on your left will show up. Most of this, you can actually disregard - Just hit 'File', then 'Open Script'. Navigate to your eAthena folder from Step 1 of this guide, and look for the folder named 'sql-files'. Choose '''main.sql''', then hit the now-highlighted 'Execute' button at the top of your screen. This is populating your database/schema with the tables neccesary for eAthena to function properly. Repeat this with '''item_db.sql''', '''item_db2.sql''', '''mob_db.sql''', '''mob_db2.sql''' and finally '''logs.sql'''. You're done here! It's time for the final step - Configuring eAthena to use the SQL information.

==Step 3: Editing Your .Conf Files==
Unfortunately, I won't be able to add any shiny images for sake of ease in this section, as you're more or less just editing text files. That said, I recommend you get [http://notepad-plus.sourceforge.net/ Notepad++] for editing said files. Once you've gotten it installed (Assuming you've chosen to do so), you'll be able to right-click most files to choose 'Edit with Notepad++', which you will be doing for this entire section. What we're going to be doing is editing specific values in the configuration files in order to link the actual game-servers (Which I don't really need to explain) and the MySQL database (& its tables) that we set-up previously. While I encourage you to look at all of the .conf files (Especially the ones in the /battle/ folder), the particular ones we '''need''' to edit are as follows;

*inter_athena.conf
*login_athena.conf

Due to the repetition involved in editing each of these two files, I'm not going to elaborate on absolutely each one but instead explain the five things which are going to come up in each file that you have to change. If something doesn't work properly upon start-up of your server, chances are you simply missed a setting you were meant to have edited. These five variables are;

*Hostname - 127.0.0.1 by default. ''Leave this alone; you don't need to edit it''
*Port - 3306 by default. ''Leave this alone too, you also don't need to edit it''.
*Username - This is the name of the new user account you created during step 2's MySQL database set-up.
*Password - This is the password corresponding to the above account.
*Database - And finally, this is the name of the database/schema you'd created earlier, linked to the username.

Once you're confident that you've done all of this correctly, there's one last thing to do - click 'runserver-sql.bat'. Cross your fingers! If you get an error pertaining to .txt files, simply rename the 'import-tmpl' folder to 'import'.

==Step 4: Connecting to Your Server==
This is the easiest step. Since you're emulating heRO's environment for the most concise development & testing, all you need to do is add your local host IP (127.0.0.1) to your sclientinfo.xml; which should connect to both the live server and the test server at this stage. Once you've done that, edit '''conf/battle/client.conf''' to add in the correct number of hairstyles & palletes.

File:794px-MySQL Administrator 1.jpg

2010-04-15T11:43:02Z

Revenant:

File:800px-MySQL Query Browser 1.jpg

2010-04-15T11:42:23Z

Revenant:

File:621px-Visual C++ 1.jpg

2010-04-15T11:42:09Z

Revenant:

File:800px-TortoiseSVN 1.jpg

2010-04-15T11:41:51Z

Revenant:

User:Revenant

2010-04-15T11:41:22Z

Revenant: New page: =How To Set Up a Local Test Server= ==Step 1: Compiling your Server== In order to compile (set-up) an eAthena server, you will need 2 things; *The eAthena base code. *A program to actua...

=How To Set Up a Local Test Server=

==Step 1: Compiling your Server==

In order to compile (set-up) an eAthena server, you will need 2 things;

*The eAthena base code.
*A program to actually compile the above code.

Before you can actually attempt to compile the code, you're going to have to obtain it - Which we will be doing via a program called [http://tortoisesvn.net/downloads Tortoise SVN]. You're going to want the 32 bit installer - If you have to ask the difference, then you don't need to worry about it anyway. When installing, the only thing you need is the actual program, but registering .diff files can be useful later on.

Once you've installed TortoiseSVN, you will be able to download the eAthena code from the official SVN. First off, find create a folder somewhere on your computer, and create a repository within it using TortoiseSVN's right-click menu, as seen in the image to the right. [[File:TortoiseSVN 1.jpg|thumb|The name of the folder doesn't matter.|212px]] Once you've done this, click 'SVN Checkout', and choose the options 'HEAD revision' & fully recursive, putting in <nowiki>http://svn.eathena.ws/svn/ea/stable/</nowiki> as the URL. What this does is download the SVN files directly from eAthena's repository, ensuring that you've got the absolute latest files, including updates & bug-fixes.

heRO currently runs on '''Stable''', but you can have multiple SVNs; I'd recommend working with '''Trunk''', too.

Now that you have the actual code on your computer, you need to download a compiler to actually manufacture the raw code into the base of your test server. The compiler many people use is [http://www.microsoft.com/express/vc/ Microsoft's Visual C++ 2008 Express Edition]. This is free with online registration, and it is recommended you do such straight away just to save yourself the time later on. You will also have to use this to re-compile your server later on should you do any degree of source-editing.

[[File:Visual C++ 1.jpg|left|thumb|As shown|163px]]
Once you've gotten VC++ installed, head to your test server folder and look for the file labeled 'eAthena-9', and double-click it. The window on the left will show up - right click 'Batch Build', and select all of them, then 'Build'. It'll probably take a while, so you may want to start on the next step. Congratulations! Assuming you've followed this guide properly, you've just compiled your first test server. Now you need to prepare the database for your server to store data in. The two types of database to choose from are TXT and MySQL - Technically, if you use TXT, you're done setting up entirely - But we're not using TXT, nope. It's just not as good as MySQL, and is looked down upon by many due to how simplistic it is in comparison. MySQL offers a number of things that TXT cannot such as script integration and automated back-ups.

==Step 2: Installing and Configuring MySQL==
As mentioned in the previous step of this guide, MySQL is vastly superior to use compared a plain TXT database, and is nowhere near as complicated to use as people think. While it's true that MySQL can be difficult and complex at times, when using it with eAthena servers, you rarely if ever have to touch it at all, past initial configuration and use, aside from perhaps when manually registering accounts via script query (Command line). Since this is a local server, you will probably be just using an easier method for test accounts. You need the following two things; the first of which is absolutely neccesary, as it is your actual server, the second being although optional, I consider absolutely essential, as it makes everything much easier.

*[http://dev.mysql.com/downloads/mysql/5.1.html MySQL Community Server]
*[http://dev.mysql.com/downloads/gui-tools/5.0.html MySQL GUI Tools]

[[File:MySQL Administrator 1.jpg|thumb|Self-explanatory|163px]]

Installation should be fairly straightforward - I made a little bit more complicated for myself because I had to choose custom installation directories due to the fact I organize my computer rather meticulously via partitions. When installing the server, at some stage you should be asked to enter a password for the root account of the server - Note this down, as you'll need it. Once everything's been installed, boot up the MySQL Administrator program, located in your MySQL directory. By default, the Server Host should be 'localhost' (your computer), and the Username 'root' (Whose password you defined earlier). Put in the password, and click OK.

First of all, we have to create a new user. While we COULD use the root MySQL account for this, it's unneccesary and could be considered unsafe. Click 'User Administration' and then 'Add a New User' (As shown in the right picture). You may notice the additional tab at the top called 'Schema Priviledges' - We'll get to that in a moment. Click the 'Catalogs' option in the left bar. A listing of schemata will come up (There will probably be 3 default ones; you don't have to worry about those). Schemata is basically a fancy way of saying 'This is a particular database for something'. It's kind of like a folder, except with data. Right click the white space at the bottom left of the screen, under the pre-existing schemata, and click 'Create New Schema', naming it whatever you want. Note this name down. Head back to User Administration, click on the user you created earlier, and then the 'Schema Priviledges'. From there, click on your newly created database, then the '<<' button in the middle of your screen, and then finally apply changes.

What you've done so far is:
[[File:MySQL Query Browser 1.jpg|thumb|left|I know it's scary|163px]]
#Create a new MySQL user.
#Create a new MySQL database.
#Link the MySQL user with the MySQL database.

You can close MySQL Administrator now. Open up MySQL Query Browser, and put in the details for the user you created; the host is still 'localhost'. For the default schema, use the name of the one you'd created earlier, which for me was 'eAthena'. The screen on your left will show up. Most of this, you can actually disregard - Just hit 'File', then 'Open Script'. Navigate to your eAthena folder from Step 1 of this guide, and look for the folder named 'sql-files'. Choose '''main.sql''', then hit the now-highlighted 'Execute' button at the top of your screen. This is populating your database/schema with the tables neccesary for eAthena to function properly. Repeat this with '''item_db.sql''', '''item_db2.sql''', '''mob_db.sql''', '''mob_db2.sql''' and finally '''logs.sql'''. You're done here! It's time for the final step - Configuring eAthena to use the SQL information.

==Step 3: Editing Your .Conf Files==
Unfortunately, I won't be able to add any shiny images for sake of ease in this section, as you're more or less just editing text files. That said, I recommend you get [http://notepad-plus.sourceforge.net/ Notepad++] for editing said files. Once you've gotten it installed (Assuming you've chosen to do so), you'll be able to right-click most files to choose 'Edit with Notepad++', which you will be doing for this entire section. What we're going to be doing is editing specific values in the configuration files in order to link the actual game-servers (Which I don't really need to explain) and the MySQL database (& its tables) that we set-up previously. While I encourage you to look at all of the .conf files (Especially the ones in the /battle/ folder), the particular ones we '''need''' to edit are as follows;

*inter_athena.conf
*login_athena.conf

Due to the repetition involved in editing each of these two files, I'm not going to elaborate on absolutely each one but instead explain the five things which are going to come up in each file that you have to change. If something doesn't work properly upon start-up of your server, chances are you simply missed a setting you were meant to have edited. These five variables are;

*Hostname - 127.0.0.1 by default. ''Leave this alone; you don't need to edit it''
*Port - 3306 by default. ''Leave this alone too, you also don't need to edit it''.
*Username - This is the name of the new user account you created during step 2's MySQL database set-up.
*Password - This is the password corresponding to the above account.
*Database - And finally, this is the name of the database/schema you'd created earlier, linked to the username.

Once you're confident that you've done all of this correctly, there's one last thing to do - click 'runserver-sql.bat'. Cross your fingers! If you get an error pertaining to .txt files, simply rename the 'import-tmpl' folder to 'import'.

==Step 4: Connecting to Your Server==
This is the easiest step. Since you're emulating heRO's environment for the most concise development & testing, all you need to do is add your local host IP (127.0.0.1) to your sclientinfo.xml; which should connect to both the live server and the test server at this stage. Once you've done that, edit '''conf/battle/client.conf''' to add in the correct number of hairstyles & palletes.