Creation/Management/Playerworld Guide - Revision history

MattKan at 19:32, 27 August 2011

2011-08-27T19:32:57Z

← Older revision		Revision as of 15:32, 27 August 2011
Line 22:		Line 22:

	==Adding Other People==		==Adding Other People==
	Making a playerworld takes time, and man-hours. Because of this, it's best to form a staff team, with good working people who you can trust and know well. Staff may need RC to help aid them with their job. RC should not be given to every staff member, and rights should be given to people who need them only. Nobody but the manager and the owner should have full rights.		Making a playerworld takes time, and man-hours. Because of this, it's best to form a staff team, with good working people who you can trust and know well. Staff may need RC to help aid them with their job. RC should not be given to every staff member, and rights should be given to people who need them only. Nobody but the manager and the owner should have full rights, and high rights to other staff members should not be delegated generously.

	To give someone access to your playerworld via RC you first need to tell the server that they are allowed to log on via RC. This is done via a serveroption which is read by the server, and is used to load and keep certain settings.		To give someone access to your playerworld via RC you first need to tell the server that they are allowed to log on via RC. This is done via a serveroption which is read by the server, and is used to load and keep certain settings.
Line 83:		Line 83:

	==Notifying The PWA of the Managers==		==Notifying The PWA of the Managers==
	The PWA (Playerworld Administration) is in control of sorting out problems on playerworld, enforcing certain rules and to help you if you have problems. They try to have an updated list of managers and co-managers so that they know who to contact if they have any problems~~. You can find all of the information listed below by typing in RC "/global serverinfo this"~~. Please try and e-mail all of your manager information to a PWA member, set out like the following:		The PWA (Playerworld Administration) is in control of sorting out problems on playerworld, enforcing certain rules and to help you if you have problems. They try to have an updated list of managers and co-managers so that they know who to contact if they have any problems. Please try and e-mail all of your manager information to a PWA member, set out like the following:

	<pre>		<pre>

McChucken: /* Notifying The PWA of the Managers */

2011-08-26T22:13:42Z

Notifying The PWA of the Managers

← Older revision		Revision as of 18:13, 26 August 2011
Line 83:		Line 83:

	==Notifying The PWA of the Managers==		==Notifying The PWA of the Managers==
	The PWA (Playerworld Administration) is in control of sorting out problems on playerworld, enforcing certain rules and to help you if you have problems. They try to have an updated list of managers and co-managers so that they know who to contact if they have any problems. Please try and e-mail all of your manager information to a PWA member, set out like the following:		The PWA (Playerworld Administration) is in control of sorting out problems on playerworld, enforcing certain rules and to help you if you have problems. They try to have an updated list of managers and co-managers so that they know who to contact if they have any problems. You can find all of the information listed below by typing in RC "/global serverinfo this". Please try and e-mail all of your manager information to a PWA member, set out like the following:

	<pre>		<pre>

McChucken: /* Adding Other People */

2011-08-26T22:10:34Z

Adding Other People

← Older revision		Revision as of 18:10, 26 August 2011
Line 22:		Line 22:

	==Adding Other People==		==Adding Other People==
	Making a playerworld takes time, and man-hours. Because of this, it's best to form a staff team, with good working people who you can trust and know well. Staff may need RC to help aid them with their job. RC should not be given to every staff member, and rights should be given to people who need them only. Nobody but the manager; should ~~not~~ have ~~a high amount of~~ rights.		Making a playerworld takes time, and man-hours. Because of this, it's best to form a staff team, with good working people who you can trust and know well. Staff may need RC to help aid them with their job. RC should not be given to every staff member, and rights should be given to people who need them only. Nobody but the manager and the owner should have full rights.

	To give someone access to your playerworld via RC you first need to tell the server that they are allowed to log on via RC. This is done via a serveroption which is read by the server, and is used to load and keep certain settings.		To give someone access to your playerworld via RC you first need to tell the server that they are allowed to log on via RC. This is done via a serveroption which is read by the server, and is used to load and keep certain settings.

Matt: /* Admin-Account */ Made a bit more specific.

2010-04-23T19:08:17Z

Admin-Account: Made a bit more specific.

