[[Category:Remote Control]]
[[File:ScriptedRC.png|300px|thumb|right|Scripted RC window]]The Scripted RC is an in-game utility that allows administration of Graal servers without needing to download extra software. It supports most of the functionality of the external RC, including editing attributes, rights, bans, uploading and downloading files, adding, removing and editing NPCs, etc.

You can access the Scripted RC by pressing F6. Note that you must have admin rights on the server.

==Having trouble?==

If you are having problems with the Scripted RC or would like to report any bugs or issues, please post them in [http://forums.graalonline.com/forums/showthread.php?t=73833 this thread] on the Graal forums or contact [[User:Skyld]].

==Recent updates==

====28th June 2010====
The Scripted RC received the following updates:
* The attributes window has been improved so that colours are now selectable using a drop-down box.
* The rights window is now tabbed and works like the external RC.
* The ban window is much improved, now supporting computer bans properly, working like the external RC, and ban lengths are properly listed now.
* The file manager has been improved, it is now possible to drag the pane between the folder tree and the file list. Columns can also be sorted by clicking the column header, and you can search the file list by clicking the list and typing what it is you are looking for.
* The RC playerlist has been removed, instead moving shortcuts into the scripted playerlist (F7). Once you have logged into Scripted RC, you can right-click players on the playerlist to open their attributes, etc.
* The script menu has been removed, instead making it possible to add new weapons, classes and NPCs from inside the script editor itself.
* RC chat is now stripping HTML tags properly.

==Notes==

====Attributes====
In Scripted RC, the player's attributes are more separated. You must edit attributes, weapons and flags separately. The following commands help you to edit attributes:
* <tt>/open account name</tt> for basic attributes, look, etc
* <tt>/openflags account name</tt> for editing client flags
* <tt>/openweapons account name</tt> for editing weapons
* <tt>/openchests account name</tt> for editing opened chests

Scripted RC

2010-06-29T13:27:17Z

Skyld:

User:Skyld

2010-06-29T13:26:27Z

Skyld: /* Accounts */

[[Category:Users]][[Category:Administration]][[Category:Global Staff]]
{{player}}
----
Lex, aka `Skyld'

=== About ===
Skyld is a [[Regular]] user of the [[GScript IRC Channel|#gscript]] IRC Channel (freenode) and [[GScript IRC Channel|#gscript]] [[Guild]] member. He is a high level[[Scripter]] and, and has been known to help other #gscript visitors with their scripting problems.

=== Staff Experience ===

Skyld has been a member of the Global Sripting team since March 25th, 2006. For a short time, Skyld was also a PWA, but stepped back due to being busy with the university.

Skyld returned and resumed his management of the Global Scripting team. A short time later, in late August of 2009, the Global development team was formed and Skyld joined the team as a technical administrator.

Skyld has had experience working on multiple servers as a GST, but Skyld's home server has always been Rudora, a server that he manages.

=== Accounts ===
{| border="1" cellpadding="2" width="100%"
| '''Name'''
| '''Admin level'''
| '''Banned?'''
| '''Comments'''
|-
| Skyld
| 2 (All)
| No
| [[GST]]
|}

=== Documents written by Skyld ===
* [[Creation/Dev/Graal_v4_IRC|Graal v4 IRC Documentation]]
* [[Creation/Dev/Troubleshooting_Graal_v4_IRC|Troubleshooting Graal v4 IRC]]
* [[Creation/Dev/Basics_of_NPC-Control|Basics of NPC-Control]]
* [[Creation/Dev/Output_Methods|GScript2 Output Methods]]

=== Comments ===
See [[User_Talk:Skyld|Skyld's Talk Page]]

Scripted RC

2010-06-29T13:25:56Z

Skyld:

ScriptedRC

2010-06-29T13:23:44Z

Worlds/Rudora

2009-09-09T19:01:47Z

Skyld:

[[Category:Worlds]]
{{playerworld}}

[[Image:RudoraBank.png|frame|border|right||alt=Rudora Bank|Screenshot of Rudora Bank]]Rudora was one of the original Classic playerworlds of GraalOnline. It was originally created by Spark911, Wan and Fox, and has since been managed by GrowlZ and, now, Skyld. It maintains a strong classic theme using the default tileset. For the past few years, Rudora has been under slow redevelopment by Skyld, renewing the scripted features (including a complete conversion to the new GScript language) and a freshen up of the overworld. A number of new jobs have been added.

====Playerworld Status====

Rudora is currently a private playerworld, although it has previously been on both the Classic and the Hosted tabs.

====Current Staff====

Skyld is the only person currently working on the project.

====New Features====

A compliment of new features has been added to the older overworld in order to improve gameplay.

* A new ratings system has been added that gives players three separate ratings: a PK rating (or otherwise known as your regular rating), a spar rating and a quest rating. This is a value out of 100 that starts at 50 and improves with more kills and worsens with more deaths. This serves as a replacement to the aging AP system. Your AP is updated as you enter different levels, for instance, as you enter a spar level, your AP is changed to match your spar rating. A scoreboard system is in place to show the top five PK, spar and quest ratings from players on the server.

* Rudora uses a hybrid HP system that distributes tasks between the clientside and the serverside. Quests and events can easily use clientside HP to improve response times.

* A simple item system has been added that allows item collection, trading and selling. A marketplace has been added which allows players to rent stalls and sell their items to other players. With it, a new scripted inventory has been added which allows players to select and equip items, as well as drop them and see information about them. The inventory menu is accessible by keyboard (Q key, up and down) and by mouse (clicking on the top-left icon and then scrolling and clicking the item you want). For additional device compatibility with platforms such as the iPhone, it is possible to scroll up and down on the list by dragging with your finger.

* A new events system has been added making it much easier for Events Team to announce, host and end events, and distribute event coins. Players can join and leave events as they wish.

* Both new and old jobs have been added to the server, including fishing, berry picking, tree cutting, vine growing, mining and crafting. All produced items from these jobs can be sold, and some can be used for other jobs such as crafting new items. The old Lottery has been readded too.

* A new guilds system allows players to create local guilds, providing they have the support of at least 5 other players. Importance will be brought back to guilds by providing some guild events and quests, although some guilds may require that you have a certain rating first!

* Hats have been added with a new hat shop and dynamic pricing. The prices of hats are changed automatically to reflect upon their rarity. A hat that is bought more often will go down in price, and a hat that is bought less often will stay at a higher price (as it is classed "more rare"). Special hats will be added for certain guilds and also a couple of collector hats will be moved into circulation.

Worlds/Rudora

2009-09-09T19:01:14Z

Skyld:

[[Category:Worlds]]
{{playerworld}}

[[Image:RudoraBank.png|frame|border|right||alt=Rudora Bank|Screenshot of Rudora Bank]]Rudora was one of the original Classic playerworlds of GraalOnline. It was originally created by Spark911, Wan and Fox, and has since been managed by GrowlZ and, now, Skyld. It maintains a strong classic theme using the default tileset. For the past few years, Rudora has been under slow redevelopment by Skyld, renewing the scripted features (including a complete conversion to the new GScript language) and a freshen up of the overworld. A number of new jobs have been added.

===Playerworld Status===

Rudora is currently a private playerworld, although it has previously been on both the Classic and the Hosted tabs.

===Current Staff===

Skyld is the only person currently working on the project.

===New Features===

A compliment of new features has been added to the older overworld in order to improve gameplay.

* A new ratings system has been added that gives players three separate ratings: a PK rating (or otherwise known as your regular rating), a spar rating and a quest rating. This is a value out of 100 that starts at 50 and improves with more kills and worsens with more deaths. This serves as a replacement to the aging AP system. Your AP is updated as you enter different levels, for instance, as you enter a spar level, your AP is changed to match your spar rating. A scoreboard system is in place to show the top five PK, spar and quest ratings from players on the server.

* Rudora uses a hybrid HP system that distributes tasks between the clientside and the serverside. Quests and events can easily use clientside HP to improve response times.

* A simple item system has been added that allows item collection, trading and selling. A marketplace has been added which allows players to rent stalls and sell their items to other players. With it, a new scripted inventory has been added which allows players to select and equip items, as well as drop them and see information about them. The inventory menu is accessible by keyboard (Q key, up and down) and by mouse (clicking on the top-left icon and then scrolling and clicking the item you want). For additional device compatibility with platforms such as the iPhone, it is possible to scroll up and down on the list by dragging with your finger.

* A new events system has been added making it much easier for Events Team to announce, host and end events, and distribute event coins. Players can join and leave events as they wish.

* Both new and old jobs have been added to the server, including fishing, berry picking, tree cutting, vine growing, mining and crafting. All produced items from these jobs can be sold, and some can be used for other jobs such as crafting new items. The old Lottery has been readded too.

* A new guilds system allows players to create local guilds, providing they have the support of at least 5 other players. Importance will be brought back to guilds by providing some guild events and quests, although some guilds may require that you have a certain rating first!

* Hats have been added with a new hat shop and dynamic pricing. The prices of hats are changed automatically to reflect upon their rarity. A hat that is bought more often will go down in price, and a hat that is bought less often will stay at a higher price (as it is classed "more rare"). Special hats will be added for certain guilds and also a couple of collector hats will be moved into circulation.

Worlds/Rudora

2009-09-09T18:59:32Z

Skyld:

[[Image:RudoraBank.png|frame|border|right||alt=Rudora Bank|Screenshot of Rudora Bank]]Rudora was one of the original Classic playerworlds of GraalOnline. It was originally created by Spark911, Wan and Fox, and has since been managed by GrowlZ and, now, Skyld. It maintains a strong classic theme using the default tileset. For the past few years, Rudora has been under slow redevelopment by Skyld, renewing the scripted features (including a complete conversion to the new GScript language) and a freshen up of the overworld. A number of new jobs have been added.

===Current Staff===

Skyld is the only person currently working on the project.

===New Features===

A compliment of new features has been added to the older overworld in order to improve gameplay.

* A new ratings system has been added that gives players three separate ratings: a PK rating (or otherwise known as your regular rating), a spar rating and a quest rating. This is a value out of 100 that starts at 50 and improves with more kills and worsens with more deaths. This serves as a replacement to the aging AP system. Your AP is updated as you enter different levels, for instance, as you enter a spar level, your AP is changed to match your spar rating. A scoreboard system is in place to show the top five PK, spar and quest ratings from players on the server.

* Rudora uses a hybrid HP system that distributes tasks between the clientside and the serverside. Quests and events can easily use clientside HP to improve response times.

* A simple item system has been added that allows item collection, trading and selling. A marketplace has been added which allows players to rent stalls and sell their items to other players. With it, a new scripted inventory has been added which allows players to select and equip items, as well as drop them and see information about them. The inventory menu is accessible by keyboard (Q key, up and down) and by mouse (clicking on the top-left icon and then scrolling and clicking the item you want). For additional device compatibility with platforms such as the iPhone, it is possible to scroll up and down on the list by dragging with your finger.

* A new events system has been added making it much easier for Events Team to announce, host and end events, and distribute event coins. Players can join and leave events as they wish.

* Both new and old jobs have been added to the server, including fishing, berry picking, tree cutting, vine growing, mining and crafting. All produced items from these jobs can be sold, and some can be used for other jobs such as crafting new items. The old Lottery has been readded too.

* A new guilds system allows players to create local guilds, providing they have the support of at least 5 other players. Importance will be brought back to guilds by providing some guild events and quests, although some guilds may require that you have a certain rating first!

* Hats have been added with a new hat shop and dynamic pricing. The prices of hats are changed automatically to reflect upon their rarity. A hat that is bought more often will go down in price, and a hat that is bought less often will stay at a higher price (as it is classed "more rare"). Special hats will be added for certain guilds and also a couple of collector hats will be moved into circulation.

Skyld: Changed "Functions & Variables & Objects" for better sentence flow

'''GScript''' is [[Graal]]'s scripting language.

Its syntax and some of its semantics might seem familiar to those who program in [[WikiPedia:C (Programming Language) | C]] or [[WikiPedia:Java_programming_language|Java]]. In some ways it is more dynamic, e.g. supporting dynamicly joining and leaving of classes, and brings support for easy management of online game content.

GScript started as a very limited language ([[Creation/Dev/Old GScript|Old GScript]]) and has since kept up with improvements to the game engine and can now be used for pretty sophisticated scripts that greatly customise the gaming experience.

It is used, with minor differences, for [[Clientside]] tasks like [[GUI | GUI programming]], special effects with nifty 3d lighting and custom [[NPC weapon|NPC Weapons]] or "engines", and [[Serverside]] systems like player housing, complex baddies or pets.

GScript can be discussed in the non-official [[GScript IRC channel]].

'''If you would like to contribute to the GraalBible's GScript documentation, you might want to [[Creation/Dev/GScript/Contribute|read this article]].'''

In your scripting quest, you may find the following articles to be of use:

'''Basic information'''
* [[Creation/Dev/Script/Starting Guide|Starting Guide]]
* [[Creation/Dev/Script/Client|Functions, variables and objects (clientside)]]

'''Specific Features'''
* [[Creation/Dev/GS1_To_GS2|GS1 To GS2: Guide for fixing scripts to work with the new engine]]
* [[Particle Engine|Particle Engine]]
* [[Creation/Dev/Graal v4 IRC|Graal IRC Scripting: Graal IRC Scripting Reference]]
* [[Creation/Dev/Troubleshooting Graal v4 IRC|Graal IRC Scripting: Troubleshooting Scripting Reference]]
* [[Creation/Dev/Output Methods|Output methods]]
* [[Creation/Dev/Using Classes Effectively|Use of classes]]
* [[Creation/Dev/GScript/Understanding GUI Profiles|GUI Features: Understanding GUI profiles]]
* [[Creation/Dev/GScript/Constants|Constants]]

'''Tutorials'''
* [[Creation/Dev/Creating Tabbed Window Panes|Creating Tabbed Window Panes]]
* [[Creation/Dev/Database_Communication|Indexed Database Communication]]

'''Script Functions'''

These are frequently updated, to get the latest list run Graal with the -listscriptfunctions option:
* [[Creation/Dev/Script/Clientside_Functions|Client side]]
* [[Creation/Dev/Script Functions: NPC Server|Server side]]

[[Creation/Dev/Script/Index|Related Artices]]

2006-06-26T20:21:03Z

Skyld: /* Working with if () checks */

Creation/Dev/GScript/GScript for Dummies

2006-06-15T16:39:10Z

Skyld:

[[Image:s_dummies.png]]
= Preface =
== Introduction ==
New Engine GScript for Dummies is a guide designed to aid the learning of the new scripting engine, frequently dubbed 'gscript2'. This guide will explain the basics, such as functions, variables and some Gscript-specific concepts that you will need to know in order to get scripting in no time. The guide is indexed at the top of the page, and by clicking one of the index links, you will be taken to the appropriate section. If you haven't really a clue where to start, then you're probably best reading through the entire guide.

== Who is this for? ==
This is for absolutely anyone who is interested in learning in Gscript. Having some previous knowledge of scripting would be beneficial, but isn't required.

== What should I do if I have a problem or a question not covered here? ==
You can, of course, post your problem on the [http://forums.graalonline.com/forums/ GraalOnline Forums] in the NPC Scripting section. Similarly, you can also contact a member of the Global Scripting Team via Forum PM if you think that you require more direct assistance, although usually forum regulars will be happy to help.

= Welcome to GScript =
GScript is the scripting language that powers most of the dynamic content provided by GraalOnline. The scripting language is a very useful tool, since it enables you to create a very wide variety of systems, including automated baddies, scripted systems, GUIs.

== Glossary of Terms ==
Through this guide, a number of terms are likely to be used. In case you are not sure exactly what any of the terms mean, you can look them up here!
* '''Variable''': This is a special type of object that stores data. The data might be a string, an integer, a float, or an array.
* '''String''': This is a type of data that can be stored in a variable. A string is a collection of letters, numbers and symbols. For example, if you are interested in storing a sentence in a variable, a string is probably your best bet.
* '''Integer''': This is a type of data that can be stored in a variable. An integer is simply a round number. No decimal places. Positive or negative, it's just a round number.
* '''Float''': This is a type of data that can be stored in a variable. A float is a number that is not an integer, that may contain decimal places.
* '''Function''': This is a block of code. A function is a defined routine of instructions that can be ran at any time in a script.
* '''Predefined Function''': This is a function that is already available in the scripting engine. Such functions are internal, that usually allow mathematical and other variable operations, manipulation of players and such like. You do not need to define a predefined function yourself, since it is already there for you to use!
* '''Event Functions''': These are functions that are called by the scripting engine automatically based on events happening. For example, one function may be called when a player touches the NPC, and another one might be called when a player enters the level. Note that these event functions are only called if you have written the instructions for them yourself. This will be explained in the Functions section.

= Using GScript =
== Basic concepts ==
It is important to remember a couple of very basic, but very important concepts when using GScript.
* All statements (that is, function calls, writing to variables) '''must''' end in a semicolon (that's a ;). This simply tells the engine that the current statement has finished. You must remember to include it, or the engine will throw errors at you when it does not realise that you have finished a statement before it moves onto the next one.

== Functions ==
A function, like mentioned in the Glossary of Terms, is a defined block of instructions. Practically everything you do in GScript will rely on functions. First, let's look at how you can define a function.

=== Defining a function ===
The syntax for defining a function is, in fact, very simple. Let's look at an example.
<pre>function myFunction()
{
// code
}</pre>
The first thing to identify is the 'function' keyword. This tells the scripting engine that you're going to define a function. This is absolutely necessary in defining functions of any kind yourself.

Second, you'll notice a name - 'myFunction'. This is the bit where you specify the name of the function that you're defining. This can be anything, providing that it doesn't contain strange symbols (usually an underscore '_' is the best suited symbol to split up function names with, since other symbols can cause errors).

Thirdly, you'll see (). This is a convention that is later used for parameters, but for now, that's not important. Just stick () on the end of your name for now.

Finally, you'll see { and }. These are braces, and define exactly what the function contains. Anything inside the braces is code that is specific to the function. If it's inside the braces for that function, it'll run when you call that function. Very simple.

=== Function scopes ===
A fairly important concept is the idea of scopes. As demonstrated before, anything inside the { and } of a function means that it's a part of the function. Now, imagine that the entire script is like a hallway, and behind every door, is a function. When you walk into a room and close the door behind you, you are in a fairly closed space. This is true of functions.

Some types of variable, when set inside a function, are placed in the function's 'local' scope. This simply means that the variable is available for use inside the function, but not outside of the function. The 'global' scope is where other types of variable are stored, for example, variables that need to be accessible in all functions. This will be explained further in the variables section.

=== Calling a function ===
Now you've created your function, it's there to be used. Anywhere inside your script, you can call this function using the following method:
<pre>myFunction();</pre>
Note that the 'function' keyword is not present because we are not defining a function, we are just calling one. Now, the moment the scripting engine hits a function call, any code that you put inside of your function will run. Let's use the following example:
<pre>function myFunction()
{
player.chat = "Hello!";
}</pre>
This is a very basic function that just sets the player's chat text. Let's call the function.
<pre>myFunction();</pre>
Suddenly, the player's chat will be set to "Hello!". By calling the function, you've told the engine to run the code inside of that function - in this case, setting the player's chat.

== Variables ==
Now, you've seen how functions work. The next very important part is using variables. As you have read in the glossary of terms, a variable is simply a sort of object that stores information.

Variables have three important factors: name, type and value.
=== Name ===
Every variable must have a unique name. This is how you will access the value that is stored inside of the variable whenever you want to use it.

=== Type ===
Every variable also has a type. In GScript, there is a clever little system in place for variables called 'variants'. This sounds complicated, but is in fact also very simple. It simply means that the variable's type ''adjusts itself'' in order to suit the sort of data that it contains.

For example, if you make the value of a variable "Hello!", then the variable automatically becomes a string, and simply because you assigned it a value of a string. In GScript, all string values must be enclosed in "speechmarks".

What about a number? You don't even need to use speechmarks for numbers - you just type the number! Simple, no? When you do so, the variable automatically becomes either an integer or a float type in order to suit the number that you just put in it.

=== Value ===
As already established, this is simply the information/data that the variable contains.

=== Why variables are useful ===
Variables are incredibly useful for a number of reasons. They allow you to:
* Store a value that you plan to repeatedly use in your script. If you change the value of the variable, then the script uses the new value in every place the variable is used.
* Keep a value saved for when you want it later. If you take the player's chat text and want to save it, then you can use a variable.
* Manipulate a value. There are many predefined functions available in the scripting engine that will allow you to modify and use the value that is stored inside a variable; for example, mathematical operations.

=== Setting a variable ===
Setting the value of a variable is ''even'' simpler than defining a function. Let's use an example.
<pre>myVariable = "Hello!";
myVariable = 3;</pre>
Looking at this, it's easy to see the logic here.
* First, the engine is taking the variable name - in this case, "myVariable".
* Second, it is identifying the assignment operator (=). Simply, the engine has so far established that you want "myVariable" to equal something.
* Finally, it is taking the value that you want to set the variable's value to, and setting it.

In our example, we initially set the variable "myVariable" to "Hello!". This turns the variable automatically into a string. However! Immediately after, we have rewritten the value of "myVariable" with the number 3. Since there are no decimal places, the variable suddenly becomes an integer.

=== Reading a variable ===
Any time you want to get a variable's value and use it, you simply write the name of the variable. This is best explained while using a Conditional Check.

== Conditional Checks ==
For your script to even be remotely useful, you're going to have to check something somewhere. For example, if you want the script to only respond to a player saying "Foo", then you're going to have to use a conditional check.

There is another operator, called the comparison operator. It's two equals signs stuck together (==), and just instructs the engine to compare the two values. If the two values are the same, then it'll return TRUE. If they are different, it'll return FALSE.

This is simple enough. Observe the following example:
<pre>myVariable = "excellent";</pre>
We've set the variable 'myVariable' to "excellent".
<pre>myVariable == "excellent"</pre>
This time, we're checking to see if 'myVariable' equals "excellent". Since it does, this statement will evaluate to be TRUE.
<pre>myVariable == "fabulous"</pre>
Now, we're checking to see if 'myVariable' equals "fabulous". It clearly doesn't, since we set it's value to "excellent" instead. As a result, this statement returns FALSE.

=== Working with if () checks ===
Now, conditional checks alone are no good to you in a complex script. You'll need to actually use the conditional checks to make a difference in what happens.

To do this, you use an 'if' check'. 'if' is a very simple operator (it doesn't get complicated yet!) that simply runs one thing if the statement you give it is true, and optionally runs another thing if it isn't.

Since using examples so far has been the common way, let's see one here. We'll even include a bit of what you've learned already:
<pre>function myFunction()
{
myVariable = "excellent";

if (myVariable == "excellent")
{
player.chat = "Hooray! The values match.";
}
else
{
player.chat = "The values don't match.";
}
}</pre>
Now. The first thing about an if statement is giving it something to check. The statement "myVariable ==" alone will return either one of two values - TRUE (1, one) or FALSE (0, zero).

An if () statement by itself will only check if something is true. If not, it'll ignore it. If you put an else in, like in the above example, that code will be run in the case of a failure.

Creation/Dev/GScript/GScript for Dummies

2006-06-15T15:46:48Z

Skyld:

Creation/Dev/GScript/GScript for Dummies

2006-06-15T15:39:56Z

Skyld:

Creation/Dev/GScript/GScript for Dummies

2006-06-15T15:10:25Z

Skyld: