User guide for Ark, short for Ryzom Arkitect.

For historical reasons, those manuals refers very often, almost always, to A.R.C.C.. This is due to the fact that the full documentation has been started with the initial name, ARCC, meaning Advanced Ryzom Content Creator.

Note: with the exception of paragraph 2.1, all paragraphs Level 2 are in single page that can be accessed by clicking on the arrow (→) behind the title of the functions.

1 The script functions
2 Visualizations
- 2.1 weVMessage (Displaying a message)
3 Actions without player intervention
4 Checks
5 Captures information
- 5.1 PlayerInfos (Captures information on the player) →
6 Steps to be validated by player

The script functions

This guide is intended to show how to use the scripting capabilities of the ARCC, Advanced Ryzom Content Creator. It is recommended to read the volume I for having an overview of the use of the ARCC. The functions of the script are classified into five groups.

Visualizations
Actions without player intervention
Checks
Captures information
Steps to be validated by player

Visualizations

This group has only one function, one of the simplest and most common.

It serves as a reference with regard to the areas and buttons common to all functions detailed in separate pages for an easy maintenance of the ARRC documentation.

Common objects will be reported in the documentation by [common].
The tag [expert] corresponds to the advanced editing mode (see below paragraph 10).

window title and function name

The edit mode is also indicated by an icon alongside the function which was published in this mode.

weVMessage (Displaying a message)

Internal function name: weVMessage

window title and function name

This function displays a message in a WebIG window, with a title (in the sample here: Unit_test: " May the Force be with you " )

weVMessage_v3

1) [commun] Function name.
2) [expert] Always display this message (Yes/No)
3) [expert] Player must click the link in the message (Yes/No)
4) Text field for the message.

Text field

5) [commun] enlargement zone corner (4)
6) [commun] toggle button editor. (assisted mode or not)

7) [expert] Type of message content:

bbcode (recommended; an aide-memoire of ryzom bbcode is provided in a dedicated page.)

Exemple :
[session=url_validated][scriptinfos]is_valid_url[/scriptinfos][/session]

html (Specific, studied later, but immediately testable in web page)

Exemple :
<hr/>Hello!
<br/>this is a new line
<hr>External link!
<img src="http://wiki.blender.org/skins/naiad/images/blender_logo.png"/><hr/>

lua (very specific; to see later)

Exemple :
[lua]
function game:onMissionSelected(index)
disableModalWindow()
self:updateCurrMissionComboBox()
local missionWnd = getMissionWindow()
setOnDraw(missionWnd, "game:updateArccMissionCustomDesc()")
end
...
updateArccMissionCustomDesc_loop = 100
game:updateArccMissionCustomDesc(1)
[/lua]

8) [commun] Internal name of the function. This name is used especially for jumps, loops ...
9) [commun] Save Changes button.
10) [commun] toggle the "Basic Edition" mode to "Advanced Edit" mode.

Once in "Advanced Edit" mode, it is no longer possible to return to the "Basic Edition" mode.

The description of functions in that guide will always be in "Advanced Edit" mode. The specific "Advanced objects" are indicated by [expert]