← Older revision		Revision as of 15:08, 23 April 2010
Line 17:		Line 17:

	==Admin-Account==		==Admin-Account==
	Once your are ~~connecting~~ to your server for the first time, you will receive full rights on your server and the IP range for your account will automatically be set to include your current ip and computer id.		Once your are logged onto your account, and connected to your server for the first time, you will receive full rights on your server and the IP range for your account will automatically be set to include your current ip and computer id.

	The IP range is used for security so that later other people cannot abuse admin rights even if they somehow steal your password. See Section 5.1 about how to find an IP Range!		The IP range is used for security so that later other people cannot abuse admin rights even if they somehow steal your password. See Section 5.1 about how to find an IP Range!

Matt: Added source: http://forums.graalonline.com/forums/showthread.php?t=57041

2010-04-23T05:00:40Z

Added source: http://forums.graalonline.com/forums/showthread.php?t=57041

← Older revision		Revision as of 01:00, 23 April 2010
Line 519:		Line 519:

	'''Remember: You can always edit or change the IP range, but you can't always get back the Levels and NPCs deleted by an intruder.'''		'''Remember: You can always edit or change the IP range, but you can't always get back the Levels and NPCs deleted by an intruder.'''

			==Naming your Playerworld Files==

			Several times have there been problems wherein servers have uploaded files with the same names as files on other servers. When players visit these other servers, these more-recently-uploaded files will overwrite the normal files from the other servers in your webgifs directory. This is a problem, especially when files from official servers such as Graal Kingdoms are being overwritten.
			While reading, take this opportunity to remind yourself of the recommendation that when uploading graphics and sounds to your server, you prefix (or suffix) them with the name of the server where it is being uploaded. A recent example: instead of uploading some modified 'bomyload.wav' file to your server, you should rename it to (yourservername)_bomyload.wav or bomyload_(yourservername).wav. However, you should not be using bomys anyway, so you might want to use a name which actually fits what you are using the new file for.

			This will prevent the overwriting from happening and also will help when there are issues with one server stealing another's graphics. By following this recommendation, you will also avoid the awkward problem where two different people on one server might see a single NPC as having a different graphic, depending on which other servers they may have already visited. A good example of this would be a file with a simple name like 'speaker.png'. Several months ago, I visited a playerworld with a different (and newer) speaker.png file than Era's, so whenever I was on Era I ended up seeing the other server's speaker.png. It was much bigger than Era's, so you can see how it would be a problem. That problem has been solved, but many other such problems keep appearing. So, please, take care when naming files.

Pooper200000 at 19:50, 16 February 2010

2010-02-16T19:50:49Z

← Older revision		Revision as of 15:50, 16 February 2010
Line 1:		Line 1:
			[[Category:Creation]]
	So you decided to buy a Graalonline playerworld?		So you decided to buy a Graalonline playerworld?

Matt: Added "Using a PC ID, and "How to find a PC ID".

2009-04-04T19:46:08Z

Added "Using a PC ID, and "How to find a PC ID".

← Older revision		Revision as of 15:46, 4 April 2009
Line 468:		Line 468:

	=Frequently Asked Questions=		=Frequently Asked Questions=

			==How to find a PC ID==
			To find the PC ID of a specific account, that account first has to be online. Once that player is online use the command "/openaccess accountname" to open that users ban options. Once opened you can find the PC ID by look at the very top, to the right of "Edit Access of account (computer:#####)

			===Using a PC ID===
			Once you've retrieved the ID, insert the numbers in the selected players rights as "pc:pcidnumbers".

			Using a PC ID should be your primary option while giving RC access to your staff. IP Ranges should be a secondary option, and more information about IP Ranges can be found below.

	==How to find an IP/IP Range==		==How to find an IP/IP Range==

Cbk1994: /* NPC Control Rights */

2008-06-16T19:21:43Z

NPC Control Rights

← Older revision		Revision as of 15:21, 16 June 2008
Line 244:		Line 244:
	<pre>		<pre>
	rw WEAPONS/* (Weapons - Icon with sword)		rw WEAPONS/* (Weapons - Icon with sword)
			rw WEAPONS// (Weapons - Icon with sword)
	rw CLASSES/* (Classes)		rw CLASSES/* (Classes)
	rw NPCS/* (database NPCs)		rw NPCS/* (database NPCs)
Line 251:		Line 252:
	<pre>		<pre>
	rw WEAPONS/staffname/*		rw WEAPONS/staffname/*
	rw CLASSES/staffname/*		rw CLASSES/staffname*
	rw NPCS/staffname/*		rw NPCS/staffname*
	</pre>		</pre>

Tigairius: /* RC Shortcuts */

2008-06-15T22:21:59Z

RC Shortcuts

← Older revision		Revision as of 18:21, 15 June 2008
Line 322:		Line 322:
	===RC Shortcuts===		===RC Shortcuts===
	If you say one of the following in RC, it will allow you to perform certain actions, but quicker. Here is a list of all of the shortcuts from the /help action.		If you say one of the following in RC, it will allow you to perform certain actions, but quicker. Here is a list of all of the shortcuts from the /help action.

			Available commands for the NPC-Server:

	* '''/stats:''' displays server info		* '''/stats:''' displays server info

Tigairius: /* RC Shortcuts */

2008-06-15T22:21:09Z

RC Shortcuts

← Older revision		Revision as of 18:21, 15 June 2008
Line 323:		Line 323:
	If you say one of the following in RC, it will allow you to perform certain actions, but quicker. Here is a list of all of the shortcuts from the /help action.		If you say one of the following in RC, it will allow you to perform certain actions, but quicker. Here is a list of all of the shortcuts from the /help action.

	* '''/help:''' displays the following below
	* '''/stats:''' displays server info		* '''/stats:''' displays server info
			* '''/reloadscriptlibs:''' reloads the script libraries
	* '''/loadlang:''' reloads the translations into memory		* '''/loadlang:''' reloads the translations into memory
	* '''/loadlevellist:''' reloads the level list		* '''/loadlevellist:''' reloads the level list
	* '''/loadmap:''' reloads the map (for onmapx()/onmapy())
	* '''/savenpcs:''' saves all database npcs		* '''/savenpcs:''' saves all database npcs
	* '''/clearnpcs levelname:''' deletes local db npcs from a level (including gralats)		* '''/clearnpcs levelname:''' deletes local db npcs from a level (including gralats)
	* '''/npc<command param>:''' commands to the control-npc		* '''/npc<command param>:''' commands to the control-npc
			* '''/style weapon/npc/class name:''' formats the script
			* '''/listscriptlogfunctions:''' lists all loggable script functions
			* '''/functionprofilestart:''' start/restart the function profiler
			* '''/functionprofilestop:''' stop the function profiler
			* '''/functionprofileshow weapon/npc/class name:''' stats about functions
			* '''/scripthelp text:''' print help for a server side function
			* '''/scriptscan weapons/npcs/classes/levels/all text:''' scan scripts
	* '''/npcshutdown:''' closes the server		* '''/npcshutdown:''' closes the server

	Available commands for GServer:		Available commands for GServer:
	* '''/stats:''' displays server info		* '''/stats:''' displays server info
			* '''/playerinfo accountname:''' displays info about an online player
	* '''/open accountname:''' opens the player attributes window		* '''/open accountname:''' opens the player attributes window
	* '''/openrights accountname:''' opens the rights		* '''/openrights accountname:''' opens the rights
	* '''/opencomments accountname:''' opens the comments		* '''/opencomments accountname:''' opens the comments
	* '''/openaccess accountname:''' opens the ban info		* '''/openaccess accountname:''' opens the (new) ban info
	* '''/openacc accountname:''' opens the account		* '''/openacc accountname:''' opens the account
			* '''/openprofile accountname:''' opens the profile
	* '''/reset accountname:''' resets the account		* '''/reset accountname:''' resets the account
	* '''/find ~~filename~~:''' searches for a game ~~file~~		* '''/localbans:''' lists all local bans (requires RC2)
	* '''/~~allservers~~ text:''' global ~~RC chat~~ (only for high admins) ~~[High levelled Globals Only]~~		* '''/staffactivity accountname:''' lists staff actions (requires RC2)
			* '''/find filepattern:''' searches for a game files in levels/
			* '''/finddef filepattern:''' searches for default (classic) game files
			* '''/global text:''' global command (only for high admins)
	* '''/updatelevel level[,level]:''' reloads levels form hard disk		* '''/updatelevel level[,level]:''' reloads levels form hard disk
			* '''/refreshfilelist:''' scans the folders again (only use when /find is not working correctly)
			* '''/clientstats accountname:''' shows client stats (requires Graal v6)
	* '''/npcstart:''' starts the npcserver		* '''/npcstart:''' starts the npcserver
	* '''/~~shutdown~~:''' ~~closes~~ the ~~server~~		* '''/npckill:''' stops the npcserver (use this if /npcshutdown and /npcstart are not working)

	==Serveroptions==		==Serveroptions==