EncyclopAtys - User contributions [en]

Category:Events

2025-01-21T10:38:56Z

Ledania:

{{Trad
|DE = Kategorie:Ereignisse |DEs= 4
|EN = Category:Events |ENs= 4
|ES = Category:Eventos |ESs= 4
|FR = Category:Événements |FRs= 4
|RU = Category:События |RUs= 4
|H =
|palette=
|ref=
|com=
}}
This is a category for everything related to events.
[[Category:Animation]] [[Category:Event Team]]

Event:Refugee Days

2025-01-21T10:25:48Z

Ledania:

<noinclude>
{{Trad
|DE = Event:Flüchtlingstage |DEs= 0
|EN = Event:Refugee Days |ENs= 0
|ES = |ESs=
|FR = Événement:Fête des réfugiés |FRs=
|RU = |RUs=
|H =
|palette=
|ref=
|com= FR (2020) and EN (2011) versions are very different
}}</noinclude>

{{quotation|website|
The Refugee Days celebration will soon be here! This is the time that we celebrate having made the perilous journey to secure our future in the new lands and explore the past of our ancient history. Following are some of the special events lined up for Refugee Days*.

Gubunnies: Docile gubunnies appear to spawn about every 5 Jena years and are known to leave special gifts wrapped in decorated yber eggs in random locations throughout the lands. These special gifts are a boon to all homins and therefore, Refugee Days coincides with their spawn. It is unknown where these gubunnies come from and what their plan might be, but whatever it is it can't be bad! Can it?

Scenic Challenges: Exploring is the wanderlust skill that all refugees posses. Without this desire to seek and learn many discoveries would have been left unknown. Throughout the celebration, you can test your visual knowledge of the flora, fauna and landmarks of Atys with 4 different challenges. The level 1 challenge has you searching for Wa Ji-Do throughout the "calmer" regions of Atys starting in Zora. The level 2 challenge starts in Pyr as you hunt for Zekollo through the wilds of the lesser used regions of Atys. Yrkanis is the start of the level 3 challenge where Bevaldo tests your skills in the more formidable areas of Atys. Thoddan's search, the level 4 challenge, starts in Fairhaven and takes you to the most arduous locations on the surface of Atys. To begin a challenge look for the first hint near a city tourist guide. You can only participate in each challenge one time. For all that finish any of the challenges a special gift will be rewarded. An additional surprise will be given to the homin that finishes each level first.

Celebration Outfitter: Don't miss your opportunity to receive a special outfit made especially for the Refugee Days celebration. An outfitter will be traveling around Atys to make 10 lucky homins signature refugee gear. During the celebration the outfitter will oversee various games to determine the winners.

Corrah Egg Hunt: Unravel an ancient folklore tale of Borrah and her daughter Corrah as the tale is recreated for your pleasure. In this modern variation, Corrah's nest has been looted and it is your job to help locate all her eggs and find the one responsible for this dastardly deed!

Petting Zoo: All refugees learn quickly that recognizing the aggressive and non-aggressive creatures can mean the difference between a pleasant stroll and resurrection sickness. Due to the nature of of the agressive critters, we rarely get to see their most striking features, at least not for long. That will soon change as the Magical Menagerie has returned to Atys, in miniature! Check out cute and cuddly pet-sized versions of the most fearsome beasts of Atys.
Disclaimer: Management not responsible for possible damage to homin or property.

[*] 22 - 25 April}}

<noinclude>
[[Category:Special events]]

</noinclude>

Magical Menagerie

2025-01-21T10:12:01Z

Ledania: /* The display */

<noinclude>{{Trad|DE=Magische Menagerie|EN=Magical Menagerie|palette=RP|H=1}}</noinclude>
The '''Magical Menagerie''' was a display of [[Bosses of Atys|bosses and nameds]] from all around Atys at the end of the [[Event:Firewine Fest|Firewine Fest]] and then made available again during [[Event:Refugee Days|Refugee Days]] and was called the '''Miniature Magical Menagerie'''. This version of the menagerie contained miniaturised versions of the creatures along with some new appearances in the display.

{{quotation|Menagerie Barker|
Ladies and gentlemen, travellers from afar welcome to the Greatest Show on [[Atys]], the Magical Menagerie!

Here you will find the fantastical creatures from the far corners of Atys. Many of these creatures have never been seen on the bark and they are all yours to gander at for the low price of 10 tickets! Feast your eyes on the delights Atys has to offer!

Today's show will be free of charge due to the kind actions of homins locating our prized beasts.

The Management}}

==The display==
Below is a list of all the displays and their given descriptions that has remained unchanged during all appearances of the Magical Menagerie.

; Bawakya : Don't bite off more than you can chew with this one! This is a creature from the depths of the jungle with skin that glimmers of gold and an adorned spine. It many groan and wheeze but can still dispatch you with its many minions.

; CSR : This endangered species does not handle complaints from homins well and is best left alone. If this exhibit is empty, the CSR has escaped and should be hunted down.

; Cuttlekin : A special delivery from the Nexus! This carnivorous boss was not captured easily and transporting him is a dangerous undertaking. Though his name closely suggests a warm gesture, we recommend keeping your distance.

; Goakan : Be shocked and amazed! This beast will give you a powerful jolt if you venture too close. The bulb dangling from its head should be your warning to give it the space if needs in the [[Lagoons of Loria]].

; Hornkoo : The winds howl through the place of the gate one might venture in but it might also seal one's fate. For out of the Halls of Darkring comes this creature you will not want to see. The darkness however, cannot hid you from this bright blue critter so you had better run if you want to escape.

; Kinkoo : [[Kinrey]]s are a force to be reckoned with, but Kinkoo takes the cake and eats it too when it comes to pure nastiness. Hidden in a tree-stump, he is a popular destination for homins gathering materials.

; Rakya : Rarely seen! Not as large and powerful as most of the creatures in our collection, this [[ragus]] king is one of our prized pieces as many believe he only exists as a myth. Many have claimed to hear its howls but few are the ones that have seen it, and lived to tell their tale.

; Tyrakoo : This terrifying creature with a mouth rimmed with teeth and thought to be mostly blind can only be found in the deepest parts of the Prime Roots.

; Vorkoo : Seeing is believing! This colossal giant is from the dank dark of the Prime Roots and is a force to be reckoned with. It enjoys feeding on homins and is known for its particular taste for [[Tryker]]s. If its size doesn't scare you then its teeth surely will. If not, the you are either a brave homin or one with a death wish. If you are the latter, then we bid you adieu.

; Vulca : Special attraction! Be weary of this monster's noxious breath. [[Jugula]]s are famous for giving out lingering pain.

; Wylin : Here is a [[Zerx]] that will eat you as soon as it looks at you. All the way from the [[Lands_of_Umbra#Gate_of_Obscurity|Gates of Obscurity]], Wylin has made a meal of more than one enterprising forager.

; Yetikya : From the dampness of the Void, this yetin boss will not willingly let you leave its domain.

===Firewine Fest===
These creatures were only displayed during the [[Firewine Fest]].

; Death Clopper : Though commonly found in the lakes this death [[clopper]] avoided the butter sauce by dancing on command. Unfortunately, the management failed to also purchase the commands when they secured their possession. We will gladly pay in [[dapper]]s to anyone who can figure out a command. The Management

; Kizokin : Gaze in wonder at this [[kizoar]] as he dips and dives, spears and flies. This boisterous blue bug is friendly enough to pet. Just don't get too rough!

; Slyk : [[Varinx]] are cuddly creatures normally, but Slyk is the black yubo of the family and does not care much for visitors. Or being petted.

; Spinah : Curious and strange, if you visit the [[Maiden Grove|Grove of the Maiden]] you may just see this brute with its large protruding mandible.

===Refugee Days===
These creatures were only displayed during [[Event:Refugee Days|Refugee Days]].

; Clopperketh : Clopperketh replaces our dancing clopper as we never could figure out the commands. This clopper is unique in that she only turns on you if you bother her children in the desert dunes.

; Izakoo : This [[izam]] is currently the only flying creature in our collection. Though he looks brilliant in the sun, do not let him fool you; with his stripes he can camouflage quite easily.

; Najakya : Our newest creature to our collection, Najakya hails from the jungle tropics. The bright colors should stand as a warning but more oft than not they lure in unsuspecting homins.

; Ocyketh : Thought to be the stuff of legends, this great blue ocyx's bite is worse than it's growl!

; Rendokin : This tiny Rendokin has a powerful kick but yet an usually passive beast. His unusual sheen is due to the lichen that find his hide home.

; Torkan : This feline might look cute and cuddly but don't stand too close or you will be its next meal.

==See also==
* [[Event:Firewine Fest|Firewine Fest]]

[[Category:Firewine Fest]]

Event:Dark Preparations

2025-01-21T08:07:31Z

Ledania: /* Second caravan */

[[Image:Event-DarkPreparations2.jpg|thumb|right|300px|Players battling Marauders in the Prime Roots]]<noinclude>{{Trad|DE=Event:Dunkle Vorbereitungen|EN=Event:Dark Preparations|palette=RP|H=1}}</noinclude>
Dark Preparations was an event that took place during August 2011. In this event, the [[Marauders]] made preparations to once again invade the [[New Lands]], and the players were tasked with stopping them. (Or, if they so chose to, aiding them.)

Having failed to conquer the New Lands several times already, the Marauders' plan this time was to arm local rebel factions to fight for them. To this end, they sent an escorted caravan of weapons to each of the 4 [[nations]] that the rebels would use to attack with. The actual attacks took place in the next [[Event:Ultimate Provocation]].

==Part 1: The meeting==
The event started with a '''Zoraï informant''' warning homins of the Marauders' plans. This Zoraï informant was a defected member of a rebel Zoraï faction known as the Syndicate of Despair<ref>http://atys.ryzom.com/start/app_forum.php?page=topic/view/8278/#1</ref>, one of the rebel faction that was going to have a secret meeting with the Marauders<ref>http://atys.ryzom.com/start/app_forum.php?page=topic/view/8318/#1</ref>.

:''Sunday, 14 August, 2011.''
Disguised players attended this secret meeting in the [[Prime Roots]], and learned there that caravans loaded with Marauder weapons would make their way into the New Lands. After receiving these caravans, the rebel factions would then prepare their assaults on the respective nations. Rewards were promised to those who helped escort the caravans.

==Part 2: The caravans==
The Zoraï informant warned the players of the approximate times that each caravan would arrive<ref>http://atys.ryzom.com/start/app_forum.php?page=topic/view/8318/#2</ref>, but could not tell the exact time or destination or the route they would take. Thus players had no choice but to guard and scout as many places as possible and hope they would catch the caravans in time.

===First caravan===
:''Friday, 19 August, 2011.''
:To '''Syndicate of Despair, [[Witherings]]'''

The first caravan was spotted just as it entered [[Void]] through the tunnel from [[Wastelands]]. It is engaged and destroyed as it reaches [[Lost Valley Stronghold]], but this turned out to be too late, as the packers with the weapons escaped during the battle and reached their destination.

===Second caravan===
:''Sunday, 21 August, 2011.''
:To '''Cynics of Liberty, [[Aeden Aqueous]]'''

Better knowing what to expect this time, and with fewer routes to watch, scouts already spotted the second caravan deep in [[Trench of Trial]]. This allowed assault parties to harass the caravan in the Prime Roots and weaken it before it could reach the tunnel to [[Bounty Beaches]]. Upon exiting the tunnel, what was left of the caravan was immediately destroyed by the defenders that laid in waiting. The contents of the caravan is captured and distributed amongst the victors.

===Third caravan===
:''Friday, 26 August, 2011.''
:To '''Coalition of Flames, [[Burning Desert]]'''

Despite people guarding the portals from the Prime Roots to the desert, the third caravan reaches it's destination without ever being spotted. Rumours abounded that it exited the Prime Roots at [[Knoll of Dissent]] and travelled to the desert through [[Hidden Source]], with the approval of the Matis.
[[Image:Event-DarkPreparations1.jpg|thumb|right|200px|The caravan runs into the blockade.]]
===Fourth caravan===
:''Sunday, 28 August, 2011.''
:To '''Council of Dissent, [[Verdant Heights]]'''

The fourth caravan is already spotted deep in [[Wastelands]], and is trailed by scouts as it travels through [[Nexus]] and [[Abyss of Ichor]]. Due to the extraordinary speed with which this caravan travels, defenders decide not to attempt to intercept it en route but to set up a defensive line at to north end of Abyss of Ichor. The caravan fails to breach this line and is destroyed before ever setting foot in the forests. The contents of the caravan is once again captured and distributed amongst the victors.

==Outcome==
[[Image:PerfectMaterial.jpg|thumb|right|100px|Check out the stats on that thing!]]
Three of the four caravans were destroyed, though only two in time to stop them from delivering their cargo. The Marauder Lackeys in charge of the caravans were killed in all three cases, as were all the Marauders escorting the caravans. The two caravans that were captured obtained quantities of a perfect generic raw material, with literally perfect attributes for [[crafting]] with.

This Event continued in [[Event:Ultimate Provocation]].

== References ==
<references/>

[[Category: Events]]

Deep Fyros diplomacy

2024-11-03T20:28:01Z

Ledania:

<noinclude>{{WIP}}{{Trad
|DE=Fyros-Diplomatie in der Tiefe |DEs=4
|EN=Deep Fyros diplomacy |ENs=4
|ES= Deep Fyros diplomacy |ESs=
|FR=Diplomatie Fyros en profondeur |FRs=4
|RU= Deep Fyros diplomacy |RUss=
|palette=fyros
|H=1}}{{Clear}}
{| style="float:left; margin-right: 10px;"
|-
| __TOC__
|}
</noinclude>

== Announce ==
[https://app.ryzom.com/app_forum/index.php?page=topic%2Fview%2F33241%2F210348&lang=en Forums » OFFICIAL NEWS » Events » (Fyros) Deep Fyros diplomacy (2024-10-27)
<poem>
Creator of the event: Player [[User:Azazor|Azazor]] and Event Team.
Type of event: Investigation and PvE.
Appropriate levels: For all. The lower levels may need to join a team.

Date of the event: Sunday, 27 October + Monday, 28, 21:00:00 CET 2024. Expected duration: About 2 hour(s).
Meeting place: [[Dyron]], [[Dunes of Exile]], Burning Desert.

Homins concerned: Fyros patriots, akenakos, friends of the Fyros.
'''Synopsis''': A quarrel is about to break out between the Empire and the [[Root Tappers]]. A diplomatic mission must go there and resolve the situation with a civilian escort to avoid poisoning relations.
'''Please note''': Due to the length of the event, the end of the event will probably have to be postponed until the following day.
</poem>

==Report==
From our special reporter, the Ranger [[User:Craftjenn|Craftjenn]]

See French pages for full logs (from 20h56:10 to 23h23:57 Paris time), October 28th 2024: [[:fr:Diplomatie Fyros en profondeur/Ch1-Dyron|Dyron]] • [[:fr:Diplomatie Fyros en profondeur/Ch2-Go PR|Camp des Saigneur]] • [[:fr:Diplomatie Fyros en profondeur/Ch3-Bandits|Bandits]] • [[:fr:Diplomatie Fyros en profondeur/Ch4-Piste|Une piste ?]]

I arrived in Dyron late in the evening from '''Tria, Nivia 27, 4th CA 2630''', on a beautiful starry winter's night.

'''Present''' at the time were: Thelotis Midix ([[User:Margote|Margote]]), Pephoan Kridix ([[User:Pavor|Pavor]] also played the bandit leaders and the Underspring Lynchers witness) and Diobus Apocaps (was played by [[User:Baranil|Baranil]]), [[User:Azazor|Azazor]] and (in order of arrival in the league): Bezzo, Lyren, Chenli, Pogofishmage, Vanixia and Marisia, Ynel, Tapioca, Karry, Jorgensen, Lorlyn, Chanchey, Sharixx, Denrak, Aistar, Kamora, Ados and Sildo, Eolinius, Hayt, Tarka, Baffos, Lyrasse, Craftjenn and Dykocus, Kiriselly and Vortexselly, Zeezee, Concho, Elainia, Adaira, Atrox, Yumy, Shalla, Zephira, Nisroch, Nymphe, Kyrean, Missylee, Sleepygirl, Muscles, Nutsy, Zimbo, Mano, Elke, Noqa, Ashgan, Imotep, Golika, Altrix, Geveda, Grundelwolf.

We waited for [[Pephoan Kridix]], who arrived in the middle of the night (around 2am). He explained that relations with the Lords of the Roots had become strained recently, and their latest water convoy had not reached us [1]. [[Thelotis Midix]] discovers that she is here to check with the [[Root Tappers]] to see what has happened to the convoy. At around 6am, it was decided who would lead our troop: it would be Ambassador Lyren.

At around 7.45am, we're north of the Dunes of Exile, near the Vortex leading north to the Forbidden Springs. We arrive at the camp of the Root Lords at around 11am. Thelotis Midix asks their leader, Diobus Apocaps, what has happened. Diobus says that a caravan has left - and that they're waiting for them to return and for payment (which she thinks is cheap, given the dangers). Azazor then makes a comment, which Diobus does not take kindly to. But that doesn't stop Diobus from asking us to go and look for them (from here to Dyron)... Thelotis Midix wants to go and question the local bandits - the Underspring Lyhnchers will be questioned very seriously. But Lyren prefers to finish with them, given his map.

Shortly before 4pm, we cross the lake towards the Cooky's Cranks camp.

After killing a pat and most of the bandits, Lyren and Azazor question their leader (with a few slaps), who claims not to have done anything, and accuses the bandits of being evil. He also says that they've been supplying Dyron for a long time, and that they don't want any fewer homins passing through here... Lyren believes him, while Azazor claims it's because these Trykers are too weak and small to attack this kind of convoy... Ashgan insists "if only it were a convoy of Byrh, at the very least...". However, Azazor delivers a diplomatic mandal to the tryker, who ends up giving (at random) the name of the Silencers.

We massacred another pat, and set off for the Silenciers camp - it was around 11pm...

2.20am, Quarta, Nivia 28, (4th CA 2630): we arrive near the Silencers' camp. An hour later, all the bandits are dead and we question their leader (the one who lets the others fight)... Brought to his knees by Lyren, he says that one of their scouts said he saw the convoy, far from here, to the north of the hole in the dead trees, but that they didn't attack it. Their leader, looking at Lyren, says he won't forget him...

So we set off north, for the Underspring lyncher camp. We arrived in the morning. Around midday, their leader called us barbarians, and a witness showed us where he'd seen homins emerging from the ground... We arrived near the OP at around 6pm.

We decide to take a rest and resume the investigation later.

=== Lucios ===
<gallery caption="Chapitres 1 to 4">
DeepFDiplo-2024-10-27-21h12-33-Wait.png|Waiting Kridix, (late)
DeepFDiplo-2024-10-27-21h17-11-Kridix.png|Thelotis Midix (of the chamber of justice) and Kridix (Fyros captain)
DeepFDiplo-2024-10-27-21h28-55-Lyren.png|Ambassador Lyren will lead us to the camp and head up Fyros diplomacy. D
DeepFDiplo-2024-10-27-21h33-40-VortexDune.png|At around 7.45am, we're north of the Dunes of Exile, near the Vortex.
DeepFDiplo-2024-10-27-21h35-38-SI.png|Arrival (and short break) in the [[Under Spring]]
DeepFDiplo-2024-10-27-21h44-50-Saig.png|In the camp of the [[Root Tappers]]
DeepFDiplo-2024-10-27-21h44-03-Camp.png|Thelotis talk to their chief, Diobus Apocaps
DeepFDiplo-2024-10-27-21h59-02-Cooky'sCranks.png|Arrival near the Cooky's Cranks camp (bandits)
DeepFDiplo-2024-10-27-21h59-51-KillCooCranks.png|Fyros diplomacy in practice: first you hit, then you talk
DeepFDiplo-2024-10-27-22-09-34-CooCranChief.png|their leader talks to us about Silenciers
DeepFDiplo-2024-10-27-22-15-45-HominCooCr.png|the homins present discuss their answers: they are too small to attack a water convoy - and, at the very least, if it was a beer convoy...
DeepFDiplo-2024-10-27-22h33-24-SilenciersChief.png|The leader of the Silenciers is then questioned
DeepFDiplo-2024-10-27-23h06-56-UnderspringLynchers.png|Underspring Lynchers camp: a witness will show us where he saw strange things
DeepFDiplo-2024-10-27-22h59-20-witness.png|un témoin va nous montrer là où il a vu des choses étranges
DeepFDiplo-2024-10-27-23h17-13-NearOP.png|Near the OP, we'll meet up later
</gallery>

<gallery caption="Chapitres 5 to 8">
DeepFDiplo-2024-10-28-21h25-20-Hole.png|Nous trouvons un trou (et sautons dedans)
DeepFDiplo-2024-10-28-21h29-Map.png|The "Hole" map
DeepFDiplo-2024-10-28-21h35-28-Issue.png|Arrêtez de taper des armas
DeepFDiplo-2024-10-28-21h36-Pat.png|Un nid de Kitin ou une énorme pat ?
DeepFDiplo-2024-10-28-21h45-11-FoundThem.png|Nous avons trouvé le convoi, tous morts !
DeepFDiplo-2024-10-28-21h45-BodyNoHead.png|Un corps trouvé, sans tête...
DeepFDiplo-2024-10-28-21h50-23-fyrak.png|Dans un étrange brouillard, Azazor accuse ces "ces foutus adorateurs du [[Grand Dragon]]"
DeepFDiplo-2024-10-28-21h53-38-dead.png|Tués par l'énorme [[pat]],
DeepFDiplo-2024-10-28-21h57-17-Rez.png|... on rez tous au Vortex nord des Sources Interdites
DeepFDiplo-2024-10-28-21h57-26-Hot.png|Chaud devant ! (attaque de tyrancha)
DeepFDiplo-2024-10-28-22h03-15-Blocks.png|La sortie est bouchée par d'énormes blocs
DeepFDiplo-2024-10-28-22h04-36-grouped.png|Comme toujours, on n'est pas très groupés...
DeepFDiplo-2024-10-28-22h11-15-OfloByrh.png|Rapport au camp, une plainte des brasseurs d'Oflovak :/
DeepFDiplo-2024-10-28-23h00-DyronEnd.png|Pour finir, un pot au bar de Dyron avec Kridix
</gallery>

== Notes and links ==
More on wikis:
* [[Root Tappers]]
* [[Pephoan Kridix]]
* [[Street show]]
and on the forum
* [https://app.ryzom.com/app_forum/index.php?page=topic/view/31530/1#1 The lost expedition]
* [https://app.ryzom.com/app_forum/index.php?page=topic/view/31877/1#1 Tracing the trail of his brethren in blood]

{{clear}}

<noinclude>
{{last version link|Deep Fyros diplomacy}}
{{Portal|Animation}}
[[Category:Events]]</noinclude>

Menia Pyron, engaged Fyros

2024-10-31T02:12:24Z

Ledania:

<noinclude>{{Trad
|DE=Menia Pyron, engagierte Fyros|DEs=4
|EN=Menia Pyron, engaged Fyros|ENs=0
|FR=|FRs=
|ES=|ESs=
|RU=|RUs=
|palette=fyros
|H=1}}</noinclude>
__NOTOC__
{{quotation|''interview with Menia Pyron, a young engaged Fyros.''|
:''Today our social reporter brings you an exclusive insight in the ceremony and symbolism involved in arranging a wedding in Fyros. She interviewed Menla Pyron, a bride who will be getting married next week.''

'''Interviewer:''' So is the [[Fyros]] wedding ceremony religious-based? Are the [[Kami]] involved?

'''Menia Pyron:''' No, – it is not like that really.

Our weddings are steeped in historical tradition but they do not have any religious undertones. Weddings are civil acts and although devoid of any spiritual ritual, are celebrated by the whole community as we understand that marriage enhances the solidarity of the community so increasing its capacity to contribute to the state.

Well, that is what it says in the book I was given but basically we get married because we love each other and we want to become part of the community as a couple.

'''Interviewer:''' Tell me a little bit about the build up you have just come through?

'''Menia Pyron:''' Oh this is really fun! .The engagement period usually lasts for about two months during which we had to overcome a certain number cleverly thought out difficulties together. This allowed us to find out if we actually got on together and could work with each other. The tasks were set by a mutual friend of our parents, if you like an elder of the community. And boy did she come up with some tough challenges for us. But we made it through and now we are more in love than ever! After this the banns were published and the invitations sent out asking our guests to share our joy next week.

'''Interviewer:''' And the wedding itself?

'''Menia Pyron:''' Here, traditionally the celebrations can last an entire week, from [[Holeth]] to Holeth. According to our best warrior traditions, it is technically my husband who marries me, but that’s so old-fashioned now and the law has recently been changed to reflect this making sure that we both give typically, we choose to get married in spring or autumn. As the days are more clement and it is not so hot for the dancing and partying.

We prefer a wedding set around a sacred fire, to bring us closer to our roots in the past, I have picked [[Pyr]] gate for mine! This is quite a popular spot and sometimes you will even see wedding parties waiting their turn here, but I have made an arrangement. Oh and we mustn’t see each other all the day up until the ceremony – that would bring shocking bad luck so the two processions of relatives, friends and witnesses will assemble in different places.

Then we all sit around in two semicircles with on the left hand the females, and on the right the males, and the wedding ceremony begins. Of course we exchange rings as a symbol of our love as an unbroken circle and my husband will wear his best uniform and weapons. In fact, in the ceremony itself he pledges me his sword – It’s a lovely moment and I can hardly wait! Me? Oh my finest dress and jewels, I’ve managed to talk daddy into a very nice new outfit!

The guests too of course will all dress up to the nines in an attempt to outdo each other, and the pictures are always a splash of colour.

My mother’s old friend will be conducting the ceremony, we normally have someone of status in the community to do this and it will be lovely to be married by someone who has known me since I was a baby in a carved crib.

Hmm what else? Oohh I know, presents! Well the guests used to give money, but it is also becoming increasingly customary to give finely crafted objects instead.

This bit is really funny, in the evening I am “sold” by my best five female friends who put on their finest medium armour and dance for the assembly collecting money and gifts for me and my new husband. This is always a riot!

Then we have fireworks and singing and dancing and sometimes people compose special poems and songs to perform in the evening. I am really hoping some of our more creative guests will do this for us!

'''Interviewer:''' Menla, thank you very much for sharing your big day with us, we wish you all joy and happiness for the future.}}

{{The Chronicles of Atys}}

[[Category:Lore]]
[[Category:Chronicles of the New Beginning]]
[[Category:Chronicles]]
[[Category:Chronicles of the Burning Desert]]

Menia Pyron, engaged Fyros

2024-10-31T02:11:44Z

Ledania:

<noinclude>{{Trad
|DE=Menia Pyron, engagierte Fyros|DEs=4
|EN=Menia Pyron, engaged Fyros|ENs=2
|FR=|FRs=
|ES=|ESs=
|RU=|RUs=
|palette=fyros
|H=1}}</noinclude>
__NOTOC__
{{quotation|''interview with Menia Pyron, a young engaged Fyros.''|
:''Today our social reporter brings you an exclusive insight in the ceremony and symbolism involved in arranging a wedding in Fyros. She interviewed Menla Pyron, a bride who will be getting married next week.''

'''Interviewer:''' So is the [[Fyros]] wedding ceremony religious-based? Are the [[Kami]] involved?

'''Menia Pyron:''' No, – it is not like that really.

Our weddings are steeped in historical tradition but they do not have any religious undertones. Weddings are civil acts and although devoid of any spiritual ritual, are celebrated by the whole community as we understand that marriage enhances the solidarity of the community so increasing its capacity to contribute to the state.

Well, that is what it says in the book I was given but basically we get married because we love each other and we want to become part of the community as a couple.

'''Interviewer:''' Tell me a little bit about the build up you have just come through?

'''Menia Pyron:''' Oh this is really fun! .The engagement period usually lasts for about two months during which we had to overcome a certain number cleverly thought out difficulties together. This allowed us to find out if we actually got on together and could work with each other. The tasks were set by a mutual friend of our parents, if you like an elder of the community. And boy did she come up with some tough challenges for us. But we made it through and now we are more in love than ever! After this the banns were published and the invitations sent out asking our guests to share our joy next week.

'''Interviewer:''' And the wedding itself?

'''Menia Pyron:''' Here, traditionally the celebrations can last an entire week, from [[Holeth]] to Holeth. According to our best warrior traditions, it is technically my husband who marries me, but that’s so old-fashioned now and the law has recently been changed to reflect this making sure that we both give typically, we choose to get married in spring or autumn. As the days are more clement and it is not so hot for the dancing and partying.

We prefer a wedding set around a sacred fire, to bring us closer to our roots in the past, I have picked [[Pyr]] gate for mine! This is quite a popular spot and sometimes you will even see wedding parties waiting their turn here, but I have made an arrangement. Oh and we mustn’t see each other all the day up until the ceremony – that would bring shocking bad luck so the two processions of relatives, friends and witnesses will assemble in different places.

Then we all sit around in two semicircles with on the left hand the females, and on the right the males, and the wedding ceremony begins. Of course we exchange rings as a symbol of our love as an unbroken circle and my husband will wear his best uniform and weapons. In fact, in the ceremony itself he pledges me his sword – It’s a lovely moment and I can hardly wait! Me? Oh my finest dress and jewels, I’ve managed to talk daddy into a very nice new outfit!

The guests too of course will all dress up to the nines in an attempt to outdo each other, and the pictures are always a splash of colour.

My mother’s old friend will be conducting the ceremony, we normally have someone of status in the community to do this and it will be lovely to be married by someone who has known me since I was a baby in a carved crib.

Hmm what else? Oohh I know, presents! Well the guests used to give money, but it is also becoming increasingly customary to give finely crafted objects instead.

This bit is really funny, in the evening I am “sold” by my best five female friends who put on their finest medium armour and dance for the assembly collecting money and gifts for me and my new husband. This is always a riot!

Then we have fireworks and singing and dancing and sometimes people compose special poems and songs to perform in the evening. I am really hoping some of our more creative guests will do this for us!

'''Interviewer:''' Menla, thank you very much for sharing your big day with us, we wish you all joy and happiness for the future.}}

{{The Chronicles of Atys}}

[[Category:Lore]]
[[Category:Chronicles of the New Beginning]]
[[Category:Chronicles]]
[[Category:Chronicles of the Burning Desert]]

Menia Pyron, engaged Fyros

2024-10-31T02:11:22Z

Ledania:

<noinclude>{{Trad
|DE=Menia Pyron, engagierte Fyros|DEs=4
|EN=Menia Pyron, engaged Fyros|ENs=1
|FR=|FRs=
|ES=|ESs=
|RU=|RUs=
|palette=fyros
|H=1}}</noinclude>
__NOTOC__
{{quotation|''interview with Menia Pyron, a young engaged Fyros.''|
:''Today our social reporter brings you an exclusive insight in the ceremony and symbolism involved in arranging a wedding in Fyros. She interviewed Menla Pyron, a bride who will be getting married next week.''

'''Interviewer:''' So is the [[Fyros]] wedding ceremony religious-based? Are the [[Kami]] involved?

'''Menia Pyron:''' No, – it is not like that really.

Our weddings are steeped in historical tradition but they do not have any religious undertones. Weddings are civil acts and although devoid of any spiritual ritual, are celebrated by the whole community as we understand that marriage enhances the solidarity of the community so increasing its capacity to contribute to the state.

Well, that is what it says in the book I was given but basically we get married because we love each other and we want to become part of the community as a couple.

'''Interviewer:''' Tell me a little bit about the build up you have just come through?

'''Menia Pyron:''' Oh this is really fun! .The engagement period usually lasts for about two months during which we had to overcome a certain number cleverly thought out difficulties together. This allowed us to find out if we actually got on together and could work with each other. The tasks were set by a mutual friend of our parents, if you like an elder of the community. And boy did she come up with some tough challenges for us. But we made it through and now we are more in love than ever! After this the banns were published and the invitations sent out asking our guests to share our joy next week.

'''Interviewer:''' And the wedding itself?

'''Menia Pyron:''' Here, traditionally the celebrations can last an entire week, from [[Holeth]] to Holeth. According to our best warrior traditions, it is technically my husband who marries me, but that’s so old-fashioned now and the law has recently been changed to reflect this making sure that we both give typically, we choose to get married in spring or autumn. As the days are more clement and it is not so hot for the dancing and partying.

We prefer a wedding set around a sacred fire, to bring us closer to our roots in the past, I have picked [[Pyr]] gate for mine! This is quite a popular spot and sometimes you will even see wedding parties waiting their turn here, but I have made an arrangement. Oh and we mustn’t see each other all the day up until the ceremony – that would bring shocking bad luck so the two processions of relatives, friends and witnesses will assemble in different places.

Then we all sit around in two semicircles with on the left hand the females, and on the right the males, and the wedding ceremony begins. Of course we exchange rings as a symbol of our love as an unbroken circle and my husband will wear his best uniform and weapons. In fact, in the ceremony itself he pledges me his sword – It’s a lovely moment and I can hardly wait! Me? Oh my finest dress and jewels, I’ve managed to talk daddy into a very nice new outfit!

The guests too of course will all dress up to the nines in an attempt to outdo each other, and the pictures are always a splash of colour.

My mother’s old friend will be conducting the ceremony, we normally have someone of status in the community to do this and it will be lovely to be married by someone who has known me since I was a baby in a carved crib.

Hmm what else? Oohh I know, presents! Well the guests used to give money, but it is also becoming increasingly customary to give finely crafted objects instead.

This bit is really funny, in the evening I am “sold” by my best five female friends who put on their finest medium armour and dance for the assembly collecting money and gifts for me and my new husband. This is always a riot!

Then we have fireworks and singing and dancing and sometimes people compose special poems and songs to perform in the evening. I am really hoping some of our more creative guests will do this for us!

'''Interviewer:''' Menla, thank you very much for sharing your big day with us, we wish you all joy and happiness for the future.}}

{{The Chronicles of Atys}}

[[Category:Lore]]
[[Category:Chronicles of the New Beginning]]
[[Category:Chronicles]]
[[Category:Chronicles of the Burning Desert]]

Event:Memorial Service for Merrielyn/Rivendell

2024-10-31T01:40:49Z

Ledania:

<noinclude>{{Trad
|DE=Event:Gedenkveranstaltung für Merrielyn/Rivendell |DEs=4
|EN=Event:Memorial Service for Merrielyn/Rivendell |ENs=0
|ES=Evento:Servicio Memorial por Merrielyn/Rivendell |ESs=4
|FR= |FRs=
|RU= |RUs=
|palette= matis
|H=
}}</noinclude>
[[Image:Event-MemorialService1.jpg|thumb|right|300px|The Memorial Service.]]
At Saturday, 28 August, at 19:00 GMT, an ingame memorial service was held for a longtime Ryzom player and volunteer CSR (Customer Service Representative) who had passed away a week earlier.

The procession started at the gates of [[Yrkanis]] and headed to an open field in [[Majestic Garden]]. There an area was set up specially for the memorial.

Numerous players held speeches that, all together, lasted several hours. A memorial plaque was erected where people could leave their farewell messages. The memorial event was concluded with fireworks and the releasing of Merrielyn's CSR mount.

==Official Announcement==
{{quotation|Official Website<ref>http://atys.ryzom.com/news/290</ref>|
A mounted memorial procession and service will be held in honor of GM/EG Merrielyn/Rivendell, HO of TheNewEmpire, on 28 August at 19:00 GMT leaving from the Yrkanis gates. All homins, with or without a mount, are invited to share in the Ryzom tribute and farewell to our beloved friend.
}}

==Event Summary==
[[Image:Event-MemorialService2.jpg|thumb|right|200px|Setting off the fireworks.]]
Players gathered at the gates of [[Yrkanis]], many of them bringing their mounts for the procession. Originally the plan had been to move to Virginia Falls in [[Hidden Source]] and have the memorial there. But instead the procession headed to the location set aside in [[Majestic Garden]], just off the crossroads, northwest of the Arena and west of the [[Green Seed]] camp.

Players were invited to share their stories about their lost friend, and many players took the stand to tell of their own experiences.
:'''If anyone has a log of these stories, you are encouraged to add it to this article.'''

The memorial event was attended by probably more players than had been seen together in Ryzom in many months, as well as by a lot of CSRs, including some from the other servers.

At the end, all the players present were given fireworks and asked to form two lines. As they set off the fireworks, Merrielyn's Tenwo (CSR [[mektoub]] mount) was lead through the lines to be released into the wild.

Lastly, all players were encouraged to share their last goodbyes at the memorial plaque, which linked directly to the forum thread set aside for that purpose on the ingame forums.

[[Image:Event-MemorialService5.jpg|300px|The players set up in two lines.]] [[Image:Event-MemorialService4.jpg|300px|Writing last goodbyes on the plaque.]]

[[Image:Event-MemorialService3.jpg|thumb|right|200px|Tenwo wanders past the plaque.]]
===Aftermath===
Though most of the memorial site was only temporary and disappeared again after the event, the memorial plaque (in the shape of a [[Ring]] terminal) remains at the location permanently. Clicking it still takes a player directly to the forum thread with all the last goodbyes.

Merrielyn's Tenwo, which was released into the wild, also remained as a permanent reminder, and can still be found peacefully wandering the area around the memorial site in [[Majestic Garden]].

= See also =
* [http://forums.ryzom.com/showthread.php?t=35064 Farewell Merrielyn] - Farewell thread on the official forums.
* [http://forums.ryzom.com/showthread.php?t=35075 Video of the memorial service] - Video of the memorial service on the official forums.
* [https://www.mmorpgitalia.it/threads/memorial-per-merrielyn-rivendell.278609/ Memorial per Merrielyn / Rivendell]
{{Quotation|Gilgameesh (on mmorpgitalia) |A beneficio di quei pochi italiani che hanno giocato in passato e possono ricordarlo, GM Merrielyn / Rivendell (HO The New Empire) / Carl Schofield ci ha lasciato qualche giorno fa.
Malato da molti anni e costretto a vivere in una carrozzella, è sicuramente stato uno dei Game Masters più amati dalla comunità.}}
* [https://vimeo.com/14535890 (Vimeo) by SaM.] R.I.P. friend. The sad and beautiful, virtual service for a lost Friend. Sorry for the slight choppiness. There were just too many homins and fireworks to handle for my rig. <ref>[https://vimeo.com/user633832 SaM on Vimeo]</ref>
{{Reflist|subpages=}}

[[Category:Special events|Memorial Service for Merrielyn/Rivendell]]
[[Category:Events]]
[[Category:Missing player]]
[[Category:Memorial]]

Deep Fyros diplomacy

2024-10-30T18:11:06Z

Ledania:

<noinclude>{{WIP}}{{Trad
|DE=Fyros-Diplomatie in der Tiefe |DEs=3
|EN=Deep Fyros diplomacy |ENs=4
|ES= Deep Fyros diplomacy |ESs=
|FR=Diplomatie Fyros en profondeur |FRs=4
|RU= Deep Fyros diplomacy |RUss=
|palette=fyros
|H=1}}{{Clear}}
{| style="float:left; margin-right: 10px;"
|-
| __TOC__
|}
</noinclude>

== Announce ==
[https://app.ryzom.com/app_forum/index.php?page=topic%2Fview%2F33241%2F210348&lang=en Forums » OFFICIAL NEWS » Events » (Fyros) Deep Fyros diplomacy (2024-10-27)
<poem>
Creator of the event: Player [[User:Azazor|Azazor]] and Event Team.
Type of event: Investigation and PvE.
Appropriate levels: For all. The lower levels may need to join a team.

Date of the event: Sunday, 27 October + Monday, 28, 21:00:00 CET 2024. Expected duration: About 2 hour(s).
Meeting place: [[Dyron]], [[Dunes of Exile]], Burning Desert.

Homins concerned: Fyros patriots, akenakos, friends of the Fyros.
'''Synopsis''': A quarrel is about to break out between the Empire and the [[Root Tappers]]. A diplomatic mission must go there and resolve the situation with a civilian escort to avoid poisoning relations.
'''Please note''': Due to the length of the event, the end of the event will probably have to be postponed until the following day.
</poem>

==Report==
From our special reporter, the Ranger [[User:Craftjenn|Craftjenn]]

See French pages for full logs (from 20h56:10 to 23h23:57 Paris time), October 28th 2024: [[:fr:Diplomatie Fyros en profondeur/Ch1-Dyron|Dyron]] • [[:fr:Diplomatie Fyros en profondeur/Ch2-Go PR|Camp des Saigneur]] • [[:fr:Diplomatie Fyros en profondeur/Ch3-Bandits|Bandits]] • [[:fr:Diplomatie Fyros en profondeur/Ch4-Piste|Une piste ?]]

I arrived in Dyron late in the evening from '''Tria, Nivia 27, 4th CA 2630''', on a beautiful starry winter's night.

'''Present''' at the time were: Thelotis Midix ([[User:Margote|Margote]]), Pephoan Kridix ([[User:Pavor|Pavor]] also played the bandit leaders and the Underspring Lynchers witness) and Diobus Apocaps (was played by [[User:Baranil|Baranil]]), [[User:Azazor|Azazor]] and (in order of arrival in the league): Bezzo, Lyren, Chenli, Pogofishmage, Vanixia and Marisia, Ynel, Tapioca, Karry, Jorgensen, Lorlyn, Chanchey, Sharixx, Denrak, Aistar, Kamora, Ados and Sildo, Eolinius, Hayt, Tarka, Baffos, Lyrasse, Craftjenn and Dykocus, Kiriselly and Vortexselly, Zeezee, Concho, Elainia, Adaira, Atrox, Yumy, Shalla, Zephira, Nisroch, Nymphe, Kyrean, Missylee, Sleepygirl, Muscles, Nutsy, Zimbo, Mano, Elke, Noqa, Ashgan, Imotep, Golika, Altrix, Geveda, Grundelwolf.

We waited for [[Pephoan Kridix]], who arrived in the middle of the night (around 2am). He explained that relations with the Lords of the Roots had become strained recently, and their latest water convoy had not reached us [1]. [[Thelotis Midix]] discovers that she is here to check with the [[Root Tappers]] to see what has happened to the convoy. At around 6am, it was decided who would lead our troop: it would be Ambassador Lyren.

At around 7.45am, we're north of the Dunes of Exile, near the Vortex leading north to the Forbidden Springs. We arrive at the camp of the Root Lords at around 11am. Thelotis Midix asks their leader, Diobus Apocaps, what has happened. Diobus says that a caravan has left - and that they're waiting for them to return and for payment (which she thinks is cheap, given the dangers). Azazor then makes a comment, which Diobus does not take kindly to. But that doesn't stop Diobus from asking us to go and look for them (from here to Dyron)... Thelotis Midix wants to go and question the local bandits - the Underspring Lyhnchers will be questioned very seriously. But Lyren prefers to finish with them, given his map.

Shortly before 4pm, we cross the lake towards the Cooky's Cranks camp.

After killing a pat and most of the bandits, Lyren and Azazor question their leader (with a few slaps), who claims not to have done anything, and accuses the bandits of being evil. He also says that they've been supplying Dyron for a long time, and that they don't want any fewer homins passing through here... Lyren believes him, while Azazor claims it's because these Trykers are too weak and small to attack this kind of convoy... Ashgan insists "if only it were a convoy of Byrh, at the very least...". However, Azazor delivers a diplomatic mandal to the tryker, who ends up giving (at random) the name of the Silencers.

We massacred another pat, and set off for the Silenciers camp - it was around 11pm...

2.20am, Quarta, Nivia 28, (4th CA 2630): we arrive near the Silencers' camp. An hour later, all the bandits are dead and we question their leader (the one who lets the others fight)... Brought to his knees by Lyren, he says that one of their scouts said he saw the convoy, far from here, to the north of the hole in the dead trees, but that they didn't attack it. Their leader, looking at Lyren, says he won't forget him...

So we set off north, for the Underspring lyncher camp. We arrived in the morning. Around midday, their leader called us barbarians, and a witness showed us where he'd seen homins emerging from the ground... We arrived near the OP at around 6pm.

We decide to take a rest and resume the investigation later.

=== Lucios ===
<gallery caption="Chapitres 1 to 4">
DeepFDiplo-2024-10-27-21h12-33-Wait.png|Waiting Kridix, (late)
DeepFDiplo-2024-10-27-21h17-11-Kridix.png|Thelotis Midix (of the chamber of justice) and Kridix (Fyros captain)
DeepFDiplo-2024-10-27-21h28-55-Lyren.png|Ambassador Lyren will lead us to the camp and head up Fyros diplomacy. D
DeepFDiplo-2024-10-27-21h33-40-VortexDune.png|At around 7.45am, we're north of the Dunes of Exile, near the Vortex.
DeepFDiplo-2024-10-27-21h35-38-SI.png|Arrival (and short break) in the [[Under Spring]]
DeepFDiplo-2024-10-27-21h44-50-Saig.png|In the camp of the [[Root Tappers]]
DeepFDiplo-2024-10-27-21h44-03-Camp.png|Thelotis talk to their chief, Diobus Apocaps
DeepFDiplo-2024-10-27-21h59-02-Cooky'sCranks.png|Arrival near the Cooky's Cranks camp (bandits)
DeepFDiplo-2024-10-27-21h59-51-KillCooCranks.png|Fyros diplomacy in practice: first you hit, then you talk
DeepFDiplo-2024-10-27-22-09-34-CooCranChief.png|their leader talks to us about Silenciers
DeepFDiplo-2024-10-27-22-15-45-HominCooCr.png|the homins present discuss their answers: they are too small to attack a water convoy - and, at the very least, if it was a beer convoy...
DeepFDiplo-2024-10-27-22h33-24-SilenciersChief.png|The leader of the Silenciers is then questioned
DeepFDiplo-2024-10-27-23h06-56-UnderspringLynchers.png|Underspring Lynchers camp: a witness will show us where he saw strange things
DeepFDiplo-2024-10-27-22h59-20-witness.png|un témoin va nous montrer là où il a vu des choses étranges
DeepFDiplo-2024-10-27-23h17-13-NearOP.png|Near the OP, we'll meet up later
</gallery>

<gallery caption="Chapitres 5 to 8">
DeepFDiplo-2024-10-28-21h25-20-Hole.png|Nous trouvons un trou (et sautons dedans)
DeepFDiplo-2024-10-28-21h29-Map.png|The "Hole" map
DeepFDiplo-2024-10-28-21h35-28-Issue.png|Arrêtez de taper des armas
DeepFDiplo-2024-10-28-21h36-Pat.png|Un nid de Kitin ou une énorme pat ?
DeepFDiplo-2024-10-28-21h45-11-FoundThem.png|Nous avons trouvé le convoi, tous morts !
DeepFDiplo-2024-10-28-21h45-BodyNoHead.png|Un corps trouvé, sans tête...
DeepFDiplo-2024-10-28-21h50-23-fyrak.png|Dans un étrange brouillard, Azazor accuse ces "ces foutus adorateurs du [[Grand Dragon]]"
DeepFDiplo-2024-10-28-21h53-38-dead.png|Tués par l'énorme [[pat]],
DeepFDiplo-2024-10-28-21h57-17-Rez.png|... on rez tous au Vortex nord des Sources Interdites
DeepFDiplo-2024-10-28-21h57-26-Hot.png|Chaud devant ! (attaque de tyrancha)
DeepFDiplo-2024-10-28-22h03-15-Blocks.png|La sortie est bouchée par d'énormes blocs
DeepFDiplo-2024-10-28-22h04-36-grouped.png|Comme toujours, on n'est pas très groupés...
DeepFDiplo-2024-10-28-22h11-15-OfloByrh.png|Rapport au camp, une plainte des brasseurs d'Oflovak :/
DeepFDiplo-2024-10-28-23h00-DyronEnd.png|Pour finir, un pot au bar de Dyron avec Kridix
</gallery>

== Notes and links ==
More on wikis:
* [[Root Tappers]]
* [[Pephoan Kridix]]
* [[Street show]]
and on the forum
* [https://app.ryzom.com/app_forum/index.php?page=topic/view/31530/1#1 The lost expedition]
* [https://app.ryzom.com/app_forum/index.php?page=topic/view/31877/1#1 Tracing the trail of his brethren in blood]

{{clear}}

<noinclude>
{{last version link|Deep Fyros diplomacy}}
{{Portal|Animation}}
[[Category:Events]]</noinclude>

Mektoub Racing

2024-07-26T12:55:33Z

Ledania:

<noinclude>{{Stub}}{{Trad
|DE=Mektoub-Rennen
|EN=Mektoub Racing
|ES=
|FR=
|RU=
|H=1
}}</noinclude>
Mektoub racing is where participants on [[mektoub mount]]s race each other from a starting point to a finishing point, the goal being to get to the finishing point first. These races can either be held officially by the events team or unofficially by players or guilds.

==Mini-Mek Racing==
A variation of normal mektoub racing hosted officially. It was first introduced during the 5th birthday celebrations of Ryzom. In this variation the racers ride atop miniature versions of the [[mektoub mount]].

==Rewards==
Depending on the host, there can be many rewards. Most commonly rewards include:
*[[Dappers]]
*Dug Materials
*[[Outpost_Produce#Catalysers|Cats]]
*Equipment (such as boosted focus jewels)

[[Category:Events]]

Yubo Plushie

2024-07-26T12:53:13Z

Ledania:

{{Trad
|DE=Yubo-Plüschtier
|EN=Yubo Plushie
|ES=Peluche Yubo
|FR=
|RU=
|H=1
}}

[[Image:Evilplushie.jpg|right|200px|I will feast on your soul.]]
Yubo plushies are inherently evil entities that seek to infiltrate the inventories of all homins and then devour their hosts from within.

They appear as cute and fluffy plushie versions of the [[Yubo]] to seem harmless, and many homins are fooled by this and actively seek to have a yubo plushie in their inventory. The picture on the right shows their true evil face.

Yubo plushies may sneak into your inventory if you win at the [[wheel of fortune|Wheel of Fortune]], or if you win at events like [[Mektoub Racing]].

===Stats===
As an inventory item, the yubo plushie is called "Teddy". They have 0 weight and 5 bulk and no other stats. They come in all qualities, and that changes absolutely nothing except the number on their icon.

They can be wielded in your right hand like a weapon or crafting tool, but give no bonuses or anything and you can't do anything with them. (Though you can still cast spells while wielding them, but that's no different from casting spells with a crafting tool equipped.)

They're purely to look cute!

[[Image:Cuteplushie.jpg|left|thumb|300px|But doesn't it look cute enough to be worth the risk?]]

[[Category:Mysteries]]

Yubo Plushie

2024-07-26T12:52:57Z

Ledania:

{{Trad
|DE=Yubo-Plüschtier
|EN=Yubo Plushie
|ES=Peluche Yubo
|FR=
|RU=
|h=1
}}

[[Image:Evilplushie.jpg|right|200px|I will feast on your soul.]]
Yubo plushies are inherently evil entities that seek to infiltrate the inventories of all homins and then devour their hosts from within.

They appear as cute and fluffy plushie versions of the [[Yubo]] to seem harmless, and many homins are fooled by this and actively seek to have a yubo plushie in their inventory. The picture on the right shows their true evil face.

Yubo plushies may sneak into your inventory if you win at the [[wheel of fortune|Wheel of Fortune]], or if you win at events like [[Mektoub Racing]].

===Stats===
As an inventory item, the yubo plushie is called "Teddy". They have 0 weight and 5 bulk and no other stats. They come in all qualities, and that changes absolutely nothing except the number on their icon.

They can be wielded in your right hand like a weapon or crafting tool, but give no bonuses or anything and you can't do anything with them. (Though you can still cast spells while wielding them, but that's no different from casting spells with a crafting tool equipped.)

They're purely to look cute!

[[Image:Cuteplushie.jpg|left|thumb|300px|But doesn't it look cute enough to be worth the risk?]]

[[Category:Mysteries]]

Marauders fame

2024-04-20T21:50:41Z

Ledania:

<noinclude>{{Trad
|DE=Marodeurs-Ruhm
|EN=Marauders fame
|ES=Fama de los merodeadores
|FR=Fame marauds
|RU=слава Мародерса
|palette=maraudeur
}}{{WIP}}</noinclude>

== [[Patch 00952]] ==
Since [[Patch 00952]] (June 2023) Marauders have a real fame.

* To up your marauder fame: take missions in marauder's camps.
** You then increase your marauder fame,
** without affecting the fames of [[tribes]] (the fames of [[:Category:Marauder Tribes|marauder tribes]] will not be affected)
** Of course, the fames of nations and other factions ([[Karavan]], [[Kami]], [[Ranger]]) may change.
* These [[mission]]s can be taken at any time.

* These marauding camps are indicated on your map (M), there is one in each country and are located in the following regions:
** [[Knoll of Dissent]] (KoD), in the Matis forest
** [[Maiden Grove]], in the Zorai jungle
** [[Resting Water]], and
** [[Sawdust Mines]] in desert. The camp is between TP Kami and Karavan.

== [[Patch 00847]] ==
With [[Patch 00847]] (Feb. 2021), there's a [[Marauders|marauder]] tribe, camps, and a big change in maraud's fame is changing.
[https://app.ryzom.com/app_forum/index.php?page=post/view/203399 See on the forum, Ulu's answer]:
:The famous marauder is particular. From -100 to 50 it is linked to other fames. The famous marauder is the opposite of the highest famous nation or faction.

:: Let's imagine that you have -20 in all fames and -10 in Tryker.
:: * The famous marauder is thus 10 (the highest of the non-marauder fames was the tryker at -10).
:: * Now making a mission of the camp, the famous Tryker goes down to -11. Automatically the famous marauder is adjusted and becomes 11.

:Once all the nation and faction fames are at minus 50, the famous marauder reaches 50. It is no longer possible to raise the famous marauder by lowering the nation/faction fames: it is necessary "at that moment" to carry out the missions of the [[Masters of the Goo]] who give the famous marauder.

* To the [https://app.ryzom.com/app_forum/index.php?page=topic/view/31385/203394#203394 official announcement of the patch on the forum] ; here is a summary, which concerns the marauders:
:* All other fames are now capped to -40 after a character has done the marauder rite;
:* A marauder can do missions from the Masters of the Goo tribe to increase the marauder fame above 50;
:* A teleport fx has been added to Marauders as for Kami/kara. To display the teleport fx, a marauder must have 100 in marauder fame
:* The xp catalysers have been replaced by sap recharges in Marauder Bosses loots
:* The Marauder camp in Nexus have now less aggressive creatures.
:* A maraudeur mini campment will be created in each continent. The first one, in Aeden Aqueous, is up with missions to lower the Tryker fame;
:* The zinuakeen of the region has been moved to the mini campment;
:* Addition of a third skin for outpost drills: the Marauder one, available to any guild whatever its Faction.

<noinclude>
{{Portal Gameplay}}
{{Portal|Marauders}}
[[Category:Game updates 2021|Fame]]
[[Category:Marauders|Fame]]
</noinclude>

Bugs

2023-06-27T04:00:09Z

Ledania:

<noinclude>{{Trad|DE=Bugs|EN=Bugs|ES=Bugs|FR=Bugs|RU=|palette=ryzom|H=1}}</noinclude>
[[Category:Forge]]

[[Portal:Forge|⬅️ Return to the Forge portal]]

===== [[Report a bug]] =====
''To learn how to create a ticket and report a bug''

===== [[Project BugsHunter]] =====
''To learn more about the project and how to join it''

Portal:Rangers/Language

2023-06-08T07:29:19Z

Ledania:

{{Tabs
|Tab-1={{3DText|group=ranger|text='''<big>Rangers</big>'''}}
|URL-1=Portal:Rangers
|bg_Tab-1=#{{ColorAtys|group=ranger|type=light}}

|Tab-2={{3DText|group=ranger|text='''History'''}}
|URL-2=Portal:Rangers/History
|bg_Tab-2=#{{ColorAtys|group=ranger|type=light}}

|Tab-3={{3DText|group=ranger|text='''Protagonists'''}}
|URL-3=Portal:Rangers/Protagonists
|bg_Tab-3=#{{ColorAtys|group=ranger|type=light}}

|Tab-4={{3DText|group=ranger|text='''Relations'''}}
|URL-4=Portal:Rangers/Relations
|bg_Tab-4=#{{ColorAtys|group=ranger|type=light}}

|Tab-5={{3DText|group=ranger|text='''Organization'''}}
|URL-5=Portal:Rangers/Organization
|bg_Tab-5=#{{ColorAtys|group=ranger|type=light}}

|Tab-6={{3DText|group=ranger|text='''Roleplay'''}}
|URL-6=Portal:Rangers/Roleplay
|bg_Tab-6=#{{ColorAtys|group=ranger|type=light}}

|Tab-7={{3DText|group=ranger|text='''Jargon'''}}
|URL-7=Portal:Rangers/Language
|bg_Tab-7=#{{ColorAtys|group=ranger|type=light}}

|bord=2px solid #{{ColorAtys|type=dark|group=ranger}}
|bg_frame=#{{ColorAtys|type=bg|group=ranger}}
|round=5em
|align_tab=center
}}{{Trad
|DE=Portal:Ranger/Sprache
|EN=Portal:Rangers/Language
|ES=Portal:Rangers/Lenguaje
|FR=Portail:Rangers/Langage
|RU=Портал:Рейнджеры/Язык
|palette=ranger
}}[[Image:Portail rangers princ.png|center]]

{{Portal bottom|ranger}}
__NOTOC__
__NOEDITSECTION__

[[Category:Portals]]

Prospector

2023-06-04T10:49:01Z

Ledania:

{{Stub}}<noinclude>{{Trad|DE=Prospektor|EN=Prospector|palette=atys|H=1}}</noinclude>

{{Quotation|''Unnamed Prospector''|
I'm the official prospector round here. I've never a moment to myself, always running round town, outpost and country collecting resources for the prosperity of my people. Up to my eyes in it, I am, and always on the lookout for any worthy homin to lend a hand to gather materials or to clear away the grounds of unwanted resources.
}}
Prospector are wandering mission givers. They give mostly foraging missions, and will pay dapper for their completion. Completing their missions will also give a small fame gain with the group the prospector belongs to, but not much, the dapper is the primary reward.

Prospectors can work for either one of the 4 civilisations, or for one of the local tribes. Whichever it is though, they require that you have at least positive fame with the group they belong to before they will give you missions.

Prospectors tend to have:
*7 cleaning missions
*7 foraging missions

Category:Biographies

2023-06-04T06:14:13Z

Ledania:

<noinclude>{{Trad
|DE=Kategorie:Biographie
|EN=Category:Biographies
|ES=Categoría:Biografías
|FR=Catégorie:Biographies
|RU=
|palette=atys
|H=1}}</noinclude>
The '''category'' Biographies''''' brings together the "long" biographies of players considered to be literary works.
[[Category:Player Characters]]
[[Category:Literature]]

Category:Biographies

2023-06-04T06:13:02Z

Ledania:

{{Trad
|DE=Kategorie:Biographie
|EN=Category:Biographies
|ES=Categoría:Biografías
|FR=Catégorie:Biographies
|RU=
}}The '''category'' Biographies''''' brings together the "long" biographies of players considered to be literary works.
[[Category:Player Characters]]
[[Category:Literature]]

Category:Biographies

2023-06-04T06:12:21Z

Ledania:

{{Trad
|DE=[[Kategorie:Biographie]]
|EN=[[:Category:Biographies]]
|ES=[[:Categoría:Biografías]]
|FR=[[:Catégorie:Biographies]]
|RU=
}}The '''category'' Biographies''''' brings together the "long" biographies of players considered to be literary works.
[[Category:Player Characters]]
[[Category:Literature]]

Testing Team

2022-03-22T22:18:56Z

Ledania:

{{Trad
|DE =Test-Team|DEs=4
|EN =Testing Team|ENs=0
|ES =Testing Team|ESs=5
|FR =Testing Team|FRs=2
|RU =Testing Team|RUs=5
|H =
|palette=Grey
}}
[[File:Ugly kipucka bug.png|400px|right]]
Test team is one of project teams that is focused on testing and re-testing current or new features of the game and related services. The team is being run by its members, mostly volunteers.
= Aim of the group =
It might look obvious by the team name, however don't be mislead. Our goal is to...
* provide systematic and complex testing for any other team, project or single developer
* discover and resolve all (possible) issues before a change is published
* track and research unresolved issues discovered internally or reported by players
* cooperate with developers, translators, lorists, designers...

= Who can join? =
Aim of our group may look that we seek mostly advanced users. Yes, being a member of another project team is welcome, however signing the NDA is not required. But, don't be mislead again. We are looking for you, in case you are...
* careful and responsible (because we care about tasks)
* prepared for hard work (because your work does not end by an issue discover)
* playing for some time (because testing will spoil your game experience)
* want to improve Ryzom

= How to join? =
We have a [[The Test Team Handbook|Testers handbook]] that can give you some answers. You will however, sooner or later, end up with contacting [[User:Tamarea|Tamarea]] who will grant you access to team tools and give you further information. In case you have joined the Test Team already, here is a [[New Tester's Checklist]] that summarize all you need to resolve before you really can start.

= Team members =
The team is using the system of roles. It means that, based on your abilities and will, you can occupy various roles in the team. This system tries to join abilities of all team members. Flags in front of each member name indicate preferred language in communication. More information about team roles is described in [[Test Team roles]] article.

== Coordinators ==
Members in this role care about all tasks management withing the team, prepare and evaluate all tests being done, update the Test board and make sure all issues were taken care of. Contact them if you are lost or need to request a testing. You do not need to be a member of any other team but you need to have experience with work of the Test team. Following members usually do the team management, in alphabetical order:
* 🇫🇷 [[User:Ashgan|Ashgan]]
* 🇬🇧 [[User:Moniq|Moniq]]
* 🇫🇷 [[User:Tamarea|Tamarea]]
* 🇫🇷 [[User:Ulukyn|Ulukyn]]

== Testers ==
The most important role in the Test team. You do not need to be member of any other team and you do not need previous experience with work of the team. It is the usual starting role for new volunteers. Following members do the core work, the testing, sorted in alphabetical order:
* 🇫🇷 [[User:Ashgan|Ashgan]]
* 🇬🇧 [[User:Beaujhangles|Beaujhangles]]
* 🇩🇪 [[User:Elke|Elke]]
* ⁇ [[User:Emiro|Emiro]]
* 🇩🇪 [[User:Lasabo|Lasabo]]
* 🇫🇷 [[User:Margote|Margote]]
* 🇬🇧 [[User:Moniq|Moniq]]
* ⁇ [[User:Nightviper|Nightviper]]
* 🇫🇷 [[User:Tuffgong|Tuffgong]]
* ⁇ [[User:Zarden|Zarden]]
* 🇫🇷 [[User:Steamox|Steamox]]

== Developers ==
[[Development_Team|Developers]] and [[ARK|content creators]] are important part of the Test team. We need to communicate with them and report about finished testing. You need to be a Ryzom / Ryzom Core / Ryzom project developer or a member of either the [[:Category:Animation Team|Animation or the Event team]]. Following alphabetically sorted list of members act in this role:
* 🇩🇪 [[User:SirCotare|Cotare]]
* ⁇ [[User:Daemonixus|Daemonixus]]
* ⁇ [[User:Fohdron|Fohdron]]
* ⁇ [[User:Ikarra|Ikarra]]
* ⁇ [[User:Jayvaraman|Jayvaraman]]
* ⁇ [[User:Nimetu|Nimetu]]
* 🇫🇷 [[User:PtitBill|PtitBill]]
* 🇩🇪 [[User:Riasan|Riasan]]
* 🇫🇷 [[User:SIELA1915|Siela]]
* 🇫🇷 [[User:Ulukyn|Ulukyn]]

== Translators ==
While the team concerns on all issues, we also need to cooperate with [[Translation|translators]]. Obviously, to act in this role, you need to be member of the Translation team. Members in the following alphabetically sorted list do use this role.
* 🇩🇪 [[User:Aileya|Aileya]]
* 🇩🇪 [[User:Elke|Elke]]
* 🇫🇷 [[User:Margote|Margote]]
* 🇪🇸 [[User:Zamoor|Zamoor]]

== Encyclopatysts and Marketing team ==
Another important members of the team are [[Ryzom_Wiki:About|encyclopatysts]] who work on team or end-user documentation and members of the [[:Category:Communication-Marketing_Team|Communication & Marketing team]] who need to review progress of changes and fixes. It requires you to join the Wiki project or become member of the Communication & Marketing team to act in this role. This is a list of members who are usually act in this role, alphabetically sorted:
* 🇬🇧 [[User:Moniq|Moniq]]
* 🇫🇷 [[User:Tamarea|Tamarea]]

== Artists, designers and lorists==
The team work is also to review and test all interfaces and look for possible troubles. This requires cooperation with an [[Computer_graphics|artist]], [[Level-Design|designers]] or [[:category:Lore Team|lorists]] You have to be member of such team to act in this role. Here is a list of members who act in this role most often, alphabetically sorted:
* 🇩🇪 [[User:Aileya|Aileya]]

<noinclude>
{{clear}}{{Last version link|Testing Team}}
{{Portal|Forge}}
[[Category:Test|Test team]] [[Category:Testing Team]] [[Category:Ryzom Team]] [[Category:Test]] [[Category:Tutorials]]</noinclude>

The Test Team Handbook

2022-03-22T09:39:01Z

Ledania:

{{Trad
|DE =Das Test-Team-Handbuch|DEs=4
|EN =The Test Team Handbook|ENs=0
|ES =The Test Team Handbook|ESs=5
|FR =Manuel de l'équipe de test|FRs=5
|RU =The Test Team Handbook|RUs=5
|H =
|palette=Grey
}}
This document gives you quick overview about necessary steps you must undertake to join the [[Test Team]] and be able to do good work. It is enriched with links to other documents with more details in case such text exists. If you have any questions or suggestions, feel free ask on [https://chat.ryzom.com/group/chat-general #chat-general] (accessible for team members only) or [https://chat.ryzom.com/channel/pub-general #pub-general] (open for everybody).

=Step 1: Apply to join=
If you are willing to apply to become a member of the Testing team, please contact Tamarea, directly on [https://chat.ryzom.com/direct/Tamarea Ryzom chat] or by sending an e-mail to [mailto:tamarea@ryzom.com tamarea@ryzom.com]. You need to get access to team tools and private chat rooms. After this step use the [https://chat.ryzom.com/group/t-test #t-test] chat room for any questions related to testing.

'''More information:''' [[The Test Team Handbook/1 - Get in touch with Ryzom Forge|Get in touch with Ryzom Forge]]

=Step 2: Get familiar with team tools=
As next you need to become familiar with tools used by the Ryzom team. For planning we use Kan Board, for collaboration we have a cloud system and internal (team) chat rooms.

'''More information:''' [[The Test Team Handbook/2 - External team tools|External team tools]]

=Step 3: Configure Ryzom clients=
The most of team work and testing is closely tight to our testing servers. You need to create two separated client installations to have access to Yubo, the developers server, Gingo, the testing server and also to beta updates for Atys server.

'''More information:''' [[The Test Team Handbook/3 - Setting up connection to non-public Ryzom servers|Setting up connection to non-public Ryzom servers]]

=Step 4: Prepare for testing=
Once you have access to testing servers, you need to prepare some characters to perform tests and become familiar with in-game tools for testers. It will make your life much easier.

'''More information:''' [[The Test Team Handbook/4 - On a testing server|On a testing server]]

=Step 5: Choose a test=
Your work in the Test team is mostly up to you. You are free to join any test and you can use any procedure that fits you. However there are some rules that help cooperation with others, prevents fails. You need to get familiar with our Test board where we track all existing testing tasks.

'''More information:''' [[The Test Team Handbook/5 - Test board organization|Test board organization]]

=Step 6: Start testing=
Now you are getting to the core. Your work would be pointless if you could not provide all details from your testing. There are some tips that can help you in case you have no previous experience with a testing.

'''More information:''' [[The Test Team Handbook/6 - Testing report tips|Testing report tips]]

{{Portal|Forge}}
[[Category:Test|Test team]]
[[Category:Tutorials|Test team]]
[[Category:Testing Team]]
[[Category:Ryzom Team]]
[[Category:Test]]
[[Category:Tutorials]]

Making evidence

2022-03-22T09:24:15Z

Ledania:

{{WIP}}
{{Trad
|DE =Das Test-Team-Handbuch/Beweise schaffen|DEs=3
|EN =Making evidence|ENs=0
|ES =The Test Team Handbook|ESs=5
|FR =The Test Team Handbook|FRs=5
|RU =The Test Team Handbook|RUs=5
|H =
|palette=Grey
}}

This document describes ways how to make evidence in form of screenshots or videos. It is mainly helpful and intended for members of the [[Test Team]] however it might be useful for for regular users as well, especially when they need to document game issues for a ticket or game forum post. The document is separated into three sections by client platform and, in case of video recording, is not meant as help with live streaming.

The Ryzom client itself contains feature to capture screenshots and this functionality is described in [[:Help:Screenshots|Screenshot help]] on this wiki.

=Windows=
Windows 10 has some support for needed features but in case of older version you will probably need to install 3rd part software.

==Screenshot==
The way how to take a screenshot of your desktop in most of recent versions of Windows is very easy. In case of older version it consists of two steps, first the screenshot will be copied into the clipboard, then you need to start an image editor and paste the content of the clipboard in. Most of procedures use the '''Print Screen''' (sometimes '''PrtScn''') key on your keyboard. It is located right to F12 key, above the Insert key.

[[File:Gamebar ui.png|thumb|150px|alt=Windows Game Bar interface|Windows Game Bar interface]]

===Build-in tools===
With Windows 8.1 and newer you have an easy way how to take a screenshot of your desktop, it will be automatically saved into '''Pictures''' folder in your home folder.
Press '''Win+Print Screen'''

The other way will work with Windows 98 or newer but might also work with Windows 95 (not tested). First copy the desktop screenshot into your clipboard:
Press '''Print Screen''' key
Then you need to open Microsoft Paint, a simple image editor that is default part of all Windows, and paste the content of your clipboard. You can however use any other bitmap image editor.
Execute '''mspaint''' command (or find application '''Paint''' / '''MS Paint''' in your '''Start Menu''')
Press '''Ctrl+V''' (or '''right-click''' in the drawing area and select '''Paste''')
Save the image into a file

===Windows Game Bar===
Microsoft Windows 10 has a build-in feature to capture screenshots of you application related to other gamer extensions. It however is not possible to capture the whole desktop and you need to start the application you want to capture first.
Press '''Win+Alt+Print Screen''' to take a screenshot
Press '''Win+G''' to display Game Bar and access options

===[https://en.wikipedia.org/wiki/Greenshot Greenshot]===
[[File:Greensgot settings.png|thumb|150px|alt=Greenshot screenshot tool preferences|Greenshot screenshot tool preferences]]
Another option is to use Greenshot, an open source screenshot tool for Windows. Install the application and start it, it will be hidden in the panel notification area along with other icons. This will work with any Windows version that is supported by this software.
Press '''Ctrl''' + '''Print Screen''' to capture whole desktop, then save it to a file

===[https://en.wikipedia.org/wiki/GIMP The GIMP]===
GNU Image Manipulation Program, a powerful tool to edit bitmap images in various formats. It also have an interface to capture desktop screenshots.
Choose '''File''' > '''Create''' > '''Screenshot''' from the main menu

==Video recording==
Latest Microsoft Windows 10 includes support for video recording. In case you are using any older version, you will probably need to use 3rd party software to do the job.

===Windows Game Bar===
Microsoft Windows 10 has a build-in feature to record video of you application related to other gamer extensions. It however is not possible to record the whole desktop and you need to start the application you want to record first.
Press '''Win+Alt+R''' to start or stop video recording
Press '''Win+G''' to display Game Bar and access recording options

===[https://en.wikipedia.org/wiki/VLC_media_player VLC media player]===
[[File:Vlc capture.png|thumb|150px|alt=VLC capture device settings|VLC capture device settings]]
VLC is open-source multimedia player and stream server application that can, along with many other functions, also record your desktop. This recording should work with every version of Windows in case you are able to install and run VLC, however it requires you to perform several steps:
1. Select '''Media''' > '''Convert/Save''' (or press '''Ctrl+R''')
2. Switch to '''Capture Device''' tab
3. Select '''Desktop''' from '''Capture mode''' drop down menu
4. Set '''Desired frame rate for the capture''' using the spin box to at least '''15''' f/s
5. Click '''Convert/Save''' button
6. Select '''Profile''' from the drop-down menu (or click preferences button to adjust video output)
7. Select '''Destination file''' clicking on '''Browse''' button
8. Click '''Start''' button to start recording
9. To stop recording click standard '''⏹''' (stop) button as if you stop video/audio playback

==Other tools==
[[File:Carnac preferences preview.png|thumb|150px|alt=Carnac preferences and preview|Carnac preferences and preview]]
There exist some additional tools and utilities that might help to make evidence for your (testing) report.

=== [http://carnackeys.com/ Carnac] ===
In some special cases it might be needed to also record keys that you press on your keyboard. You can use the this utility in combination with desktop video recording. It requires Windows 7 or newer and [https://www.microsoft.com/en-au/download/details.aspx?id=42643 Microsoft .NET Framework 4.5.2]

=Linux=
[[File:Screenshot capture.png|thumb|150px|alt=Linux screenshot capture interface|Linux screenshot capture interface]]
Most of end-user desktop Linux distributions come with various tools that can do the job. Some of them are already part of your desktop environment, other can be installed from your distribution package repository. It is not aim of this document to describe all existing utilities.

==Screenshot==
Most of Linux graphical environments have built-in a way how to capture desktop screenshots already. It is usually accessible by pressing the '''Print Screen''' (sometimes '''PrtScn''') key on your keyboard. It is located right to '''F12''' key, above the '''Insert''' key. In case that your environment does not support this feature, you can use one of many alternatives.

===Build-in tools===
Taking screenshot by pressing '''Print Screen''' will work in case you are using [https://en.wikipedia.org/wiki/Cinnamon_(desktop_environment) Cinnamon], [https://en.wikipedia.org/wiki/GNOME Gnome], [https://en.wikipedia.org/wiki/KDE_Plasma_5 KDE Plasma 5], [https://en.wikipedia.org/wiki/MATE_(software) MATE] or [https://en.wikipedia.org/wiki/Xfce Xfce] desktop. Please consult help (accessible usually by pressing '''F1''' key) for advanced options specific for your desktop environment. These are usually accessible by starting the application alone from menu or as an argument on the command line.
Press '''Print Screen''' key to take a screenshot

===[https://en.wikipedia.org/wiki/GIMP The GIMP]===
[[File:Gimp screenshot ui.png|thumb|150px|alt=GIMP interface to take screenshot|GIMP interface to take screenshot]]
GNU Image Manipulation Program, a powerful tool to edit images in various formats. It also have an interface to capture desktop screenshots.
Choose '''File''' > '''Create''' > '''Screenshot''' from the main menu

===[https://en.wikipedia.org/wiki/ImageMagick ImageMagick]===
A set of command line driven utilities for image manipulation. Consult the manual page page for more options.
Execute '''import -window root ~/file_name.png''' command to take screenshot of your desktop and save it to your home directory.

==Video recording==
[[File:Simplescreenrecorder.png|thumb|150px|alt=SimpleScreenRecorder window with input settings|SimpleScreenRecorder window with input settings]]
It might be important to record your activity in the game. It can help you to show a problem or describe a client behaviour to others. There exist various ways how to do this.

===[https://en.wikipedia.org/wiki/SimpleScreenRecorder SimpleScreenRecorder]===
It is a small but powerful tool to record a video of your desktop environment. It is a Qt-based free (libre) software that allows you to specify shortcut to start and stop recording and set many other options. As first you need to configure the utility and then it can wait in the notification area until you need it.
1. Press '''Continue''' button on first window
2. Set video and audio input options and click '''Continue''' (optionally create a profile)
3. Select output file manually or by clicking on '''Browse...''' button
4. Check '''Separate file per segment''' (every video sequence will be save in a separated file)
5. Set video and audio output options and click '''Continue''' (optionally create a profile)
6. Set '''Hotkey''' combination to start/stop recording
7. Click SimpleScreenRecorder icon in notification area to hide main window
Now the tool is configured and you can start and stop recording any time you need.
Press selected shortcut (hotkey) to start/stop recording, '''Ctrl+R''' by default

===byzanz===
Another option is to use '''byzanz''', a command line utility that will record your desktop as an animated GIF (Graphics Interchange Format) image. Please note that, by default, the record will suffer the format limitations with small colour palette because True color using separated image blocks is not supported. Please consult the manual page for more options and output formats.
Execute '''byzanz-record ~/file_name.gif''' to record your desktop and save it to your home directory.

=== OBS ===
For linux (but windows, macOS 10 too) OBS is a good solution too https://obsproject.com

==Other tools==
[[File:Screenkey preferences preview.png|thumb|150px|alt=Screenkey preferences and preview|Screenkey preferences and preview]]
There exist some additional tools and utilities that might help to make evidence for your (testing) report.

=== [https://www.thregr.org/~wavexx/software/screenkey/ Screenkey] ===
In some special cases it might be needed to also record keys that you press on your keyboard. You can use the this utility in combination with desktop video recording.

=macOS=
Apple macOS is very friendly to all multimedia and you will have several ways to make evidence with tools shipped with the system.

'''Note:''' Following information were not tested and are based on public Apple macOS documentation. In case you are using this system, please [[Help#Help_on_wiki|help]] with this document.

==Screenshot==
By default, macOS comes with several applications to take screenshots of your desktop.

===[https://support.apple.com/en-us/HT201361 Screenshot app]===
The easiest way how to take a screenshot of your current desktop and let it be saved on your desktop is
Press '''Shift + Command ⌘ + 3''' and wait a moment before it is saved on your desktop

===[https://en.wikipedia.org/wiki/Grab_(software) Grab]===
Grab is another application that you can use to take screenshots of your desktop. You can find it in '''Applications''' > '''Utilities''' > '''Grab'''. When you see Grab menu...
Select '''Capture''' > '''Screen''' (or press '''Shift + Command ⌘ + W''')
Click somewhere out of the dialog window

==Video recording==
Same as in case of screenshots, macOS comes with several ways how to record your desktop.

===Mojave and newer===
With macOS Mojave or newer there is a very easy way how to record your desktop or its part.
Press '''Shift + Command ⌘ + 5''' to see bar with all possible options
Select appropriate button and click on a screen to start recording (or click '''Record''' button on the bar)

===[https://en.wikipedia.org/wiki/QuickTime QuickTime Player]===
You can use the QuickTime Player on macOS systems older than Mojave.
Select '''File''' > '''New Screen Recording'''
Click the red button in the middle of the window
Click anywhere on the screen to start recording
Click black stop button in notification area of the menu bar to stop recording (or press '''Command ⌘ + Ctrl + Esc''')

{{Portal|Forge}}
[[Category:Test|Test team]]
[[Category:Tutorials|Test team]]
[[Category:Testing Team]]
[[Category:Ryzom Team]]
[[Category:Test]]
[[Category:Tutorials]]

The Test Team Handbook/6 - Testing report tips

2022-03-22T08:59:51Z

Ledania:

<noinclude>{{Trad|DE=Das Test-Team-Handbuch/6 - Tipps für den Testbericht|EN=The Test Team Handbook/6 - Testing report tips|H=1}}</noinclude>
This document is a collection of tips that are very important for every testing report. Each topic is important and has a reason. It is not possible to write a document that will teach to to be a good tester or that cover all situations that can occur. These are some highlighted important points, however your personal effort and will is the second and not less important part of your work.

=Report into latest PAD=
As a tester, do all your reports into the latest [[File_formats#The_.pads|Testing PAD]] related to a task you are working on. In case the task includes more than one PAD link, always use the latest. There exists a [https://cloud.ryzom.com/f/36218 self-explaining PAD example] as well as a [https://cloud.ryzom.com/f/36039 PAD with some basic help] about PAD organization. The actual form of each Testing PAD is fully up to the current Test guide (a coordinator who manages the current test) however all PADs will be similar because of need to track similar information.

In case that the task has no PAD but the testing is open (very rare situation), do your report directly into the task comments.

=Provide testing environment details=
This is the most important and essential information you provide. Your current character name that was used for testing is not that important and might be useful only in case when a developer needs to review database details related to it. Much more important is to let us know:
* '''Tester name''' - the name that you are using in the Test Team. Not all might be clear from your report and a coordinator might need to talk about details with you.
* '''Platform''' - your operating system name and version including information if it is 32 or 64 bit. Some issues might be platform specific for various reasons.
* '''Language''' - your Ryzom client locales you have used during your testing. Some issues might be language specific for various reasons.
Besides these there might be some specific information needed for a specific testing (for example desktop screen resolution). All these information are usually stored in '''Testers''' section of the PAD. In case that you use various combinations remember to list them all and mention if any discovered issue applies to all or just some of those combinations.

=Read instructions carefully=
Every testing PAD usually has a section with general '''Description'''. You will find there some details about the change you are testing and, optionally, details about known issues, fixed issues, possible rewards, general mechanics of the change or debug/tester tools related to your testing.

Another very important section is '''Instructions''' where you will find more detailed information about which character you need to prepare for the testing, optionally with tips how to do it, and usually a list of things that we need to test. Your work should however not stop here.

=Provide date and time of your testing=
All your reports, questions and feedback go to '''Reports''' section. Always start new report with date and time when the testing was performed, including time zone. This is important for several reasons:
* Actively developed things might change in time and we might need to know if your report was done before a specific change or after
* Server might have technical difficulties by the time of your report and some discovered issues might not be directly related to the task

=Ask if you are lost=
No one knows everything. In case you do not understand the matter of a change, feature mechanics is not clear or in case you have discovered a behaviour that is not covered by the PAD instructions, ask. Every task has a developer mentioned in the PAD and also as a tag sticker on the task. Every opened test has also a Test guide, a coordinator who takes care of the current test. Ask them for details. We all work to make Ryzom better so you should not hesitate to also ask directly on the [https://chat.ryzom.com/group/t-test #t-test] channel.

=Report everything=
Yes, you should reflect all topics in Instructions, but it is also important if you can provide all possible related details you can. Your report should describe what and how you did perform the test and all related circumstances. Describe your activity, especially in case you discover an issue. Be ready to take and provide screenshots along with your report or record a video that captures whole situation. Read [[Making evidence]] article for help with how to do that.

Your report should also be partially a feedback for the Developer or the Test guide and do not hesitate to suggest better solutions for certain situations. Think the player way:
* Think about what players will experience with the feature
* Think about troubles they might have using the feature alone and in combination with other game mechanics
* Keep in mind that players might have limitations (language barriers, colour blindness, disablement...)
* Keep in mind that players might not be as experienced as you are

=Keep eye on your work=
Your work do not end with nice shiny report full of images. Come back in few days and review if your report was reviewed and all issues noted in '''Issues''' section. Ask coordinators and developers about progress. Repeat your questions in case you did not get any answer, either in the PAD or in the chat.

Do not be lazy to prepare new character and repeat your testing. Within one report (testing session) to examine and fully describe discovered issues, but also after a progress. Come back and re-test everything, provide new report reflecting latest changes. Confirm issues discovered by others, confirm issue fixes. You have the intelligence, experience and creativity. That is why we need you. Otherwise a machine could do your work.

=Break testing servers but be discreet on Atys=
When testing on Yubo on Gingo, always look for ways how to break or exploit things. Do not hesitate to do. Better break a testing server then let players to do with Atys. And don't be naive to think players will not try. Play stupid, look for ways how to use things the unexpected way. Combine things even when it looks pointless. Damage feature configuration file. Misuse the user interface. Does it ask for number? Input string. Does it expect you to click a link or button? Reload the window few times. Break it.

Absolutely different situation is when testing on Atys. Do your testing but always mind regular players who came to enjoy the game. In case you have suspicions that something might affect others...
* Do a similar test on Gingo first
* Consult it with developers as next
You should always be inconspicuous and you should definitely avoid doing following things:
* Do not spoil details to pubic, let players have fun and discover things themselves
* Do not bother other players, let them enjoy game features and do not, for example, occupy place/game
* Do not use exploits for other reasons then re-testing (or you will get ban)

{{Portal|Forge}}
[[Category:Test|Test team]]
[[Category:Tutorials|Test team]]
[[Category:Testing Team]]
[[Category:Ryzom Team]]
[[Category:Test]]
[[Category:Tutorials]]

The Test Team Handbook/4 - On a testing server

2022-03-22T08:55:23Z

Ledania:

<noinclude>{{Trad
|DE=Das Test-Team-Handbuch/4 - Auf einem Testserver |DEs=4
|EN=The Test Team Handbook/4 - On a testing server |ENs=0
}}</noinclude>
This document attempt to cover your first steps on one of Ryzom testing servers, with focus on testers. It is expected that you already have access to testing servers and you have successfully configured your clients to be actually able to connect. Consult the [[New Tester's Checklist]] to make sure you didn't forget anything. Following information applies to both testing servers, it is not important if you are on Yubo or Gingo.

==Account characters==
When you log to a testing server for the very first time, all your account slots are empty. It is recommended to create just one or two universal characters that will be always ready and leave other slots empty. Most of testing requires you to have none or just some specific skills and in most cases it is faster to simply create new character on your empty slot (or replace previous) for a test then develop a tool to reset your character or even wait for cool-downs.

When you creating your testing characters, avoid using any real Atys character name. Testing and real accounts are separated however it might bring troubles in the future when for example a character debug is be needed. It also prevents you from confusing which server are you on and which character owns what. Same names requires everyone to pay more attention and you won't to delete your character on wrong server by accident. Your character race or gender is not any important.

==First time on server==
Once you are done with creating your avatar and standing on Silan face to Chiang the Strong, it is time to give your new character some skills. The world of a testing server is, more or less, same as Atys you know. To grind necessary levels is however not needed thanks to various tools you are able to use.

Server accounts have a system of privileges. You will be able to use most of normal testing tools, however some specific applications or commands might require higher privileges than you have. In this case ask on your team/project channel (or on the [https://chat.ryzom.com/group/chat-general #chat-general] channel) so someone else with higher privileges can help you. Following text will tell you how you can adjust various aspects of your character and some basics of your life on a testing server but is not meant to be a manual for tools that you will use.

==In-game tools==
[[File:Appzone beta testing.png|thumb|alt=Beta Testing section of App Zone|Beta Testing section of App Zone]]
First of all we need to make clear which tools will we use. At this moment we have several, more or less, separated applications. Please remember that this part of Ryzom expands widely and may change during the time. In case you have any troubles using it, you find an issue or you want to suggest an improvement contact the specific tool creator please.

===[[File:TT icon command toolbar.png|18px|alt="Command toolbar icon"|left]]Command Toolbar===
[[File:Command toolbar.png|thumb|alt=Command toolbar interface|Command toolbar interface]]
It is a toolbar with various links to other testing and administrative interfaces. By default it is placed on your screen somewhere, unless you made it disappear.
* '''Start:'''
** Execute '''/cmdzone show'''
** Press '''Shift+W''' and start '''Command Toolbar''' application from '''Beta Testing''' section.
* '''Creator:''' [[User:Riasan|Riasan]]
{{clear}}

===[[File:Mp buterfly blue.png|18px|alt="Inky's Tool"|left]]Inky's tool===
[[File:Inkys tool.png|thumb|alt=Inky's tool|Inky's tool]]
This is a compact interface that contains some basic functions mostly related to character allegiance. The tool has a shortcut on the Command Toolbar. Use it to get teleportation related items or zig spawned.
* '''Start:'''
** Execute '''/appzone 2449'''
** Run its shortcut from Command Tollbar (position '''6''')
** Press '''Shift+W''' and start '''Inky's Tool''' application from '''Beta Testing''' section.
* '''Creator:''' [[User:Inky|Inky]]
'''Note:''' Tool creator do not provide any further support nor participate on the project.
{{clear}}

===[[File:Mp batiment noyau maduk.png|18px|alt="Teleport interface"|left]]Teleport interface===
[[File:Teleport interface.png|thumb|alt=Teleport interface|Teleport interface]]
This application is used to quick and free teleportation around the planet. It allows you to use one of fix positions for everyone, use short range landscape teleportation or save and share your own positions. The interface has a shortcut on the Command Toolbar.
* '''Start:'''
** Execute '''/appzone 1356'''
** Run its shortcut from Command Tollbar (position '''8''')
** Press '''Shift+W''' and start '''Teleport interface''' application from '''Beta Testing''' section.
* '''Creator:''' [[User:Riasan|Riasan]]
'''Note:''' Every time you use the teleport interface to move, a command with your current position overwrites your clipboard content.
{{clear}}

==GM island==
This is a secret area in the forest region. Its position is in the Fix list of the Teleport interface and has a link in the Inky's tool. You can find there several additional objects you can interact with. You can contact Riasan about all GM island related tools.

[[File:Gm island red box.png|100px|right|alt=Red Box|Red Box]]
====Red Box====
This object is used to access to various additional tools, items or interfaces and its options change in time by what is needed.

[[File:Gm island pumpkin.png|100px|right|alt=Debug Pumpkin|Debug Pumpkin]]
====Debug Pumpkin====
This pumpking was introduced during development of the Ranger rite and gives you access to various related options like setting allegiance, rite state, reset and so.

[[File:Gm island npc.png|100px|right|alt=NPC on GM island|NPC on GM island]]
====Cult giver NPC====
There are also two NPC who can change you civilization and faction allegiance. However we have more advanced tools now accessible from the Command Toolbar or with Inky's tool.

==Help yourself==
Now it is time to really grow your character. Following list will help you to satisfy all your basic needs:
* To '''get money''', you can use '''Money interface''' from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''1''') or the feature on [[The_Test_Team_Handbook/4_-_On_a_testing_server#Inky.27s_tool|Inky's tool]] with icon of dappers.
* To '''spawn various or special items''' you can use the '''Spawn interface''' from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''11''') or various buttons on [[The_Test_Team_Handbook/4_-_On_a_testing_server##Inky.27s_tool|Inky's tool]] (to get generic raw materials, teleport pacts and artifacts or a pet).
* To '''find a specific item sheet ID''' you can use '''All sheet list items''' interface from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''12''')
* To '''find a specific creature sheet ID''' you can use '''All sheet list creature''' interface from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''2''')
* To '''rise your skill levels''' and (optionally) learn all action bricks you can use the '''Boost''' interface from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''4)
* To '''set your allegiance''' you can use the '''Fame tool''' interface from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''13''', allows you to set allegiance and fame) or options on [[The_Test_Team_Handbook/4_-_On_a_testing_server#Inky.27s_tool|Inky's tool]] (will set your allegiance and adjust your fame automatically) or [[The_Test_Team_Handbook/4_-_On_a_testing_server#Cult_giver_NPC|Cult giver NPC]] on the GM island.
** The [[The_Test_Team_Handbook/4_-_On_a_testing_server#Red_Box|Red Box]] on GM island allows you to set your Marauder rite as done, Inky's tool will give you a Marauder teleportation crystal
** The [[The_Test_Team_Handbook/4_-_On_a_testing_server#Debug_Pumpkin|Debug Pumpkin]] on the GM island allows you to set yourself a Ranger aspirant or a Ranger with various additional options, Inky's tool can spawn you the Ranger Map
* To '''set your fame''' you can use the '''Fame tool''' interface from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''13''')
* To '''quick heal''' your life, sap, stamina or focus you can use the '''State tool''' from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''3'''). This way you can also resurrect yourself.
* To '''travel''', besides running, you can use the '''Teleportation interface''' from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''8''') or spawn yourself teleportation related items using [[The_Test_Team_Handbook/4_-_On_a_testing_server#Inky.27s_tool|Inky's tool]].
** To learn more about current position and the area you can use '''Show Position''' tool from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''18''')
* To '''toggle camera''' between fly and inside your avatar body, use '''Free Camera toggle''' from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''9''')
* To '''start a mission''' by its ID you can use '''Mission helper''' from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''16''')

==Game mastering==
Sooner or later, how you tester skills will develop, you will face the need of use more powerful tools. The power comes from using commands, knowledge of the system and account privileges. Each server has separated user rights.

===Server privileges===
User accounts on each server might have various privileges. The following list contains all server ranks, sorted from lowest (Tester) to highest (DEV). Regular player accounts are never able apply for any privileges.
* ''Inactive accounts''
* ''Free to play player (F2P)''
* ''Subscribed player (P2P)''
* Tester
* Event Guide (EG)
* Event Manager (EM)
* Senior Event Manager (SEM)
* Guide (G)
* Senior Guide (SG)
* Veteran Guide (VG)
* Game master (GM)
* Senior Game Master (SGM)
* Developer (DEV)
'''Note:''' Understand the list as to be simplified representation of server hierarchy, not to exactly describe server privileges

===Useful information and tools===
There are some external documents and 3rd party tool links that may be helpful or help you with understanding and use of advanced abilities.

====[https://ryzomcore.atlassian.net/wiki/spaces/RC/pages/19365937/Shard+Commands Shard Commands]====
A list of commands that can be used on running server, including privileges. Created by Ryzom Core project. There is another similar [https://raw.githubusercontent.com/osgcc/ryzom/master/ryzom/server/data_shard/client_commands_privileges.txt List of required privileges for client commands]

====[https://ryzomcore.atlassian.net/wiki/spaces/RC/pages/884873/Ryzom+Service+Architecture Ryzom Service Architecture]====
A Ryzom Core document with that lists and shortly describes all Ryzom server services.

====[[Skill_Tree/Skill_decoding|Skill decoding]]====
A post that explains how are skill keys composed, based on first name's letter.

====[https://api.ryzom.com/ Ryzom API documentation]====
API server with documentation related to public Ryzom APIs.

====[https://ryzomcore.atlassian.net/wiki/spaces/RC/pages/11763715/Ingame+browser In-game browser]====
A simple introduction into capabilities and use of the in-game browser, created by Ryzom Core project. It is also good to follow [https://app.ryzom.com/app_forum/index.php?page=topic/view/24138/ Ingame browser capabilities] thread on Ryzom Forum.

====[https://maps.bmsite.net/sample/builder.html Ballistic Mystix map builder]====
A tool to review and export maps of Atys...

====[https://ofancytext.firebaseapp.com/ Ryzom message coloring tool]====
A simple external tool to generate colour codes for coloring in-game messages (MOTD, crafter's message...)

====[https://atys.wiki.ryzom.com/RyzomNameGenerator/ Ryzom name generator]====
A tool to generate random names suitable for Ryzom. There exists also small [https://app.ryzom.com/app_name_gernerator_api/?race=fyros&gender=male Name generator script] that returns a random name by given parameters via URL

====[http://ryzom.aeness.net/ryzom_word/ Items list]====
Besides build-in sheet browser, which is a part of the Spawn tool as well as Command Toolbar, you can also use external lists of item sheets and names. Another option is to use [http://beta.kdyne.net/rygreg/DEVEL/bagapp/?sekce=itemdb-search search for items] in BagApp database or extract files directly from your client.

====[http://beta.kdyne.net/rygreg/DEVEL/langapp/bbtor.php Blablator API]====
A small LangApp API to provide translations with data based on original [[User:Osquallo|Osquallo]]'s Blablator.

{{Portal|Forge}}
[[Category:Test|Test team]]
[[Category:Tutorials|Test team]]
[[Category:Testing Team]]
[[Category:Ryzom Team]]
[[Category:Test]]
[[Category:Tutorials]]

Skill Tree/Skill decoding

2022-03-22T08:41:18Z

Ledania:

<noinclude>{{WIP}}{{Trad|DE=Fertigkeits-Baum/Fertigkeiten dekodieren|EN=Skill Tree/Skill decoding|H=1}}</noinclude>
Skills in Ryzom are internally coded by first letter of a branch. The following list will help you understand and decode those codes:

=Examples=
'''sfm2ssm''' = skill fight melee two handed slashing sword master

'''scahbem''' = skill craft armour heavy boots expert master

= Skill tree codes =
s = skill
* '''c = craft'''
** a = armour
*** h = heavy
*** l = light
*** m = medium
**** b = boots
***** e = expert
****** m = master
**** g = gloves
***** e = expert
****** m = master
**** h = helmet
***** e = expert
****** m = master
**** p = pants
***** e = expert
****** m = master
**** s = sleeves
***** e = expert
****** m = master
**** v = vest
***** e = excellent
****** m = master
** s = shields
*** b = buckler
***** e = expert
****** m = master
*** s = large shield
***** e = expert
****** m = master
** j = jewels
*** a = anklet
***** e = expert
****** m = master
*** b = bracelet
***** e = expert
****** m = master
*** d = diadem
***** e = expert
****** m = master
*** e = earring
***** e = expert
****** m = master
*** p = pendant
***** e = expert
****** m = master
*** r = ring
***** e = expert
****** m = master
** m = melee
*** 1 = one handed
**** a = axe
***** e = expert
****** m = master
**** d = dagger
***** e = expert
****** m = master
**** m = mace
***** e = expert
****** m = master
**** p = spear
***** e = expert
****** m = master
**** s = sword
***** e = expert
****** m = master
**** t = staff
***** e = expert
****** m = master
*** 2 = two handed
**** a = axe
***** e = expert
****** m = master
**** m = mace
***** e = expert
****** m = master
**** p = pike
***** e = expert
****** m = master
**** s = sword
***** e = expert
****** m = master
*** c = close combat
**** a = amps
***** e = expert
****** m = master
** r = ranged
*** 1 = one handed
**** p = pistol
***** e = expert
****** m = master
*** 2 = two handed
**** a = autolauncher
***** e = expert
****** m = master
**** l = launcher
***** e = expert
****** m = master
**** r = rifle
***** e = expert
****** m = master

* '''f = fight'''
** m = melee
*** 1 = one handed
**** b = smashing
***** m = mace
****** m = master
***** s = staff
****** m = master
**** p = piercing
***** s = spear
****** m = master
**** s = slashing
***** a = axe
****** m = master
***** s = sword
****** m = master
*** 2 = two handed
**** b = smashing
***** m = mace
****** m = master
**** p = piercing
***** p = pike
****** m = master
**** s = slashing
***** a = axe
****** m = master
***** s = sword
****** m = master
*** c = close combat
**** a = advanced
***** d = dagger
****** m = master
***** h = hand to hand
****** m = master
** r = ranged
*** 1 = one handed
**** a = advanced
***** p = pistol
****** m = master
*** 2 = two handed
**** a = advanced
***** a = autolauncher
****** m = master
***** l = launcher
****** m = master
***** r = rifle
****** m = master

* '''h = harvest'''
** f = forage
*** d = desert
**** a = advanced
***** e = expert
****** m = master
*** f = forest
**** a = advanced
***** e = expert
****** m = master
*** j = jungle
**** a = advanced
***** e = expert
****** m = master
*** l = lake
**** a = advanced
***** e = expert
****** m = master
*** p = prime roots
**** a = advanced
***** e = expert
****** m = master

* '''m = magic'''
** d = defensive
*** a = affliction
**** a = advanced
***** e = expert
****** m = master
**** h = healing
***** a = advanced
****** e = expert
******** m = master
** o = offensive
*** a = affliction
**** a = advanced
***** e = expert
****** m = master
*** e = elemental
**** a = advanced
***** e = expert
****** m = master

Skill Tree

2022-03-22T08:36:04Z

Ledania:

{{Stub}}
<noinclude>{{Trad|DE=Fertigkeits-Baum|EN=Skill Tree|FR=Arbre de Compétences|H=1}}</noinclude>
<ArmoryAPI page="skilltree" lang="en" />

See https://ballisticmystix.net/?p=skilltree

[[Category:Skills]]

[[de:Fertigkeits-Baum]]
[[fr:Arbre de Compétences]]

Skill Tree/Skill decoding

2022-03-22T08:24:53Z

Ledania:

<noinclude>{{WIP}}{{Trad|DE=Skill Tree/Skill dekodieren|EN=Skill Tree/Skill decoding|H=1}}</noinclude>
Skills in Ryzom are internally coded by first letter of a branch. The following list will help you understand and decode those codes:

=Examples=
'''sfm2ssm''' = skill fight melee two handed slashing sword master

'''scahbem''' = skill craft armour heavy boots expert master

= Skill tree codes =
s = skill
* '''c = craft'''
** a = armour
*** h = heavy
*** l = light
*** m = medium
**** b = boots
***** e = expert
****** m = master
**** g = gloves
***** e = expert
****** m = master
**** h = helmet
***** e = expert
****** m = master
**** p = pants
***** e = expert
****** m = master
**** s = sleeves
***** e = expert
****** m = master
**** v = vest
***** e = excellent
****** m = master
** s = shields
*** b = buckler
***** e = expert
****** m = master
*** s = large shield
***** e = expert
****** m = master
** j = jewels
*** a = anklet
***** e = expert
****** m = master
*** b = bracelet
***** e = expert
****** m = master
*** d = diadem
***** e = expert
****** m = master
*** e = earring
***** e = expert
****** m = master
*** p = pendant
***** e = expert
****** m = master
*** r = ring
***** e = expert
****** m = master
** m = melee
*** 1 = one handed
**** a = axe
***** e = expert
****** m = master
**** d = dagger
***** e = expert
****** m = master
**** m = mace
***** e = expert
****** m = master
**** p = spear
***** e = expert
****** m = master
**** s = sword
***** e = expert
****** m = master
**** t = staff
***** e = expert
****** m = master
*** 2 = two handed
**** a = axe
***** e = expert
****** m = master
**** m = mace
***** e = expert
****** m = master
**** p = pike
***** e = expert
****** m = master
**** s = sword
***** e = expert
****** m = master
*** c = close combat
**** a = amps
***** e = expert
****** m = master
** r = ranged
*** 1 = one handed
**** p = pistol
***** e = expert
****** m = master
*** 2 = two handed
**** a = autolauncher
***** e = expert
****** m = master
**** l = launcher
***** e = expert
****** m = master
**** r = rifle
***** e = expert
****** m = master

* '''f = fight'''
** m = melee
*** 1 = one handed
**** b = smashing
***** m = mace
****** m = master
***** s = staff
****** m = master
**** p = piercing
***** s = spear
****** m = master
**** s = slashing
***** a = axe
****** m = master
***** s = sword
****** m = master
*** 2 = two handed
**** b = smashing
***** m = mace
****** m = master
**** p = piercing
***** p = pike
****** m = master
**** s = slashing
***** a = axe
****** m = master
***** s = sword
****** m = master
*** c = close combat
**** a = advanced
***** d = dagger
****** m = master
***** h = hand to hand
****** m = master
** r = ranged
*** 1 = one handed
**** a = advanced
***** p = pistol
****** m = master
*** 2 = two handed
**** a = advanced
***** a = autolauncher
****** m = master
***** l = launcher
****** m = master
***** r = rifle
****** m = master

* '''h = harvest'''
** f = forage
*** d = desert
**** a = advanced
***** e = expert
****** m = master
*** f = forest
**** a = advanced
***** e = expert
****** m = master
*** j = jungle
**** a = advanced
***** e = expert
****** m = master
*** l = lake
**** a = advanced
***** e = expert
****** m = master
*** p = prime roots
**** a = advanced
***** e = expert
****** m = master

* '''m = magic'''
** d = defensive
*** a = affliction
**** a = advanced
***** e = expert
****** m = master
**** h = healing
***** a = advanced
****** e = expert
******** m = master
** o = offensive
*** a = affliction
**** a = advanced
***** e = expert
****** m = master
*** e = elemental
**** a = advanced
***** e = expert
****** m = master

The Test Team Handbook/4 - On a testing server

2022-03-21T09:25:47Z

Ledania:

<noinclude>{{Trad
|DE=Das Test-Team-Handbuch/4 - Auf einem Testserver |DEs=3
|EN=The Test Team Handbook/4 - On a testing server |ENs=0
}}</noinclude>
This document attempt to cover your first steps on one of Ryzom testing servers, with focus on testers. It is expected that you already have access to testing servers and you have successfully configured your clients to be actually able to connect. Consult the [[New Tester's Checklist]] to make sure you didn't forget anything. Following information applies to both testing servers, it is not important if you are on Yubo or Gingo.

==Account characters==
When you log to a testing server for the very first time, all your account slots are empty. It is recommended to create just one or two universal characters that will be always ready and leave other slots empty. Most of testing requires you to have none or just some specific skills and in most cases it is faster to simply create new character on your empty slot (or replace previous) for a test then develop a tool to reset your character or even wait for cool-downs.

When you creating your testing characters, avoid using any real Atys character name. Testing and real accounts are separated however it might bring troubles in the future when for example a character debug is be needed. It also prevents you from confusing which server are you on and which character owns what. Same names requires everyone to pay more attention and you won't to delete your character on wrong server by accident. Your character race or gender is not any important.

==First time on server==
Once you are done with creating your avatar and standing on Silan face to Chiang the Strong, it is time to give your new character some skills. The world of a testing server is, more or less, same as Atys you know. To grind necessary levels is however not needed thanks to various tools you are able to use.

Server accounts have a system of privileges. You will be able to use most of normal testing tools, however some specific applications or commands might require higher privileges than you have. In this case ask on your team/project channel (or on the [https://chat.ryzom.com/group/chat-general #chat-general] channel) so someone else with higher privileges can help you. Following text will tell you how you can adjust various aspects of your character and some basics of your life on a testing server but is not meant to be a manual for tools that you will use.

==In-game tools==
[[File:Appzone beta testing.png|thumb|alt=Beta Testing section of App Zone|Beta Testing section of App Zone]]
First of all we need to make clear which tools will we use. At this moment we have several, more or less, separated applications. Please remember that this part of Ryzom expands widely and may change during the time. In case you have any troubles using it, you find an issue or you want to suggest an improvement contact the specific tool creator please.

===[[File:TT icon command toolbar.png|18px|alt="Command toolbar icon"|left]]Command Toolbar===
[[File:Command toolbar.png|thumb|alt=Command toolbar interface|Command toolbar interface]]
It is a toolbar with various links to other testing and administrative interfaces. By default it is placed on your screen somewhere, unless you made it disappear.
* '''Start:'''
** Execute '''/cmdzone show'''
** Press '''Shift+W''' and start '''Command Toolbar''' application from '''Beta Testing''' section.
* '''Creator:''' [[User:Riasan|Riasan]]
{{clear}}

===[[File:Mp buterfly blue.png|18px|alt="Inky's Tool"|left]]Inky's tool===
[[File:Inkys tool.png|thumb|alt=Inky's tool|Inky's tool]]
This is a compact interface that contains some basic functions mostly related to character allegiance. The tool has a shortcut on the Command Toolbar. Use it to get teleportation related items or zig spawned.
* '''Start:'''
** Execute '''/appzone 2449'''
** Run its shortcut from Command Tollbar (position '''6''')
** Press '''Shift+W''' and start '''Inky's Tool''' application from '''Beta Testing''' section.
* '''Creator:''' [[User:Inky|Inky]]
'''Note:''' Tool creator do not provide any further support nor participate on the project.
{{clear}}

===[[File:Mp batiment noyau maduk.png|18px|alt="Teleport interface"|left]]Teleport interface===
[[File:Teleport interface.png|thumb|alt=Teleport interface|Teleport interface]]
This application is used to quick and free teleportation around the planet. It allows you to use one of fix positions for everyone, use short range landscape teleportation or save and share your own positions. The interface has a shortcut on the Command Toolbar.
* '''Start:'''
** Execute '''/appzone 1356'''
** Run its shortcut from Command Tollbar (position '''8''')
** Press '''Shift+W''' and start '''Teleport interface''' application from '''Beta Testing''' section.
* '''Creator:''' [[User:Riasan|Riasan]]
'''Note:''' Every time you use the teleport interface to move, a command with your current position overwrites your clipboard content.
{{clear}}

==GM island==
This is a secret area in the forest region. Its position is in the Fix list of the Teleport interface and has a link in the Inky's tool. You can find there several additional objects you can interact with. You can contact Riasan about all GM island related tools.

[[File:Gm island red box.png|100px|right|alt=Red Box|Red Box]]
====Red Box====
This object is used to access to various additional tools, items or interfaces and its options change in time by what is needed.

[[File:Gm island pumpkin.png|100px|right|alt=Debug Pumpkin|Debug Pumpkin]]
====Debug Pumpkin====
This pumpking was introduced during development of the Ranger rite and gives you access to various related options like setting allegiance, rite state, reset and so.

[[File:Gm island npc.png|100px|right|alt=NPC on GM island|NPC on GM island]]
====Cult giver NPC====
There are also two NPC who can change you civilization and faction allegiance. However we have more advanced tools now accessible from the Command Toolbar or with Inky's tool.

==Help yourself==
Now it is time to really grow your character. Following list will help you to satisfy all your basic needs:
* To '''get money''', you can use '''Money interface''' from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''1''') or the feature on [[The_Test_Team_Handbook/4_-_On_a_testing_server#Inky.27s_tool|Inky's tool]] with icon of dappers.
* To '''spawn various or special items''' you can use the '''Spawn interface''' from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''11''') or various buttons on [[The_Test_Team_Handbook/4_-_On_a_testing_server##Inky.27s_tool|Inky's tool]] (to get generic raw materials, teleport pacts and artifacts or a pet).
* To '''find a specific item sheet ID''' you can use '''All sheet list items''' interface from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''12''')
* To '''find a specific creature sheet ID''' you can use '''All sheet list creature''' interface from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''2''')
* To '''rise your skill levels''' and (optionally) learn all action bricks you can use the '''Boost''' interface from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''4)
* To '''set your allegiance''' you can use the '''Fame tool''' interface from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''13''', allows you to set allegiance and fame) or options on [[The_Test_Team_Handbook/4_-_On_a_testing_server#Inky.27s_tool|Inky's tool]] (will set your allegiance and adjust your fame automatically) or [[The_Test_Team_Handbook/4_-_On_a_testing_server#Cult_giver_NPC|Cult giver NPC]] on the GM island.
** The [[The_Test_Team_Handbook/4_-_On_a_testing_server#Red_Box|Red Box]] on GM island allows you to set your Marauder rite as done, Inky's tool will give you a Marauder teleportation crystal
** The [[The_Test_Team_Handbook/4_-_On_a_testing_server#Debug_Pumpkin|Debug Pumpkin]] on the GM island allows you to set yourself a Ranger aspirant or a Ranger with various additional options, Inky's tool can spawn you the Ranger Map
* To '''set your fame''' you can use the '''Fame tool''' interface from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''13''')
* To '''quick heal''' your life, sap, stamina or focus you can use the '''State tool''' from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''3'''). This way you can also resurrect yourself.
* To '''travel''', besides running, you can use the '''Teleportation interface''' from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''8''') or spawn yourself teleportation related items using [[The_Test_Team_Handbook/4_-_On_a_testing_server#Inky.27s_tool|Inky's tool]].
** To learn more about current position and the area you can use '''Show Position''' tool from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''18''')
* To '''toggle camera''' between fly and inside your avatar body, use '''Free Camera toggle''' from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''9''')
* To '''start a mission''' by its ID you can use '''Mission helper''' from the [[The_Test_Team_Handbook/4_-_On_a_testing_server#Command_Toolbar|Command Toolbar]] (position '''16''')

==Game mastering==
Sooner or later, how you tester skills will develop, you will face the need of use more powerful tools. The power comes from using commands, knowledge of the system and account privileges. Each server has separated user rights.

===Server privileges===
User accounts on each server might have various privileges. The following list contains all server ranks, sorted from lowest (Tester) to highest (DEV). Regular player accounts are never able apply for any privileges.
* ''Inactive accounts''
* ''Free to play player (F2P)''
* ''Subscribed player (P2P)''
* Tester
* Event Guide (EG)
* Event Manager (EM)
* Senior Event Manager (SEM)
* Guide (G)
* Senior Guide (SG)
* Veteran Guide (VG)
* Game master (GM)
* Senior Game Master (SGM)
* Developer (DEV)
'''Note:''' Understand the list as to be simplified representation of server hierarchy, not to exactly describe server privileges

===Useful information and tools===
There are some external documents and 3rd party tool links that may be helpful or help you with understanding and use of advanced abilities.

====[https://ryzomcore.atlassian.net/wiki/spaces/RC/pages/19365937/Shard+Commands Shard Commands]====
A list of commands that can be used on running server, including privileges. Created by Ryzom Core project. There is another similar [https://raw.githubusercontent.com/osgcc/ryzom/master/ryzom/server/data_shard/client_commands_privileges.txt List of required privileges for client commands]

====[https://ryzomcore.atlassian.net/wiki/spaces/RC/pages/884873/Ryzom+Service+Architecture Ryzom Service Architecture]====
A Ryzom Core document with that lists and shortly describes all Ryzom server services.

====[[Skill_Tree/Skill_decoding|Skill decoding]]====
A post that explains how are skill keys composed, based on first name's letter.

====[https://api.ryzom.com/ Ryzom API documentation]====
API server with documentation related to public Ryzom APIs.

====[https://ryzomcore.atlassian.net/wiki/spaces/RC/pages/11763715/Ingame+browser In-game browser]====
A simple introduction into capabilities and use of the in-game browser, created by Ryzom Core project. It is also good to follow [https://app.ryzom.com/app_forum/index.php?page=topic/view/24138/ Ingame browser capabilities] thread on Ryzom Forum.

====[https://maps.bmsite.net/sample/builder.html Ballistic Mystix map builder]====
A tool to review and export maps of Atys...

====[https://ofancytext.firebaseapp.com/ Ryzom message coloring tool]====
A simple external tool to generate colour codes for coloring in-game messages (MOTD, crafter's message...)

====[https://atys.wiki.ryzom.com/RyzomNameGenerator/ Ryzom name generator]====
A tool to generate random names suitable for Ryzom. There exists also small [https://app.ryzom.com/app_name_gernerator_api/?race=fyros&gender=male Name generator script] that returns a random name by given parameters via URL

====[http://ryzom.aeness.net/ryzom_word/ Items list]====
Besides build-in sheet browser, which is a part of the Spawn tool as well as Command Toolbar, you can also use external lists of item sheets and names. Another option is to use [http://beta.kdyne.net/rygreg/DEVEL/bagapp/?sekce=itemdb-search search for items] in BagApp database or extract files directly from your client.

====[http://beta.kdyne.net/rygreg/DEVEL/langapp/bbtor.php Blablator API]====
A small LangApp API to provide translations with data based on original [[User:Osquallo|Osquallo]]'s Blablator.

{{Portal|Forge}}
[[Category:Test|Test team]]
[[Category:Tutorials|Test team]]
[[Category:Testing Team]]
[[Category:Ryzom Team]]
[[Category:Test]]
[[Category:Tutorials]]

The Test Team Handbook/3 - Setting up connection to non-public Ryzom servers

2022-03-21T09:22:29Z

Ledania:

<noinclude>{{WIP}}{{Trad
|DE=Das Test-Team-Handbuch/3 - Verbindung zu nicht-öffentlichen Ryzom-Servern einrichten |DEs=4
|EN=The Test Team Handbook/3 - Setting up connection to non-public Ryzom servers |ENs=0
}}</noinclude>
=Setting up connection to non-public Ryzom servers <ref>Setting up connection to non-public Ryzom servers @cloud.ryzom.com https://cloud.ryzom.com/f/34233</ref>=

This document describes how to configure a Ryzom client for connection to other Ryzom servers used by Ryzom Teams. It is expected that you are familiar with either using and configuration of the Ryzom Installer and/or capable to do advanced file system management as copying and editing files. The main concern of this document is to describe all necessary steps you need to set up connection to either Yubo or Gingo server.

==Yubo and Gingo (and Atys)==
Yubo and Gingo are names of two not public servers that are used by various teams to review and test the game. Yubo has status of development server and it is the main target where all new changes arrive for the first review. It can easily happen that some parts or the whole server is unstable or broken. Things are under development there. On the other hand, the server Gingo is a clone of Atys server. It is a place where everything supposed to be working and final testing of changes is being made there. We use this server for final testing, to see how will changes in future patch really impact the Live game server and game clients. This document also operates with the term "Live server" or just "Live" which are just other (internal) names of the Atys server. Beta testing on Atys, alias Atys BETA, is a testing on server Atys with beta updates enabled.

==Combinations==
There exist several combinations of your platform and ways of your Ryzom client installation. This document describes as many as possible of them, however the basic is same in all cases. You need to create a copy of your client files for each server and then adjust its configuration a bit for each server.

===Using Steam===
Steam platform is one of ways how to install the Ryzom client. It is possible to configure such client to access Yubo or Gingo server, however updates are distributed via Steam. That means such client will never get frequent updates directly from testing servers and you will not be able to perform any tests, along with possible other issues.
It is possible to add clients for Yubo and Gingo directly to Steam and this feature is planned, however it will require time and resources that the Ryzom team does not have at this moment. Your only current option is to install another non-steam client, static or using Ryzom Installer. Please choose one way and then continue with appropriate configuration details described in this document.

====Running the client with Steam====
After you complete configuration of your clients, static or installed with Ryzom Installer, you can use the Steam ability to become a launcher of non-steam games. You need to perform following steps for both clients:

*Start the Steam platform client if not running already
* Find and click "+ ADD A GAME" in bottom-left corner of the window
* Choose "Add a Non-Steam Game" from its context menu
* Ignore the list of applications and click "BROWSE..." button below
*Navigate to folder with desired client files and change the "File type" option on bottom to "All files"
*Choose the Ryzom client binary (for example "ryzom_client_r2.exe" on Windows or "ryzom_client" on unix-like systems) and click "OPEN" button
* A new line has been added and pre-selected in the list of applications, click "ADD SELECTED PROGRAMS"

A new record was created in your games Library. Right-click it and select Properities to change its details like name or icon.

===Using App Store===
App Store is one of ways how to install Ryzom client on macOS operating system. It is possible to configure such client to access Yubo or Gingo server, however updates are distributed via App Store. That means such client will never get frequent updates directly from testing servers and you will not be able to perform any tests, along with possible other issues. Your only current option is to install another client in different way, static or using Ryzom Installer. Please choose one way and then continue with appropriate configuration details described in this document.

===Using Ryzom Installer===
If you are not using the Ryzom Installer or you are going to configure testing servers manually, you can skip this chapter. To see your Ryzom Installer version, start the application and select Help > About… from the application main menu. Ryzom Installer version older than 3.5.0.9665 do not include settings for testing servers by default.
Before you continue you should update your Ryzom Installer to latest version. You can download its current binary from download.ryzom.com or check if there is any newer version along with your Live client, in the default profile sub-folder, usually at <path_to_ryzom_root>/0/, see default installation paths described in chapter about manual installation. Other option is to combine instructions described in Using Ryzom Installer with GUI and Manual installation with Ryzom Installer or simply follow just instructions for manual installation.

===Using Ryzom Installer with GUI===
Ryzom Installer is a small tool that helps you to install and manage your Ryzom clients. This chapter describes how to setup Yubo and Gingo clients using its user interface. It is expected that you have installed Live client on your system already. Please make sure you are using latest version of the Ryzom installer (>= 3.5.0.9665) that has testing servers configuration included already. Otherwise you need to update your Ryzom Installer version first or define those servers manually in the installer configuration, as described in Manual installation with Ryzom Installer.

====New profiles and separated clients====
It is recommended to have separate clients for each server while mixing patches between more servers might cause troubles. The Ryzom installer will do the most of work automatically for you. Start the Ryzom Installer tool, open Settings from main window menu. There is a list of current profiles on left and selected profile options on right. Click the Add button below the list of profiles to create new and you can start editing its configuration. You will need to create three new profiles, one for Yubo, one for Gingo and one for Atys BETA, along with the normal Atys one you already have there by default. Following list describes each of configuration options.

====Atys BETA client files====
There is no support for beta updates in the current version of Ryzom Installer. You need to create a separated copy manually. Create Yubo and Gingo profiles first, save changes and quit Ryzom Installer. Then go into <code><path_to_ryzom_root></code> and copy "ryzom_live" to "ryzom_beta". Then Start the Ryzom Installer again and create 4th profile for Atys BETA.

:'''Profile''': This option can't be changed. It is a profile ID and is used as a profile subdirectory name.
:'''Name''': Enter any name that will help you identify the profile. This name will be displayed as one of items in the drop-down menu of the main Ryzom Installer window.
:'''Server''': Here you will select the server type. This option will cause that the profile will contain all necessary options for specific server. Choose "Atys" for Atys BETA client profile.
:'''Executable''': This option points to the client executable file and is optional for those who will use non-default client installation location, otherwise just leave it as it is. For the Atys BETA client locate its binary in the <path_to_ryzom_root>/ryzom_beta/ manually using Browse button.
:'''Arguments''': This field can be used to pass arguments to the game client like your login, password and character slot number to use. This is optional and you can leave it blank.
:'''Comments''': You can insert any profile comments you wish here.
:'''Directory''': Displays the path to specific installer profile settings. It was set and subdirectory created along with new profile and its name is based on Profile ID.
:'''Language''': Here you can specify which translation will be used for the client when starting from this profile. If not set, English will be used.
:'''Create shortcuts''': These are additional installer profile options that are not important for the client setup itself.

Once you are done with profiles configuration, click Ok button on bottom right to save changes. It might take some time because the Ryzom Installer will create and configure two new profiles. Those will appear in the drop-down menu on main Ryzom installer window after it is completed.

====Atys BETA options====
Option to adjust Atys BETA client is not available to manage using the Ryzom Installer and you need to edit the profile config file manually. Start Atys BETA client first using the Ryzom installer, this will actually create profile files. Close the Ryzom Installer. Open client.cfg file in <path_to_ryzom_root>/3/ folder to edit and add following code at the end of the file:
Application = { "ryzom_beta", "./client_ryzom_r.exe", "./" };
Now look for RootConfigFilename optionand replace "ryzom_live" with "ryzom_beta" in the path. Save the file. The 4th profile will now accept beta updates for server Atys.

====Running the client====
Now you should have three clients set up, one for the Yubo server, one for the Gingo server and one for Atys BETA, along the default Atys profile. Start the Ryzom Installer and use the drop-down selection on bottom of the main window to choose which profile (and client) you wish to use.

===Manual installation with Ryzom Installer===
Ryzom Installer is a small tool that helps you to install and manage your Ryzom clients. This document describes how to setup '''Yubo''' and '''Gingo''' clients without user interface. It is expected you have installed Live client on your system already.

====Client files====
First step you need to do is to create a copy of your Live client files. It is recommended to have separate clients for each server while mixing patches between more servers might cause troubles. Close the Ryzom installer and Ryzom client, in case it is running, open the installation folder and copy the sub-folder "ryzom_live" to "ryzom_dev" to use as a client of the Yubo server. Then create another copy called "ryzom_test" to use as a client of the Gingo server. Then create the last copy called "ryzom_beta" to use as a client of the Atys server with beta updates enabled.

Following list contains default installation paths of all three supported platforms as well as paths where Ryzom Installer profiles are stored. 
The "~" path prefix is an unix alias for user home directory, for example "<code>/home/user</code>". 
<code>%AppData%</code> is the variable name for the application data directory under modern Windows systems, for example "<code>C:\Users\%username%\AppData</code>". More detailed information about system paths is described by the [[Ryzom location]] article on the Ryzom Wiki.
{| class="wikitable"
|-
! System !! Default client installation !! Ryzom Installer profiles location
|-
| Windows XP || <code>C:\Documents and Settings\{user}\Local Settings\Application Data\Ryzom\</code> || <code>C:\Documents and Settings\{user}\Local Settings\Application Data\Ryzom\</code>
|-
| Windows Vista/7/8/10 || <code>%AppData%\Local\Ryzom\</code> || <code>%AppData%\Roaming\Ryzom\</code>
|-
| Linux || <code>~/.local/share/Ryzom/</code> || <code>~/.local/share/Ryzom/</code>
|-
| MacOS || <code>~/Library/Application Support/Ryzom/</code> || <code>~/Library/Application Support/Ryzom/</code>
|}

====Server connection====
This step applies only when you are using older version of the Ryzom installer. With version 3.5.0.9692 or newer, both testing servers are already part of installer configuration, however not for Atys with beta updates. In case you want or must use the older installer, you need to define two new servers in the <code>ryzom_installer.ini</code> file which is stored along your client installations. 
Open the file in a text editor, locate end of section <code>[server_0]</code> and insert following block right after end of the the section, before the <code>[servers]</code> section:
[server_1]
client_download_filename=ryzom_live_client_$ARCH.7z
client_download_url="http://download.ryzom.com/ryzom_live_client_$ARCH.7z?r=&ts=$TIMESTAMP"
client_filename_linux=ryzom_client
client_filename_old_linux=
client_filename_old_windows=client_ryzom_rd.exe
client_filename_osx=Ryzom.app/Contents/MacOS/Ryzom
client_filename_windows=ryzom_client_r.exe
comments=Dev server
configuration_filename_linux=ryzom_configuration_qt
configuration_filename_osx=Ryzom.app/Contents/MacOS/RyzomConfiguration
configuration_filename_windows=ryzom_configuration_qt_r.exe
data_compressed_size=1500000000
data_download_filename=ryzom_live_data.7z
data_download_url="http://download.ryzom.com/ryzom_live_data.7z?r=&ts=$TIMESTAMP"
data_uncompressed_size=7000000000
display_url="http://app.ryzom.com/app_releasenotes/index.php?lang=$LANG"
files_list_url="https://sourceforge.net/projects/ryzom/rss?path=/installer"
id=ryzom_dev
name=Yubo

[server_2]
client_download_filename=ryzom_live_client_$ARCH.7z
client_download_url="http://download.ryzom.com/ryzom_live_client_$ARCH.7z?r=&ts=$TIMESTAMP"
client_filename_linux=ryzom_client
client_filename_old_linux=
client_filename_old_windows=client_ryzom_rd.exe
client_filename_osx=Ryzom.app/Contents/MacOS/Ryzom
client_filename_windows=ryzom_client_r.exe
comments=Test server
configuration_filename_linux=ryzom_configuration_qt
configuration_filename_osx=Ryzom.app/Contents/MacOS/RyzomConfiguration
configuration_filename_windows=ryzom_configuration_qt_r.exe
data_compressed_size=1500000000
data_download_filename=ryzom_live_data.7z
data_download_url="http://download.ryzom.com/ryzom_live_data.7z?r=&ts=$TIMESTAMP"
data_uncompressed_size=7000000000
display_url="http://app.ryzom.com/app_releasenotes/index.php?lang=$LANG"
files_list_url="https://sourceforge.net/projects/ryzom/rss?path=/installer"
id=ryzom_test
name=Gingo

As you can see, the configurations are almost the same. Server one operates with "ryzom_dev" (Yubo), Server 2 with "ryzom_test" (Gingo) and the last one (server 0) with "ryzom_live" (Atys BETA). Also server names differ. Next go to [servers] section and change the value of size to number 3. It will look like this:
[servers]
default=0
size=3

====Profile configuration====
You have two exactly same copies of the ryzom client now, one for each server. You also have new servers defined in installer configuration. Now you need to create two new installer profiles. These steps will lead to same results as when using the GUI, however you will create new profiles, one for Yubo and one for Gingo, manually. 
Open the folder with Ryzom Installer profiles. You will find a folder called "<code>0</code>" there. Create a copy with name "<code>1</code>" for your Yubo client and another with name "<code>2</code>" for your Gingo client. Then create the last one "<code>3</code>" for the client of Atys with beta updates. The next step is to create configuration for all three new profiles, "1", "2" and "3", so the installer can find them.

Open <code>ryzom_installer.ini</code> file for editing, it is located in the same folder, and scroll to locate end of section <code>[profile_0]</code> . Then insert following block of text right after it, before the section <code>[profiles]</code>:
[profile_1]
arguments=
comments=Development server
desktop_shortcut=false
executable=
id=1
menu_shortcut=false
name=Ryzom (Yubo)
server=ryzom_dev

[profile_2]
arguments=
comments=Testing server
desktop_shortcut=false
executable=
id=2
menu_shortcut=false
name=Ryzom (Gingo)
server=ryzom_test

[profile_3]
arguments=
comments=Atys with beta updates
desktop_shortcut=false
executable=
id=3
menu_shortcut=false
name=Ryzom (Atys BETA)
server=ryzom_live

In case your client files are not saved in default path, you need to insert full path to client binary into the executable option. For Yubo client in <code>[profile_1]</code> section (with client located in ''ryzom_'''dev''' folder''), for Gingo client in <code>[profile_2]</code> (with client located in ''ryzom_'''test''' folder'').

As next go to [profiles] section and change the value of size to number 3. This says how many profiles is present. It should look like this now:
[profiles]
default=0
size=3

====Special client option====
The last thing you need to do is to edit each client configuration file and add special option so the client knows you wish to connect to a specific non-public server. Configuration of clients using the Ryzom installer is pre-configured to have custom configuration file included. Additional client configuration is stored in Ryzom Installer profiles location.

=====Yubo client configuration=====
Navigate to the Yubo profile folder "<code>1</code>" in Ryzom Installer profiles location and open <code>client.cfg</code> file for editing. Then add following block to the end of the file:
Application = {
"ryzom_dev", "./client_ryzom_r.exe", "./" 
};

=====Gingo client configuration=====
Navigate to the Gingo profile folder "<code>2</code>" in Ryzom Installer profiles location and open <code>client.cfg</code> file for editing. Then add following block to the end of the file:
Application = {
"ryzom_test", "./client_ryzom_r.exe", "./" 
};

=====Atys BETA client configuration=====
Navigate to the Atys BETA profile folder "<code>3</code>" in Ryzom Installer profiles location and open <code>client.cfg</code> file for editing. Then add following block to the end of the file:
Application = {
"ryzom_beta", "./client_ryzom_r.exe", "./" 
};

====Running the client====
Now you should have two client set up, one for the Yubo server, one for the Gingo server. Start the Ryzom Installer and use the drop-down selection on bottom of the main window to choose which profile (and client) you wish to use.

===Static client===
It is not required to use the Ryzom Installer to use the Ryzom client. This document describes how to setup both testing servers manually without any use of the Installer. It is expected that you have a static Live client installed on your system already.

====Client files====
The first step you need to do is to create a copy of your Live client files. It is recommended to have ''separate'' clients for each server while mixing patches between more servers might cause troubles. There is no default installation path for the static client.

Find the folder where is your Live client installed (for example "<code>C:\Games</code>" or "<code>/opt</code>") and copy the whole game folder (for example "<code>C:\Games\Ryzom</code>" or "<code>/opt/ryzom</code>") to "<code>ryzom_dev</code>" in same folder. This installation will be used to connect to the '''Yubo''' server. Then create another copy in same folder called "ryzom_test", this one will be used fot the '''Gingo''' server.

====Special client option====
The next thing you need to do is to edit each client configuration file and add special option so the client knows you wish to connect to a specific non-public server.

Yubo client configuration
Navigate to the root folder of your Yubo client installation, for example "<code>C:\Games\ryzom_dev</code>" or "<code>/opt/ryzom_dev</code>" and open the <code>client.cfg</code> file for editing. Scroll to the end of the file and add following block of text:
Application = {
"ryzom_dev", "./client_ryzom_r.exe", "./" 
};

=====Gingo client configuration=====
Navigate to the root folder of your Gingo client installation, for example "<code>C:\Games\ryzom_test</code>" or "<code>/opt/ryzom_test</code>" and open the <code>client.cfg</code> file for editing. Scroll to the end of the file and add following block of text:
Application = {
"ryzom_test", "./client_ryzom_r.exe", "./" 
};

=====Atys BETA client configuration=====
Navigate to the root folder of your Atys BETA client installation, for example "<code>C:\Games\ryzom_beta</code>" or "<code>/opt/ryzom_test</code>" and open the <code>client.cfg</code> file for editing. Scroll to the end of the file and add following block of text:
Application = {
"ryzom_beta", "./client_ryzom_r.exe", "./" 
};

====Running the client====
Now you should have two client set up, one for the Yubo server, one for the Gingo server. To start the Yubo client, navigate to your "ryzom_dev" folder and start the client binary, for example "<code>C:\Games\ryzom_dev\ryzom_client_r.exe</code>" or "<code>/opt/ryzom_dev/ryzom_client</code>".
To start the Gingo client, navigate to your "<code>ryzom_test</code>" folder and start the client binary, for example "<code>C:\Games\ryzom_test\ryzom_client_r.exe</code>" or "<code>/opt/ryzom_test/ryzom_client</code>".
Another option is to create main menu / desktop shortcuts to start the right binary from the right folder for each client.

==Closing tips==
It is recommended to use separate clients for each server. It is possible to configure one client to be able to access all three servers, however different updates for each server might break your client or bring other troubles.

Yubo and Gingo are getting non-production client updates and things might go wrong time to time. A good practice is to keep one another separated copy with fresh Ryzom Installation (along Atys, Yubo and Gingo server) that you can use to quickly restore a broken client. Just make sure you back-up your configuration and character-related files before you replace the broken copy. The Ryzom installer makes things easier.
 
 
 
————————
<references/>
 
 
{{Portal|Forge}}
[[Category:Test|Test team]]
[[Category:Tutorials|Test team]]
[[Category:Testing Team]]
[[Category:Ryzom Team]]
[[Category:Test]]
[[Category:Tutorials]]

Ryzom location

2022-03-21T08:27:33Z

Ledania:

{{stub}}
{{Trad
|DE=Benutzerhandbuch/Abschnitt 1 - Ryzom-Ordner und -Dateien
|EN=Ryzom location
|ES=
|FR=Manuel de l'utilisateur/Ch 1 - Dossiers et fichiers de Ryzom
|RU=
}}
{{TIP
|FR=0
|EN=3
|ES=1
|DE=4
|RU=1
}}
There are 3 ways to install Ryzom

* the official one, with the Ryzom installer (in v5 in June 2019), which allows to easily manage various profiles.
* using Steam (contact support if you want your account to be unlink from Steam)
* as a static client (without the installer, App Store Mac,...).

== Files to save ==
A folder to backup: save

Here are the main file to backup (where ''avatar'' is the name of your toon):

* keys_avatar.xml has keyboards shortcuts and macros
* groups_avatar.xml jewels/armor/tools groups
* landmarks_avatar.xml landmarks saved on your map
* log_avatar.xml (if activated) the logs of your toon (chats)
* channels_avatar.xml More on [[New2019/JY_2603_Documentation#Dynamic channels restoration]]

Note 
You can share your macros (several toons on the same PC) using a single '''shared_keys.xml'''. To do this, you need to rename your keys_avatar.xml file (if a keys_avatar.xml exists in the folder, shared_keys.xml won't be used).

FYI:

* contactgroups_avatar.xml to change which contact is in which group (having quit the game) - linked to the [[Patch 00834]] (2020/09).
* log_avatar.txt is generated by the command /chatLog - more at [[Special command]]. Use it with the [[Webapps main|webapp]] '''Chat log decoder''' or https://ryzom.kervala.net/logs.php
* interface_avatar.icfg in a binary file (that can't be opened with a simple editor)

== Linux ==

=== With Ryzom Installer ===

* Data (Client executable + client_default.cfg + Data) is in '''$HOME/.local/share/Ryzom/{server_id}''', server_id beeing "ryzom_live" by default
* Profile (screenshots, save, user, client.cfg)is in '''$HOME/.local/share/Ryzom/{ProfileNumber}'''

=== With Steam ===

You'll need to find your SteamLibrary folder where your games are saved, (default location is '''$HOME/steam/SteamLibrary/steamapps/common/Ryzom''') and find the Ryzom folder inside.
* Data (Client executable + client_default.cfg + data) is directly in that folder
* Profile (screenshots, save, user, client.cfg) is also directly in that folder

== Windows Vista or newer ==

=== With Ryzom Installer ===

* Data (Client executable + client_default.cfg + Data) is in '''C:\Users\{YourName}\AppData\Local\Ryzom\{server_id}''', server_id beeing "ryzom_live" by default
* Profile (screenshots, save, user, client.cfg)is in '''C:\Users\{YourName}\AppData\Roaming\Ryzom\{ProfileNumber}'''
Note : You can access the AppData folder by typing %appdata% in the start search box

=== With Steam ===

You'll need to find your Steam library folder where your games are saved, default location is '''C:\Program Files (x86)\Steam\steamapps\common\Ryzom''' but you can change it.
* Data (Client executable + client_default.cfg + data) is directly in that folder
* Profile (screenshots, save, user, client.cfg) is also directly in that folder

== Windows XP ==
'''XP is not supported by MicroSoft''' for several years (GNU Linux are fine for old PCs). With patch JY 2603, we discovered that XP users had issues.
With Ryzom Installer

* Data (Client executable + client_default.cfg + Data) is in '''C:\Documents and Settings\{YourName}\Local Settings\Application Data\Ryzom\{server_id}''', server_id beeing "ryzom_live" by default
* Profile (screenshots, save, user, client.cfg) is in '''C:\Documents and Settings\{YourName}\Application Data\Ryzom\{ProfileNumber}'''

=== With Steam ===

You'll need to find your Steam library folder where your games are saved, default location is '''C:\Program Files\Steam\steamapps\common\Ryzom''' but you can change it.
* Data (Client executable + client_default.cfg + Data) is also directly in that folder
* Profile (screenshots, save, user, client.cfg) is also directly in that folder

== Mac OS X ==

=== With Ryzom Installer ===

* Data (Client executable + client_default.cfg + Data) is in '''$HOME/Library/Application Support/Ryzom/{server_id}''', server_id beeing "ryzom_live" by default
* Profile (screenshots, save, user, client.cfg) is in '''$HOME/Library/Application Support/Ryzom/{ProfileNumber}'''

=== With App Store ===

* Data (Client executable + client_default.cfg + Data) is in '''/Applications/Ryzom.app'''
* Profile (screenshots, save, user, client.cfg) is in the same folder, '''$HOME/Library/Containers/com.winchgate.Ryzom/Data/Library/Application Support/Ryzom'''

=== With Steam ===

* Data (Client executable + client_default.cfg + data) is in '''$HOME/Library/Application Support/Steam/SteamApps/common/Ryzom''' or another directory if you changed it
* Profile (screenshots, save, user, client.cfg) is in '''$HOME/Library/Application Support/Ryzom'''

<noinclude>
{{Portal|Forge|Gameplay}}
[[category:Support]]
</noinclude>

The Test Team Handbook/3 - Setting up connection to non-public Ryzom servers

2022-03-21T06:59:52Z

Ledania:

<noinclude>{{WIP}}{{Trad
|DE=Das Test-Team-Handbuch/3 - Verbindung zu nicht-öffentlichen Ryzom-Servern einrichten |DEs=3
|EN=The Test Team Handbook/3 - Setting up connection to non-public Ryzom servers |ENs=0
}}</noinclude>
=Setting up connection to non-public Ryzom servers <ref>Setting up connection to non-public Ryzom servers @cloud.ryzom.com https://cloud.ryzom.com/f/34233</ref>=

This document describes how to configure a Ryzom client for connection to other Ryzom servers used by Ryzom Teams. It is expected that you are familiar with either using and configuration of the Ryzom Installer and/or capable to do advanced file system management as copying and editing files. The main concern of this document is to describe all necessary steps you need to set up connection to either Yubo or Gingo server.

==Yubo and Gingo (and Atys)==
Yubo and Gingo are names of two not public servers that are used by various teams to review and test the game. Yubo has status of development server and it is the main target where all new changes arrive for the first review. It can easily happen that some parts or the whole server is unstable or broken. Things are under development there. On the other hand, the server Gingo is a clone of Atys server. It is a place where everything supposed to be working and final testing of changes is being made there. We use this server for final testing, to see how will changes in future patch really impact the Live game server and game clients. This document also operates with the term "Live server" or just "Live" which are just other (internal) names of the Atys server. Beta testing on Atys, alias Atys BETA, is a testing on server Atys with beta updates enabled.

==Combinations==
There exist several combinations of your platform and ways of your Ryzom client installation. This document describes as many as possible of them, however the basic is same in all cases. You need to create a copy of your client files for each server and then adjust its configuration a bit for each server.

===Using Steam===
Steam platform is one of ways how to install the Ryzom client. It is possible to configure such client to access Yubo or Gingo server, however updates are distributed via Steam. That means such client will never get frequent updates directly from testing servers and you will not be able to perform any tests, along with possible other issues.
It is possible to add clients for Yubo and Gingo directly to Steam and this feature is planned, however it will require time and resources that the Ryzom team does not have at this moment. Your only current option is to install another non-steam client, static or using Ryzom Installer. Please choose one way and then continue with appropriate configuration details described in this document.

====Running the client with Steam====
After you complete configuration of your clients, static or installed with Ryzom Installer, you can use the Steam ability to become a launcher of non-steam games. You need to perform following steps for both clients:

*Start the Steam platform client if not running already
* Find and click "+ ADD A GAME" in bottom-left corner of the window
* Choose "Add a Non-Steam Game" from its context menu
* Ignore the list of applications and click "BROWSE..." button below
*Navigate to folder with desired client files and change the "File type" option on bottom to "All files"
*Choose the Ryzom client binary (for example "ryzom_client_r2.exe" on Windows or "ryzom_client" on unix-like systems) and click "OPEN" button
* A new line has been added and pre-selected in the list of applications, click "ADD SELECTED PROGRAMS"

A new record was created in your games Library. Right-click it and select Properities to change its details like name or icon.

===Using App Store===
App Store is one of ways how to install Ryzom client on macOS operating system. It is possible to configure such client to access Yubo or Gingo server, however updates are distributed via App Store. That means such client will never get frequent updates directly from testing servers and you will not be able to perform any tests, along with possible other issues. Your only current option is to install another client in different way, static or using Ryzom Installer. Please choose one way and then continue with appropriate configuration details described in this document.

===Using Ryzom Installer===
If you are not using the Ryzom Installer or you are going to configure testing servers manually, you can skip this chapter. To see your Ryzom Installer version, start the application and select Help > About… from the application main menu. Ryzom Installer version older than 3.5.0.9665 do not include settings for testing servers by default.
Before you continue you should update your Ryzom Installer to latest version. You can download its current binary from download.ryzom.com or check if there is any newer version along with your Live client, in the default profile sub-folder, usually at <path_to_ryzom_root>/0/, see default installation paths described in chapter about manual installation. Other option is to combine instructions described in Using Ryzom Installer with GUI and Manual installation with Ryzom Installer or simply follow just instructions for manual installation.

===Using Ryzom Installer with GUI===
Ryzom Installer is a small tool that helps you to install and manage your Ryzom clients. This chapter describes how to setup Yubo and Gingo clients using its user interface. It is expected that you have installed Live client on your system already. Please make sure you are using latest version of the Ryzom installer (>= 3.5.0.9665) that has testing servers configuration included already. Otherwise you need to update your Ryzom Installer version first or define those servers manually in the installer configuration, as described in Manual installation with Ryzom Installer.

====New profiles and separated clients====
It is recommended to have separate clients for each server while mixing patches between more servers might cause troubles. The Ryzom installer will do the most of work automatically for you. Start the Ryzom Installer tool, open Settings from main window menu. There is a list of current profiles on left and selected profile options on right. Click the Add button below the list of profiles to create new and you can start editing its configuration. You will need to create three new profiles, one for Yubo, one for Gingo and one for Atys BETA, along with the normal Atys one you already have there by default. Following list describes each of configuration options.

====Atys BETA client files====
There is no support for beta updates in the current version of Ryzom Installer. You need to create a separated copy manually. Create Yubo and Gingo profiles first, save changes and quit Ryzom Installer. Then go into <code><path_to_ryzom_root></code> and copy "ryzom_live" to "ryzom_beta". Then Start the Ryzom Installer again and create 4th profile for Atys BETA.

:'''Profile''': This option can't be changed. It is a profile ID and is used as a profile subdirectory name.
:'''Name''': Enter any name that will help you identify the profile. This name will be displayed as one of items in the drop-down menu of the main Ryzom Installer window.
:'''Server''': Here you will select the server type. This option will cause that the profile will contain all necessary options for specific server. Choose "Atys" for Atys BETA client profile.
:'''Executable''': This option points to the client executable file and is optional for those who will use non-default client installation location, otherwise just leave it as it is. For the Atys BETA client locate its binary in the <path_to_ryzom_root>/ryzom_beta/ manually using Browse button.
:'''Arguments''': This field can be used to pass arguments to the game client like your login, password and character slot number to use. This is optional and you can leave it blank.
:'''Comments''': You can insert any profile comments you wish here.
:'''Directory''': Displays the path to specific installer profile settings. It was set and subdirectory created along with new profile and its name is based on Profile ID.
:'''Language''': Here you can specify which translation will be used for the client when starting from this profile. If not set, English will be used.
:'''Create shortcuts''': These are additional installer profile options that are not important for the client setup itself.

Once you are done with profiles configuration, click Ok button on bottom right to save changes. It might take some time because the Ryzom Installer will create and configure two new profiles. Those will appear in the drop-down menu on main Ryzom installer window after it is completed.

====Atys BETA options====
Option to adjust Atys BETA client is not available to manage using the Ryzom Installer and you need to edit the profile config file manually. Start Atys BETA client first using the Ryzom installer, this will actually create profile files. Close the Ryzom Installer. Open client.cfg file in <path_to_ryzom_root>/3/ folder to edit and add following code at the end of the file:
Application = { "ryzom_beta", "./client_ryzom_r.exe", "./" };
Now look for RootConfigFilename optionand replace "ryzom_live" with "ryzom_beta" in the path. Save the file. The 4th profile will now accept beta updates for server Atys.

====Running the client====
Now you should have three clients set up, one for the Yubo server, one for the Gingo server and one for Atys BETA, along the default Atys profile. Start the Ryzom Installer and use the drop-down selection on bottom of the main window to choose which profile (and client) you wish to use.

===Manual installation with Ryzom Installer===
Ryzom Installer is a small tool that helps you to install and manage your Ryzom clients. This document describes how to setup '''Yubo''' and '''Gingo''' clients without user interface. It is expected you have installed Live client on your system already.

====Client files====
First step you need to do is to create a copy of your Live client files. It is recommended to have separate clients for each server while mixing patches between more servers might cause troubles. Close the Ryzom installer and Ryzom client, in case it is running, open the installation folder and copy the sub-folder "ryzom_live" to "ryzom_dev" to use as a client of the Yubo server. Then create another copy called "ryzom_test" to use as a client of the Gingo server. Then create the last copy called "ryzom_beta" to use as a client of the Atys server with beta updates enabled.

Following list contains default installation paths of all three supported platforms as well as paths where Ryzom Installer profiles are stored. 
The "~" path prefix is an unix alias for user home directory, for example "<code>/home/user</code>". 
<code>%AppData%</code> is the variable name for the application data directory under modern Windows systems, for example "<code>C:\Users\%username%\AppData</code>". More detailed information about system paths is described by the [[Ryzom location]] article on the Ryzom Wiki.
{| class="wikitable"
|-
! System !! Default client installation !! Ryzom Installer profiles location
|-
| Windows XP || <code>C:\Documents and Settings\{user}\Local Settings\Application Data\Ryzom\</code> || <code>C:\Documents and Settings\{user}\Local Settings\Application Data\Ryzom\</code>
|-
| Windows Vista/7/8/10 || <code>%AppData%\Local\Ryzom\</code> || <code>%AppData%\Roaming\Ryzom\</code>
|-
| Linux || <code>~/.local/share/Ryzom/</code> || <code>~/.local/share/Ryzom/</code>
|-
| MacOS || <code>~/Library/Application Support/Ryzom/</code> || <code>~/Library/Application Support/Ryzom/</code>
|}

====Server connection====
This step applies only when you are using older version of the Ryzom installer. With version 3.5.0.9692 or newer, both testing servers are already part of installer configuration, however not for Atys with beta updates. In case you want or must use the older installer, you need to define two new servers in the <code>ryzom_installer.ini</code> file which is stored along your client installations. 
Open the file in a text editor, locate end of section <code>[server_0]</code> and insert following block right after end of the the section, before the <code>[servers]</code> section:
[server_1]
client_download_filename=ryzom_live_client_$ARCH.7z
client_download_url="http://download.ryzom.com/ryzom_live_client_$ARCH.7z?r=&ts=$TIMESTAMP"
client_filename_linux=ryzom_client
client_filename_old_linux=
client_filename_old_windows=client_ryzom_rd.exe
client_filename_osx=Ryzom.app/Contents/MacOS/Ryzom
client_filename_windows=ryzom_client_r.exe
comments=Dev server
configuration_filename_linux=ryzom_configuration_qt
configuration_filename_osx=Ryzom.app/Contents/MacOS/RyzomConfiguration
configuration_filename_windows=ryzom_configuration_qt_r.exe
data_compressed_size=1500000000
data_download_filename=ryzom_live_data.7z
data_download_url="http://download.ryzom.com/ryzom_live_data.7z?r=&ts=$TIMESTAMP"
data_uncompressed_size=7000000000
display_url="http://app.ryzom.com/app_releasenotes/index.php?lang=$LANG"
files_list_url="https://sourceforge.net/projects/ryzom/rss?path=/installer"
id=ryzom_dev
name=Yubo

[server_2]
client_download_filename=ryzom_live_client_$ARCH.7z
client_download_url="http://download.ryzom.com/ryzom_live_client_$ARCH.7z?r=&ts=$TIMESTAMP"
client_filename_linux=ryzom_client
client_filename_old_linux=
client_filename_old_windows=client_ryzom_rd.exe
client_filename_osx=Ryzom.app/Contents/MacOS/Ryzom
client_filename_windows=ryzom_client_r.exe
comments=Test server
configuration_filename_linux=ryzom_configuration_qt
configuration_filename_osx=Ryzom.app/Contents/MacOS/RyzomConfiguration
configuration_filename_windows=ryzom_configuration_qt_r.exe
data_compressed_size=1500000000
data_download_filename=ryzom_live_data.7z
data_download_url="http://download.ryzom.com/ryzom_live_data.7z?r=&ts=$TIMESTAMP"
data_uncompressed_size=7000000000
display_url="http://app.ryzom.com/app_releasenotes/index.php?lang=$LANG"
files_list_url="https://sourceforge.net/projects/ryzom/rss?path=/installer"
id=ryzom_test
name=Gingo

As you can see, the configurations are almost the same. Server one operates with "ryzom_dev" (Yubo), Server 2 with "ryzom_test" (Gingo) and the last one (server 0) with "ryzom_live" (Atys BETA). Also server names differ. Next go to [servers] section and change the value of size to number 3. It will look like this:
[servers]
default=0
size=3

====Profile configuration====
You have two exactly same copies of the ryzom client now, one for each server. You also have new servers defined in installer configuration. Now you need to create two new installer profiles. These steps will lead to same results as when using the GUI, however you will create new profiles, one for Yubo and one for Gingo, manually. 
Open the folder with Ryzom Installer profiles. You will find a folder called "<code>0</code>" there. Create a copy with name "<code>1</code>" for your Yubo client and another with name "<code>2</code>" for your Gingo client. Then create the last one "<code>3</code>" for the client of Atys with beta updates. The next step is to create configuration for all three new profiles, "1", "2" and "3", so the installer can find them.

Open <code>ryzom_installer.ini</code> file for editing, it is located in the same folder, and scroll to locate end of section <code>[profile_0]</code> . Then insert following block of text right after it, before the section <code>[profiles]</code>:
[profile_1]
arguments=
comments=Development server
desktop_shortcut=false
executable=
id=1
menu_shortcut=false
name=Ryzom (Yubo)
server=ryzom_dev

[profile_2]
arguments=
comments=Testing server
desktop_shortcut=false
executable=
id=2
menu_shortcut=false
name=Ryzom (Gingo)
server=ryzom_test

[profile_3]
arguments=
comments=Atys with beta updates
desktop_shortcut=false
executable=
id=3
menu_shortcut=false
name=Ryzom (Atys BETA)
server=ryzom_live

In case your client files are not saved in default path, you need to insert full path to client binary into the executable option. For Yubo client in <code>[profile_1]</code> section (with client located in ''ryzom_'''dev''' folder''), for Gingo client in <code>[profile_2]</code> (with client located in ''ryzom_'''test''' folder'').

As next go to [profiles] section and change the value of size to number 3. This says how many profiles is present. It should look like this now:
[profiles]
default=0
size=3

====Special client option====
The last thing you need to do is to edit each client configuration file and add special option so the client knows you wish to connect to a specific non-public server. Configuration of clients using the Ryzom installer is pre-configured to have custom configuration file included. Additional client configuration is stored in Ryzom Installer profiles location.

=====Yubo client configuration=====
Navigate to the Yubo profile folder "<code>1</code>" in Ryzom Installer profiles location and open <code>client.cfg</code> file for editing. Then add following block to the end of the file:
Application = {
"ryzom_dev", "./client_ryzom_r.exe", "./" 
};

=====Gingo client configuration=====
Navigate to the Gingo profile folder "<code>2</code>" in Ryzom Installer profiles location and open <code>client.cfg</code> file for editing. Then add following block to the end of the file:
Application = {
"ryzom_test", "./client_ryzom_r.exe", "./" 
};

=====Atys BETA client configuration=====
Navigate to the Atys BETA profile folder "<code>3</code>" in Ryzom Installer profiles location and open <code>client.cfg</code> file for editing. Then add following block to the end of the file:
Application = {
"ryzom_beta", "./client_ryzom_r.exe", "./" 
};

====Running the client====
Now you should have two client set up, one for the Yubo server, one for the Gingo server. Start the Ryzom Installer and use the drop-down selection on bottom of the main window to choose which profile (and client) you wish to use.

===Static client===
It is not required to use the Ryzom Installer to use the Ryzom client. This document describes how to setup both testing servers manually without any use of the Installer. It is expected that you have a static Live client installed on your system already.

====Client files====
The first step you need to do is to create a copy of your Live client files. It is recommended to have ''separate'' clients for each server while mixing patches between more servers might cause troubles. There is no default installation path for the static client.

Find the folder where is your Live client installed (for example "<code>C:\Games</code>" or "<code>/opt</code>") and copy the whole game folder (for example "<code>C:\Games\Ryzom</code>" or "<code>/opt/ryzom</code>") to "<code>ryzom_dev</code>" in same folder. This installation will be used to connect to the '''Yubo''' server. Then create another copy in same folder called "ryzom_test", this one will be used fot the '''Gingo''' server.

====Special client option====
The next thing you need to do is to edit each client configuration file and add special option so the client knows you wish to connect to a specific non-public server.

Yubo client configuration
Navigate to the root folder of your Yubo client installation, for example "<code>C:\Games\ryzom_dev</code>" or "<code>/opt/ryzom_dev</code>" and open the <code>client.cfg</code> file for editing. Scroll to the end of the file and add following block of text:
Application = {
"ryzom_dev", "./client_ryzom_r.exe", "./" 
};

=====Gingo client configuration=====
Navigate to the root folder of your Gingo client installation, for example "<code>C:\Games\ryzom_test</code>" or "<code>/opt/ryzom_test</code>" and open the <code>client.cfg</code> file for editing. Scroll to the end of the file and add following block of text:
Application = {
"ryzom_test", "./client_ryzom_r.exe", "./" 
};

=====Atys BETA client configuration=====
Navigate to the root folder of your Atys BETA client installation, for example "<code>C:\Games\ryzom_beta</code>" or "<code>/opt/ryzom_test</code>" and open the <code>client.cfg</code> file for editing. Scroll to the end of the file and add following block of text:
Application = {
"ryzom_beta", "./client_ryzom_r.exe", "./" 
};

====Running the client====
Now you should have two client set up, one for the Yubo server, one for the Gingo server. To start the Yubo client, navigate to your "ryzom_dev" folder and start the client binary, for example "<code>C:\Games\ryzom_dev\ryzom_client_r.exe</code>" or "<code>/opt/ryzom_dev/ryzom_client</code>".
To start the Gingo client, navigate to your "<code>ryzom_test</code>" folder and start the client binary, for example "<code>C:\Games\ryzom_test\ryzom_client_r.exe</code>" or "<code>/opt/ryzom_test/ryzom_client</code>".
Another option is to create main menu / desktop shortcuts to start the right binary from the right folder for each client.

==Closing tips==
It is recommended to use separate clients for each server. It is possible to configure one client to be able to access all three servers, however different updates for each server might break your client or bring other troubles.

Yubo and Gingo are getting non-production client updates and things might go wrong time to time. A good practice is to keep one another separated copy with fresh Ryzom Installation (along Atys, Yubo and Gingo server) that you can use to quickly restore a broken client. Just make sure you back-up your configuration and character-related files before you replace the broken copy. The Ryzom installer makes things easier.
 
 
 
————————
<references/>
 
 
{{Portal|Forge}}
[[Category:Test|Test team]]
[[Category:Tutorials|Test team]]
[[Category:Testing Team]]
[[Category:Ryzom Team]]
[[Category:Test]]
[[Category:Tutorials]]

The Test Team Handbook/2 - External team tools

2022-03-21T06:53:09Z

Ledania:

{{Trad
|DE =Das Test-Team-Handbuch/2 - Externe Teamwerkzeuge|DEs=4
|EN =The Test Team Handbook/2 - External team tools|ENs=0
|ES =The Test Team Handbook|ESs=5
|FR =The Test Team Handbook|FRs=5
|RU =The Test Team Handbook|RUs=5
|H =
|palette=Grey
}}
This document shortly describes external tools that are useful for every team member. These tools are not working in-game or just in a very limited way and you need to use external browser. The goal is not to supply any user manual just give you a basic overview about what do we use, how it could be useful and how to log in. The second part of this document is focused on members of the Test team.

=General information=
Here is a basic description of all important external tools that you should keep in mind and use.
==Ryzom chat (RC)==
You probably know the Ryzom chat already. It is a tool that allows you to read in-game chats without a need to be actually in game. You will have "~" (tilde) prefix in front of your name in case of every message sent from RC to the game. Some additional details about Ryzom chat are described in the [[Chat/RC_FAQ|RC FAQ article]].

Another important role of the Ryzom chat is also that each team or project have own private chat room available. Team chat rooms have a "t-" prefix and project chat rooms have "pj-" prefix. By default every team member supposed be member of all following rooms:
* [https://chat.ryzom.com/group/announcements #announcement]
* [https://chat.ryzom.com/group/chat-general #chat-general]
* [https://chat.ryzom.com/group/chat-ark_dev #chat-ark_dev]
Internal chat rooms are not public thus you must become a member of a team/project first to see other private rooms then default ones. In all cases if you think you have lost or didn't get access to a specific channel you should be presented on (including default ones) please contact Tamarea or Tykus.
* '''URL:''' [https://chat.ryzom.com https://chat.ryzom.com]
* '''Login:''' your character name
* '''Password:''' your account password
* '''Permissions by:''' [[User:Tamarea|Tamarea]] or [[User:Tykus|Tykus]]

==KanBoard (KB)==
KanBoard is a collaboration tool, a place where all team tasks supposed to be registered. There exists a lot of boards for various teams, projects and use. The general rule about tasks is that they travel from columns on left to columns on right as they progress. In case you miss access to any board you supposed to see please contact Tamarea.
* '''URL:''' [https://board.ryzom.com https://board.ryzom.com]
* '''Login:''' your account name
* '''Password:''' your account password
* '''Permissions by:''' [[User:Tamarea|Tamarea]]

==Ryzom cloud (Cloud)==
Ryzom cloud is a powerful tool for (not just) collaboration on documents. There are various folders and the visibility depends on your team or project membership as usually. You can work with various file types on the cloud, however for a team cooperation we use mostly Pads, a special type of document that highlights different contributors. In case you miss access to any part of the cloud please contact Tamarea. Some additional details about file formats used on the Ryzom cloud are described in [[File formats]] article <ref> You can read [[Tips for wiki contributors#With Ryzom cloud]] too. '''Caution''': the Document folder is for your personal files - no team can access it.</ref>.

There is a "[https://cloud.ryzom.com/f/1354 Ryzom-Team]" folder on the cloud that you should be able to access. You can find some useful documents for internal needs, sorted to several sub-folders.
* '''URL:''' [https://cloud.ryzom.com https://cloud.ryzom.com]
* '''Login:''' your account name
* '''Password:''' your account password
* '''Permissions by:''' [[User:Tamarea|Tamarea]]

==Ryzom Wiki==
Ryzom wiki is the main place for all documentation. It is not a tool you will probably need to use directly in your team, however it contains a lot of useful information about the game and its world. The Wiki is maintained by the Ryzom Wiki project. Viewing documents does not require any authentication, however you must have an account in case you wish to contribute. As a member of a Ryzom team consider your registration and updating your profile page <ref>More on [[:Category:Help]].</ref>.
* '''URL:''' [https://wiki.ryzom.com https://wiki.ryzom.com]
* '''Login:''' your character name
* '''Password:''' specific for the wiki
* '''Permissions by:''' [[User:Zorroargh|Zorroargh]]

More about wiki account creation on [[Help:Why create an account?]].

==Server status==
This small application is used to quick check the state of all three servers. There is no need to authenticate yourself and it is a passive too that displays what is running and what is not. Please remember that this tool is unable to cover wrong functionality of a component, it just tells you if it is running or not. In best case all icons on this page are green (thus everything is running).
* '''URL:''' [https://app.ryzom.com/app_server_status/ https://app.ryzom.com/app_server_status/]
* '''Login:''' not needed
* '''Password:''' not needed
* '''Permissions by:''' not needed

=As a member of the Test Team=
Here are some additional details for members of the Test team. In case you are lost or need a help, contact one of [[Test_Team#Coordinators|Test team coordinators]] on the team chat (see below).
==Ryzom chat (RC)==
You supposed to see [https://chat.ryzom.com/group/t-test #t-test] room by default and all discussion about testing supposed to go there, unless you need to interact with members from other teams. Feel free to ask about everything that is not clear, about your work in team, tools, a test details or your questions and issues that appeared during your testing. Feel free to suggest anything that will help run the team or fix any issue you have discovered.

==KanBoard (KB)==
You supposed to see "[https://board.ryzom.com/?controller=BoardViewController&action=show&project_id=51 [Team] Test]" board where all current or near-future tests have a place. The board is separated to various columns and tasks travel from left to right. However the most important for you are three of those columns:
* '''Testing on Yubo''', where a list of tasks to be tested on Yubo server is
* '''Testing on Gingo''', with a list of tasks that supposed to undertake final testing on Gingo server
* '''Testing on Atys''', where you can find tasks that need to be tested after it was released on Atys
You can comment each task as you wish, however remember please that each specific testing has a Testing PAD with instructions and all your testing reports should go there not to comments on the board. The link to a corresponding pad is usually attached to the task. More details about Test board organization is covered by [[The_Test_Team_Handbook/5_-_Test_board_organization|Test board organization]] chapter, more details about work for testers is described in [[Test_Team_roles#Testers|Test Team roles]]

==Ryzom cloud (Cloud)==
As a member of the Testing team you supposed to see the "[https://cloud.ryzom.com/f/1355 Test-Team]" folder. It contains various sub-folders however for the testing itself you need mostly "[https://cloud.ryzom.com/f/31392 1 - DEV_Yubo]", "[https://cloud.ryzom.com/f/31396 2 - TEST_Gingo]" and "[https://cloud.ryzom.com/f/34247 3 - LIVE_Atys]". All three folders are similar, one for each testing server and one for the Live server. All contain several other sub-folders:
* '''1 - Ongoing''' contains pads related to current opened testing
* '''2 - Minor issues''' contains pads from previous testing that contain issues to be discussed and solved
* '''3 - OK''' is a folder for recently finished testing
* '''4 - Archive''' is a place where all documents form testing will end after some time
Every existing testing task usually has a testing PAD that contains instructions about the test itself and is separated into several parts. Actual form of a Testing PAD is up to each Test Guide (a Coordinator who cares about the test), however there exists a [https://cloud.ryzom.com/f/34169 template], [https://cloud.ryzom.com/f/36218 self-describing example] and a [https://cloud.ryzom.com/f/36039 PAD with help] you can check.
Another important sub-folders are:
* [https://cloud.ryzom.com/f/32249 TT-Library] where you can find some useful documents related to the Test Team
* [https://cloud.ryzom.com/f/151402 Test related files] where you can store screenshots from your testing to link in a Testing PAD

{{Portal|Forge}}
[[Category:Test|Test team]]
[[Category:Testing Team]]
[[Category:Ryzom Team]]
[[Category:Test]]
[[Category:Tutorials]]

The Test Team Handbook/5 - Test board organization

2022-03-21T06:50:39Z

Ledania:

{{Trad
|DE =Das Test-Team-Handbuch/5 - Test-Board-Organisation|DEs=4
|EN =The Test Team Handbook/5 - Test board organization|ENs=0
|ES =The Test Team Handbook|ESs=5
|FR =The Test Team Handbook|FRs=5
|RU =The Test Team Handbook|RUs=5
|H =
|palette=Grey
}}
[[File:Test board scheme.png|thumb|alt=Test board organization scheme|Test board organization scheme]]
[[File:Test board diagram.png|thumb|alt=Test board process diagram|Test board process diagram]]
This document describes details how tasks on the Test team board are organized.

=Theory=
The board divides whole process into seven steps, with progress from left to right. Odd columns are meant for management and '''Non-Testers''' in the team. Every other column involves testing and is meant for '''Testers'''.

Every task starts in either '''Waiting for Yubo''', '''Waiting for Gingo''' or '''Waiting for Atys''' column. It determines on which server the testing is initially placed. If the task progress (pass all server testing) it moves to right to next server or to end its lifetime as completed in the '''Done''' column.

The task remains "on server" and undertake one or more Test rounds/sessions until the all known or newly discovered issues are solved. The board organization use five main settings to indicate task details to all team members no matter of the current role.
* column on the board - how is overall task progress
* task position in column - priority within the current column
* task colour - general state indication: new (yellow), ok (green), troubles (orange), WIP (grey)
* tag stickers - various additional symptoms of the task
* deadline - the latest date by which the task must be analyzed
 
 
[[File:Tteam task elements.png|center|alt=Test Team board elements description]]
 
<center>''Board task elements''</center>

=Board users=
The work in the Test team is based on team members roles. Based on your current role you have chosen, you pay attention to different parts of the board and operate on different task base. The team itself consists of different type of Ryzom team members, pure testers who look for a running test, translators who work on strings, wiki project members who document changes, marketing team members who wants news for public, event team members who prepare games or scenes and developers who maintain the code. All of them can be, basically, divided into two groups.
* Testing, members who look for opened testing and its details
* Management members who manage tasks between testing

Team members accept (use) different roles while working in the Test team. Your first step should be to tell yourself, what would you like to do with the board now. Based on that, you pay attention to different task details and different parts (columns) of the board:
*'''For Testing:'''
**Testing on Yubo (2nd)
**Testing on Gingo (4th)
**Testing on Atys (6th)
*'''For Management:'''
**Waiting for Yubo (1st)
**Waiting for Gingo (3rd)
**Waiting for Atys (5th)
**Done (7th)

After you open a desired task, based on your role you pay attention to different task details.
* For Testing, usually testers or translators performing a testing, look for latest Testing PAD. You will find there all details related to current running test.
* For Management, use task description/comments to provide task details, external links to add all related documents and sub-tasks to review and manage opened task issues.
Some more about work in the Test team by various roles is described in [[Test Team roles]] article.

=Columns (task progress)=
The theory is that a new testing task travels during its lifetime from left to right when progress and right to left when troublesome. After each testing round or session it is decided if the task is ready to progress (move right on the board) or if there is more work on it (move left on the board).

==Waiting for Yubo==
This column contains new or actually closed tasks that will continue with testing on the Yubo server. It is a place where:
* Yubo task management should be done here (yellow or orange colour)
* developers can create new tasks for the Testing team with target on Yubo server
* translators can review translation issues found during testing (low priority due early stage)
* where all tests with issues return after testing on Yubo is closed
Before such task can continue for new testing on Yubo, a new test must be prepared. That means that all issues must be solved, all patches applied and all problems discussed.

==Testing on Yubo==
This column contains all opened tests on the Yubo server. It is a place where:
* active testers from the Test team should look (green and orange colours)
* all currently opened tests on Yubo server are placed
* non-testers can optionally review running tests here to interact with testers on PAD base (orange colour)

==Waiting for Gingo==
This column contains new or actually closed tasks that will continue with testing on the Gingo server. It is a place where
* Gingo task management should be done here (yellow or orange colour)
* developers can create new tasks for the Testing team with target on Gingo server
* translators can review translation issues found during testing
* where all tests with issues return after testing on Gingo is closed
* where all successful tests on Yubo server come (yellow colour)
Before such task can continue for new testing on Gingo, a new test must be prepared. That means that all issues must be solved, all patches applied and all problems discussed.

==Testing on Gingo==
This column contains all opened tests on the Gingo or Atys BETA server. It is a place where:
* active testers from the Test team should look (green and orange colours)
* all currently opened tests on Gingo or Atys BETA servers are placed
* non-testers can optionally review running tests here to interact with testers on PAD base (orange colour)

==Waiting for Atys==
This column contains new or actually closed tasks that will continue with testing on the Atys server. It is a place where
* non-testers should do a management of tasks that belong to Atys (yellow or orange colour)
* developers can create new tasks for the Testing team with target on Atys server
* translators can review translation issues found during testing
* where all tests with issues return after testing on Atys is closed
* where all successful tests on Gingo server come
Before such task can continue for new testing on Atys, a new test must be prepared. That means that all issues must be solved, all patches applied and all problems discussed.

==Testing on Atys==
This column contains all opened tests on the Atys server. It is a place where:
* active testers from the Test team should look (green and orange colours)
* all currently opened tests on Atys server are placed
* all currently opened tests on beta Atys server are placed
* non-testers can optionally review running tests here to interact with testers on PAD base (orange colour)

==Done==
This is a column where every task come at the end of its lifetime. Once the parent task is adjusted, testing task can be closed.

=Colours (task state)=
[[File:Tteam task open.png|thumb|alt=Test Team board task opened for testing|Test Team board task opened for testing]]
[[File:Tteam task issues.png|thumb|alt=Test Team board task with known issues|Test Team board task with known issues]]
[[File:Tteam task new.png|thumb|alt=Test Team board task ready to be processed|Test Team board task ready to be processed]]
[[File:Tteam task wip.png|thumb|alt=Test Team board task being adjusted by a coordinator|Test Team board task being adjusted by a coordinator]]
Each task can have one of various colours. This setting represents its state:
* Green marks tasks that are running ok, mainly opened tests and tasks in Done column
** Colour for: Testing
* Orange marks troublesome tasks, running tests with confirmed issues or closed tests with any issues preventing progress
** Colour for: Testing, Management
* Yellow marks new tasks in column, needs to be processed
** Colour for: Management
* Grey is a colour for tasks someone is currently doing management on
** Colour for: Management

=Position (task priority in current column)=
Position of a task in each column tells you how important is a work on it. Higher position inside a column means higher task priority. Please ignore the task Priority settings. It belongs to team managers to set their priority. Optionally you can choose initial priority when the task arrives to new column to tell your priority guess, based on task progress, number and seriousness of issues, overall project priority...

=Tag stickers (task symptoms)=
Each task can have one or more stickers (tags) placed on. It represents main current task "symptoms".

==Colour scheme==
Tag stickers have coloured background to help you get oriented.
* Orange is for (confirmed) issues to solve
* Pink is for (confirmed) issues on Atys
* Purple is for (confirmed) translation issues
* Yellow is for questions
* Green is for running test

==Commonly used tags==
The list is dynamic so you can create any sticker you wish, however it is useful to have some standard list of those everyone should understand.
* '''⏳ patch''' (orange): this task requires a server patch before it can progress or be (re)tested
* '''Bugs reported''' (orange): represents tasks that have any unsolved confirmed issues
* '''Bugs reported on Atys''' (pink): represents tasks that have any unsolved confirmed issues
* '''Translation issue''' (purple): represents tasks that have any unsolved translation issues
* '''Test in progress''' (green): represents that a task testing is in progress
* '''Quick''' (green): represents those tasks that have undemanding testing, it should not consume more than 30 minutes of your time
* '''Clarify first''' (yellow): test details or some aspects of testing/change are not clear and needs to be clarified first before testing can continue
* '''Dev: XYZ''' (no colour): represents a developer who to ask for details or discuss issues

=Deadline (task deadline in current column)=
Applies to open tests only, otherwise ignore. The date and time represents when the test (round) will be closed on server. It is needed to have at least basic testing done completed due the date. Deadlines are important in case you need to prepare the change for upcoming patch or if some specific features will be activated for limited time (running events, bigger tests...).

{{Portal|Forge}}
[[Category:Test|Test team]]
[[Category:Tutorials|Test team]]
[[Category:Testing Team]]
[[Category:Ryzom Team]]
[[Category:Test]]
[[Category:Tutorials]]

The Test Team Handbook/5 - Test board organization

2022-03-21T06:01:13Z

Ledania:

{{Trad
|DE =Das Test-Team-Handbuch/5 - Test-Board-Organisation|DEs=3
|EN =The Test Team Handbook/5 - Test board organization|ENs=0
|ES =The Test Team Handbook|ESs=5
|FR =The Test Team Handbook|FRs=5
|RU =The Test Team Handbook|RUs=5
|H =
|palette=Grey
}}
[[File:Test board scheme.png|thumb|alt=Test board organization scheme|Test board organization scheme]]
[[File:Test board diagram.png|thumb|alt=Test board process diagram|Test board process diagram]]
This document describes details how tasks on the Test team board are organized.

=Theory=
The board divides whole process into seven steps, with progress from left to right. Odd columns are meant for management and '''Non-Testers''' in the team. Every other column involves testing and is meant for '''Testers'''.

Every task starts in either '''Waiting for Yubo''', '''Waiting for Gingo''' or '''Waiting for Atys''' column. It determines on which server the testing is initially placed. If the task progress (pass all server testing) it moves to right to next server or to end its lifetime as completed in the '''Done''' column.

The task remains "on server" and undertake one or more Test rounds/sessions until the all known or newly discovered issues are solved. The board organization use five main settings to indicate task details to all team members no matter of the current role.
* column on the board - how is overall task progress
* task position in column - priority within the current column
* task colour - general state indication: new (yellow), ok (green), troubles (orange), WIP (grey)
* tag stickers - various additional symptoms of the task
* deadline - the latest date by which the task must be analyzed
 
 
[[File:Tteam task elements.png|center|alt=Test Team board elements description]]
 
<center>''Board task elements''</center>

=Board users=
The work in the Test team is based on team members roles. Based on your current role you have chosen, you pay attention to different parts of the board and operate on different task base. The team itself consists of different type of Ryzom team members, pure testers who look for a running test, translators who work on strings, wiki project members who document changes, marketing team members who wants news for public, event team members who prepare games or scenes and developers who maintain the code. All of them can be, basically, divided into two groups.
* Testing, members who look for opened testing and its details
* Management members who manage tasks between testing

Team members accept (use) different roles while working in the Test team. Your first step should be to tell yourself, what would you like to do with the board now. Based on that, you pay attention to different task details and different parts (columns) of the board:
*'''For Testing:'''
**Testing on Yubo (2nd)
**Testing on Gingo (4th)
**Testing on Atys (6th)
*'''For Management:'''
**Waiting for Yubo (1st)
**Waiting for Gingo (3rd)
**Waiting for Atys (5th)
**Done (7th)

After you open a desired task, based on your role you pay attention to different task details.
* For Testing, usually testers or translators performing a testing, look for latest Testing PAD. You will find there all details related to current running test.
* For Management, use task description/comments to provide task details, external links to add all related documents and sub-tasks to review and manage opened task issues.
Some more about work in the Test team by various roles is described in [[Test Team roles]] article.

=Columns (task progress)=
The theory is that a new testing task travels during its lifetime from left to right when progress and right to left when troublesome. After each testing round or session it is decided if the task is ready to progress (move right on the board) or if there is more work on it (move left on the board).

==Waiting for Yubo==
This column contains new or actually closed tasks that will continue with testing on the Yubo server. It is a place where:
* Yubo task management should be done here (yellow or orange colour)
* developers can create new tasks for the Testing team with target on Yubo server
* translators can review translation issues found during testing (low priority due early stage)
* where all tests with issues return after testing on Yubo is closed
Before such task can continue for new testing on Yubo, a new test must be prepared. That means that all issues must be solved, all patches applied and all problems discussed.

==Testing on Yubo==
This column contains all opened tests on the Yubo server. It is a place where:
* active testers from the Test team should look (green and orange colours)
* all currently opened tests on Yubo server are placed
* non-testers can optionally review running tests here to interact with testers on PAD base (orange colour)

==Waiting for Gingo==
This column contains new or actually closed tasks that will continue with testing on the Gingo server. It is a place where
* Gingo task management should be done here (yellow or orange colour)
* developers can create new tasks for the Testing team with target on Gingo server
* translators can review translation issues found during testing
* where all tests with issues return after testing on Gingo is closed
* where all successful tests on Yubo server come (yellow colour)
Before such task can continue for new testing on Gingo, a new test must be prepared. That means that all issues must be solved, all patches applied and all problems discussed.

==Testing on Gingo==
This column contains all opened tests on the Gingo or Atys BETA server. It is a place where:
* active testers from the Test team should look (green and orange colours)
* all currently opened tests on Gingo or Atys BETA servers are placed
* non-testers can optionally review running tests here to interact with testers on PAD base (orange colour)

==Waiting for Atys==
This column contains new or actually closed tasks that will continue with testing on the Atys server. It is a place where
* non-testers should do a management of tasks that belong to Atys (yellow or orange colour)
* developers can create new tasks for the Testing team with target on Atys server
* translators can review translation issues found during testing
* where all tests with issues return after testing on Atys is closed
* where all successful tests on Gingo server come
Before such task can continue for new testing on Atys, a new test must be prepared. That means that all issues must be solved, all patches applied and all problems discussed.

==Testing on Atys==
This column contains all opened tests on the Atys server. It is a place where:
* active testers from the Test team should look (green and orange colours)
* all currently opened tests on Atys server are placed
* all currently opened tests on beta Atys server are placed
* non-testers can optionally review running tests here to interact with testers on PAD base (orange colour)

==Done==
This is a column where every task come at the end of its lifetime. Once the parent task is adjusted, testing task can be closed.

=Colours (task state)=
[[File:Tteam task open.png|thumb|alt=Test Team board task opened for testing|Test Team board task opened for testing]]
[[File:Tteam task issues.png|thumb|alt=Test Team board task with known issues|Test Team board task with known issues]]
[[File:Tteam task new.png|thumb|alt=Test Team board task ready to be processed|Test Team board task ready to be processed]]
[[File:Tteam task wip.png|thumb|alt=Test Team board task being adjusted by a coordinator|Test Team board task being adjusted by a coordinator]]
Each task can have one of various colours. This setting represents its state:
* Green marks tasks that are running ok, mainly opened tests and tasks in Done column
** Colour for: Testing
* Orange marks troublesome tasks, running tests with confirmed issues or closed tests with any issues preventing progress
** Colour for: Testing, Management
* Yellow marks new tasks in column, needs to be processed
** Colour for: Management
* Grey is a colour for tasks someone is currently doing management on
** Colour for: Management

=Position (task priority in current column)=
Position of a task in each column tells you how important is a work on it. Higher position inside a column means higher task priority. Please ignore the task Priority settings. It belongs to team managers to set their priority. Optionally you can choose initial priority when the task arrives to new column to tell your priority guess, based on task progress, number and seriousness of issues, overall project priority...

=Tag stickers (task symptoms)=
Each task can have one or more stickers (tags) placed on. It represents main current task "symptoms".

==Colour scheme==
Tag stickers have coloured background to help you get oriented.
* Orange is for (confirmed) issues to solve
* Pink is for (confirmed) issues on Atys
* Purple is for (confirmed) translation issues
* Yellow is for questions
* Green is for running test

==Commonly used tags==
The list is dynamic so you can create any sticker you wish, however it is useful to have some standard list of those everyone should understand.
* '''⏳ patch''' (orange): this task requires a server patch before it can progress or be (re)tested
* '''Bugs reported''' (orange): represents tasks that have any unsolved confirmed issues
* '''Bugs reported on Atys''' (pink): represents tasks that have any unsolved confirmed issues
* '''Translation issue''' (purple): represents tasks that have any unsolved translation issues
* '''Test in progress''' (green): represents that a task testing is in progress
* '''Quick''' (green): represents those tasks that have undemanding testing, it should not consume more than 30 minutes of your time
* '''Clarify first''' (yellow): test details or some aspects of testing/change are not clear and needs to be clarified first before testing can continue
* '''Dev: XYZ''' (no colour): represents a developer who to ask for details or discuss issues

=Deadline (task deadline in current column)=
Applies to open tests only, otherwise ignore. The date and time represents when the test (round) will be closed on server. It is needed to have at least basic testing done completed due the date. Deadlines are important in case you need to prepare the change for upcoming patch or if some specific features will be activated for limited time (running events, bigger tests...).

{{Portal|Forge}}
[[Category:Test|Test team]]
[[Category:Tutorials|Test team]]
[[Category:Testing Team]]
[[Category:Ryzom Team]]
[[Category:Test]]
[[Category:Tutorials]]

File formats

2022-03-21T05:56:18Z

Ledania:

{{Trad|DE=Dateiformate|EN=File formats|FR=Format de fichiers}}

We will talk about file types (how to open which file with which program) as well as when to use which tool...

== Ryzom Files ==
See [[Ryzom location]] (for now in French only [[:fr:Manuel de l'utilisateur/Ch 1 - Dossiers et fichiers de Ryzom]]) lists all important folder and file locations, for all operating systems (Windows, GNU/Linus and Mac and with or without Steam).

A good number of files in the game are in xml format. It's better to save them (copy and paste under another name) ''before'' modifying them because some of them, in case of error, will prevent the game from loading.

== Common Formats ==
Ryzom is a sandbox, part of whose code is said to be [https://en.wikipedia.org/wiki/Open-source_model Open Source], see [https://www.fsf.org/blogs/licensing/ryzom-free-software Ryzom on fsf.org].

We prefer "free" formats and tools (see [https://en.wikipedia.org/wiki/Open_format Open Format] and [https://en.wikipedia.org/wiki/Proprietary_format Proprietary Format]) as soon as possible.

=== The .xml ===
All the ''basic'' editors <ref>like notepad, vim, edit... Word processors (such as MicroSoft Word, Office etc.) very often pollute simple text files with their proprietary codes. See https://en.wikipedia.org/wiki/Text_editor</ref> open them (without polluting them).

More at https://en.wikipedia.org/wiki/XML

=== The .pads ===
Ideal for working together on a text. 
A "pad" is an online collaborative text editor (there are also spreadsheet-type files). Each user's contributions are colour-coded, appear on the screen in real time and are recorded as they are typed.

'''Comparison with a wiki page:''' if 2 wiki contributors work on the same wiki page at the same time, the last one who saves the page overwrites the content of the other one <ref> See also ''versioning conflict'' at [[Wiki Technical Guide#Editing War]] and/or https://en.wikipedia.org/wiki/Help:Edit_conflict</ref>. To correct a mistake, it is therefore better to edit a section (via the edit to the right of the title) rather than edit the whole page (via the top toolbar).

To ''use a pad'':
# the first thing to do is to choose the color and indicate its name (top right)
# ''Caution:'' Veru often free PADS have a limited time (one month, one semester etc). Therefore it is useful to indicate the creation and end date roughly at the beginning. You can also export the pad to make a backup.

More at https://framapad.org/en/ (free and free pads) and https://en.wikipedia.org/wiki/Portable_Application_Description.

Free provider at https://degooglisons-internet.org/en/list/ with e.g:
* their pad at https://framapad.org/en/
* spreadsheet at https://accueil.framacalc.org/en/ (end Monday, July 6, 2020)

==== the NC Wiki pads ====
Bureaucrats who have access to NC Ryzom (the cloud dedicated to the Wiki project) must connect to it not with their personal name but with their account name.

To create a pad, click on the + icon at the top center of the screen.
[[File:FR NC add pad 2019-06-14.png|vignette]]

=== The .ods and other OpenDocument ===
OpenDocument is an open data format for office applications: word processing, spreadsheets, presentations, diagrams, drawings and office databases. OpenDocument is the usage designation of a standard published by OASIS and whose official name is Open Document Format for Office Applications, also abbreviated as ODF.

In France, the OpenDocument format is the only format recommended as an office automation format by the Référentiel général d'interopérabilité since its version 2.0 validated on April 20, 2016.

=== The Markdown .md ===
*KB (the official task manager on the Ryzom Cloud) use Markdown's format (task summary),
*With NC (Ryzom Cloud) you can create .txt in .md to benefit under a basic editor of a minimal colouring helping the formatting.
* The [[RC]] syntax is very close of Markdown

More on https://en.wikipedia.org/wiki/Markdown

For those who have access to NC: choose Text File, and name it '''.md'''.

===Mind map ===
On the cloud, with .km

To understand the idea: https://en.wikipedia.org/wiki/Mind_map and https://framapad.org/en/

==Notes and Links ==
On this wiki, [[Tips for wiki contributors]] presents various tips for working on wikis (firefox tips for managing tabs, RSS for tracking changes, using Ryzom Cloud...).

----------------------------------------------------------------------------
<references/>
{{clear}}{{Last version link}}
<noinclude>{{Portal|Wikipatys|}}
[[Category:Help]]
[[Category: Trash]] [[Category:Support]]
</noinclude>

The Test Team Handbook/2 - External team tools

2022-03-21T05:06:51Z

Ledania:

{{Trad
|DE =Das Test-Team-Handbuch/2 - Externe Teamwerkzeuge|DEs=3
|EN =The Test Team Handbook/2 - External team tools|ENs=0
|ES =The Test Team Handbook|ESs=5
|FR =The Test Team Handbook|FRs=5
|RU =The Test Team Handbook|RUs=5
|H =
|palette=Grey
}}
This document shortly describes external tools that are useful for every team member. These tools are not working in-game or just in a very limited way and you need to use external browser. The goal is not to supply any user manual just give you a basic overview about what do we use, how it could be useful and how to log in. The second part of this document is focused on members of the Test team.

=General information=
Here is a basic description of all important external tools that you should keep in mind and use.
==Ryzom chat (RC)==
You probably know the Ryzom chat already. It is a tool that allows you to read in-game chats without a need to be actually in game. You will have "~" (tilde) prefix in front of your name in case of every message sent from RC to the game. Some additional details about Ryzom chat are described in the [[Chat/RC_FAQ|RC FAQ article]].

Another important role of the Ryzom chat is also that each team or project have own private chat room available. Team chat rooms have a "t-" prefix and project chat rooms have "pj-" prefix. By default every team member supposed be member of all following rooms:
* [https://chat.ryzom.com/group/announcements #announcement]
* [https://chat.ryzom.com/group/chat-general #chat-general]
* [https://chat.ryzom.com/group/chat-ark_dev #chat-ark_dev]
Internal chat rooms are not public thus you must become a member of a team/project first to see other private rooms then default ones. In all cases if you think you have lost or didn't get access to a specific channel you should be presented on (including default ones) please contact Tamarea or Tykus.
* '''URL:''' [https://chat.ryzom.com https://chat.ryzom.com]
* '''Login:''' your character name
* '''Password:''' your account password
* '''Permissions by:''' [[User:Tamarea|Tamarea]] or [[User:Tykus|Tykus]]

==KanBoard (KB)==
KanBoard is a collaboration tool, a place where all team tasks supposed to be registered. There exists a lot of boards for various teams, projects and use. The general rule about tasks is that they travel from columns on left to columns on right as they progress. In case you miss access to any board you supposed to see please contact Tamarea.
* '''URL:''' [https://board.ryzom.com https://board.ryzom.com]
* '''Login:''' your account name
* '''Password:''' your account password
* '''Permissions by:''' [[User:Tamarea|Tamarea]]

==Ryzom cloud (Cloud)==
Ryzom cloud is a powerful tool for (not just) collaboration on documents. There are various folders and the visibility depends on your team or project membership as usually. You can work with various file types on the cloud, however for a team cooperation we use mostly Pads, a special type of document that highlights different contributors. In case you miss access to any part of the cloud please contact Tamarea. Some additional details about file formats used on the Ryzom cloud are described in [[File formats]] article <ref> You can read [[Tips for wiki contributors#With Ryzom cloud]] too. '''Caution''': the Document folder is for your personal files - no team can access it.</ref>.

There is a "[https://cloud.ryzom.com/f/1354 Ryzom-Team]" folder on the cloud that you should be able to access. You can find some useful documents for internal needs, sorted to several sub-folders.
* '''URL:''' [https://cloud.ryzom.com https://cloud.ryzom.com]
* '''Login:''' your account name
* '''Password:''' your account password
* '''Permissions by:''' [[User:Tamarea|Tamarea]]

==Ryzom Wiki==
Ryzom wiki is the main place for all documentation. It is not a tool you will probably need to use directly in your team, however it contains a lot of useful information about the game and its world. The Wiki is maintained by the Ryzom Wiki project. Viewing documents does not require any authentication, however you must have an account in case you wish to contribute. As a member of a Ryzom team consider your registration and updating your profile page <ref>More on [[:Category:Help]].</ref>.
* '''URL:''' [https://wiki.ryzom.com https://wiki.ryzom.com]
* '''Login:''' your character name
* '''Password:''' specific for the wiki
* '''Permissions by:''' [[User:Zorroargh|Zorroargh]]

More about wiki account creation on [[Help:Why create an account?]].

==Server status==
This small application is used to quick check the state of all three servers. There is no need to authenticate yourself and it is a passive too that displays what is running and what is not. Please remember that this tool is unable to cover wrong functionality of a component, it just tells you if it is running or not. In best case all icons on this page are green (thus everything is running).
* '''URL:''' [https://app.ryzom.com/app_server_status/ https://app.ryzom.com/app_server_status/]
* '''Login:''' not needed
* '''Password:''' not needed
* '''Permissions by:''' not needed

=As a member of the Test Team=
Here are some additional details for members of the Test team. In case you are lost or need a help, contact one of [[Test_Team#Coordinators|Test team coordinators]] on the team chat (see below).
==Ryzom chat (RC)==
You supposed to see [https://chat.ryzom.com/group/t-test #t-test] room by default and all discussion about testing supposed to go there, unless you need to interact with members from other teams. Feel free to ask about everything that is not clear, about your work in team, tools, a test details or your questions and issues that appeared during your testing. Feel free to suggest anything that will help run the team or fix any issue you have discovered.

==KanBoard (KB)==
You supposed to see "[https://board.ryzom.com/?controller=BoardViewController&action=show&project_id=51 [Team] Test]" board where all current or near-future tests have a place. The board is separated to various columns and tasks travel from left to right. However the most important for you are three of those columns:
* '''Testing on Yubo''', where a list of tasks to be tested on Yubo server is
* '''Testing on Gingo''', with a list of tasks that supposed to undertake final testing on Gingo server
* '''Testing on Atys''', where you can find tasks that need to be tested after it was released on Atys
You can comment each task as you wish, however remember please that each specific testing has a Testing PAD with instructions and all your testing reports should go there not to comments on the board. The link to a corresponding pad is usually attached to the task. More details about Test board organization is covered by [[The_Test_Team_Handbook/5_-_Test_board_organization|Test board organization]] chapter, more details about work for testers is described in [[Test_Team_roles#Testers|Test Team roles]]

==Ryzom cloud (Cloud)==
As a member of the Testing team you supposed to see the "[https://cloud.ryzom.com/f/1355 Test-Team]" folder. It contains various sub-folders however for the testing itself you need mostly "[https://cloud.ryzom.com/f/31392 1 - DEV_Yubo]", "[https://cloud.ryzom.com/f/31396 2 - TEST_Gingo]" and "[https://cloud.ryzom.com/f/34247 3 - LIVE_Atys]". All three folders are similar, one for each testing server and one for the Live server. All contain several other sub-folders:
* '''1 - Ongoing''' contains pads related to current opened testing
* '''2 - Minor issues''' contains pads from previous testing that contain issues to be discussed and solved
* '''3 - OK''' is a folder for recently finished testing
* '''4 - Archive''' is a place where all documents form testing will end after some time
Every existing testing task usually has a testing PAD that contains instructions about the test itself and is separated into several parts. Actual form of a Testing PAD is up to each Test Guide (a Coordinator who cares about the test), however there exists a [https://cloud.ryzom.com/f/34169 template], [https://cloud.ryzom.com/f/36218 self-describing example] and a [https://cloud.ryzom.com/f/36039 PAD with help] you can check.
Another important sub-folders are:
* [https://cloud.ryzom.com/f/32249 TT-Library] where you can find some useful documents related to the Test Team
* [https://cloud.ryzom.com/f/151402 Test related files] where you can store screenshots from your testing to link in a Testing PAD

{{Portal|Forge}}
[[Category:Test|Test team]]
[[Category:Testing Team]]
[[Category:Ryzom Team]]
[[Category:Test]]
[[Category:Tutorials]]

The Test Team Handbook/1 - Get in touch with Ryzom Forge

2022-03-21T04:49:16Z

Ledania:

{{Trad
|DE =Das Test-Team-Handbuch/1 - Kontaktaufnahme mit Ryzom Forge|DEs=3
|EN =The Test Team Handbook/1 - Get in touch with Ryzom Forge|ENs=0
|ES =The Test Team Handbook|ESs=5
|FR =The Test Team Handbook|FRs=5
|RU =The Test Team Handbook|RUs=5
|H =
|palette=Grey
}}
This document attempts to give you basic information about Ryzom Forge, periodical meetings and how you can join.
[[File:Rf_meeting_HOME.png|thumb|right|alt=Elements related to Forge meeting on HOME|Elements related to Forge meeting on HOME]]

=What is Ryzom Forge?=
[[portal:Forge|Ryzom Forge]] is a collaborative project with goal to get Ryzom players involved in. It consists of many teams and projects focused on different aspects of the Ryzom development and is also ment to be a bridge between Ryzom itself, [http://ryzomcore.com/ Ryzom Core] and [https://khaganat.net/ Khaganat project].

=What is Ryzom Forge meeting?=
While team chat rooms are private for members of a team or a project, Ryzom Forge meetings are, along the [https://app.ryzom.com/app_forum/index.php?lang=en Forum], the way how can team members meet and discuss with regular players. It is a medium to publish hot news about the Ryzom Forge like upcoming changes or events and also directly answer player questions.

=Visit the meeting=
Ryzom Forge meetings are held on the [https://chat.ryzom.com/channel/pub-forge #pub-forge] channel usually twice a month and you can follow it from Ryzom Chat. If you want o visit the meeting in-game, open WebIG HOME by pressing '''Shift+W''' and click blue RF icon by languages in top-right corner. The meeting usually takes 2-3 hours and its start is announced via [https://chat.ryzom.com/channel/pub-announcements #pub-announcements] channel which is connected directly to the game.

<div style="color:red;font-weight:bold;"><nowiki>
Important note:
</nowiki></div>
<div style="color:red;"><nowiki>
At this moment you need to join the channel in-game first or it will disappear from the Ryzom Chat every time you re-log there. However it is possible to find the channel manually.
</nowiki></div>

The date and time of upcoming meetings are published in the main calendar along other events. Press '''Shift+W''' in-game or visit [https://app.ryzom.com/ App.Ryzom.com] to see the schedule. The meeting is scheduled with respect to the highest player base activity. For those who are unable to join due to unsuitable time there is always composed a meeting report that is [https://app.ryzom.com/app_forum/index.php?page=topic/view/28116 published on the Forum] some time after the meeting itself. Between meetings any free discussion is allowed, however '''once the meeting start''', you should accept following rules until its end:
==Rise your hand and wait for the floor before you speak==
To prevent the meeting getting out of order, please rise your hand and then wait your turn. Remember, that it helps the person who translate you to other language and also the one who is composing the meeting report. Another important reason is that you questions might be overlooked when everyone talks together.

==Stick with the current topic==
The meeting agenda is published at the beginning of each meeting. If you have a question or a topic that does not fit any of current topics, ask before or at the end of the meeting to incorporate it. It also helps the person who is composing the meeting report.

==Speak clearly and wait for translations==
All meetings are held in english as well as in french. There is usually a volunteer who translates between these languages. Try to help him or her, use simple expressions and make a short pause after each sentence or paragraph waiting for translation.

=Apply to join=
If you are interested in joing any team other than Support or Event (where your anonymity is important) and help to develop the Ryzom, you can apply directly during any meeting. The last agenda topic is usually dedicated to recruitment of new members. We publish there positions we do look volunteers for, however every help to every team is welcome. Do not hesitate to apply to any Ryzom Forge team.
Your other option (the only one if you apply for Support or Event team) is to contact [[User:Tamarea|Tamarea]], the communication manager, directly. You can reach her with [https://chat.ryzom.com/direct/Tamarea direct message on Ryzom Chat] or send an e-mail to [mailto:tamarea@ryzom.com tamarea@ryzom.com].

{{Portal|Forge}}
[[Category:Test|Test team]]
[[Category:Tutorials|Test team]]
[[Category:Testing Team]]
[[Category:Ryzom Team]]
[[Category:Test]]
[[Category:Tutorials]]

The Test Team Handbook/1 - Get in touch with Ryzom Forge

2022-03-21T04:47:43Z

Ledania:

{{Trad
|DE =The Test Team Handbook|DEs=3
|EN =The Test Team Handbook|ENs=0
|ES =The Test Team Handbook|ESs=5
|FR =The Test Team Handbook|FRs=5
|RU =The Test Team Handbook|RUs=5
|H =
|palette=Grey
}}
This document attempts to give you basic information about Ryzom Forge, periodical meetings and how you can join.
[[File:Rf_meeting_HOME.png|thumb|right|alt=Elements related to Forge meeting on HOME|Elements related to Forge meeting on HOME]]

=What is Ryzom Forge?=
[[portal:Forge|Ryzom Forge]] is a collaborative project with goal to get Ryzom players involved in. It consists of many teams and projects focused on different aspects of the Ryzom development and is also ment to be a bridge between Ryzom itself, [http://ryzomcore.com/ Ryzom Core] and [https://khaganat.net/ Khaganat project].

=What is Ryzom Forge meeting?=
While team chat rooms are private for members of a team or a project, Ryzom Forge meetings are, along the [https://app.ryzom.com/app_forum/index.php?lang=en Forum], the way how can team members meet and discuss with regular players. It is a medium to publish hot news about the Ryzom Forge like upcoming changes or events and also directly answer player questions.

=Visit the meeting=
Ryzom Forge meetings are held on the [https://chat.ryzom.com/channel/pub-forge #pub-forge] channel usually twice a month and you can follow it from Ryzom Chat. If you want o visit the meeting in-game, open WebIG HOME by pressing '''Shift+W''' and click blue RF icon by languages in top-right corner. The meeting usually takes 2-3 hours and its start is announced via [https://chat.ryzom.com/channel/pub-announcements #pub-announcements] channel which is connected directly to the game.

<div style="color:red;font-weight:bold;"><nowiki>
Important note:
</nowiki></div>
<div style="color:red;"><nowiki>
At this moment you need to join the channel in-game first or it will disappear from the Ryzom Chat every time you re-log there. However it is possible to find the channel manually.
</nowiki></div>

The date and time of upcoming meetings are published in the main calendar along other events. Press '''Shift+W''' in-game or visit [https://app.ryzom.com/ App.Ryzom.com] to see the schedule. The meeting is scheduled with respect to the highest player base activity. For those who are unable to join due to unsuitable time there is always composed a meeting report that is [https://app.ryzom.com/app_forum/index.php?page=topic/view/28116 published on the Forum] some time after the meeting itself. Between meetings any free discussion is allowed, however '''once the meeting start''', you should accept following rules until its end:
==Rise your hand and wait for the floor before you speak==
To prevent the meeting getting out of order, please rise your hand and then wait your turn. Remember, that it helps the person who translate you to other language and also the one who is composing the meeting report. Another important reason is that you questions might be overlooked when everyone talks together.

==Stick with the current topic==
The meeting agenda is published at the beginning of each meeting. If you have a question or a topic that does not fit any of current topics, ask before or at the end of the meeting to incorporate it. It also helps the person who is composing the meeting report.

==Speak clearly and wait for translations==
All meetings are held in english as well as in french. There is usually a volunteer who translates between these languages. Try to help him or her, use simple expressions and make a short pause after each sentence or paragraph waiting for translation.

=Apply to join=
If you are interested in joing any team other than Support or Event (where your anonymity is important) and help to develop the Ryzom, you can apply directly during any meeting. The last agenda topic is usually dedicated to recruitment of new members. We publish there positions we do look volunteers for, however every help to every team is welcome. Do not hesitate to apply to any Ryzom Forge team.
Your other option (the only one if you apply for Support or Event team) is to contact [[User:Tamarea|Tamarea]], the communication manager, directly. You can reach her with [https://chat.ryzom.com/direct/Tamarea direct message on Ryzom Chat] or send an e-mail to [mailto:tamarea@ryzom.com tamarea@ryzom.com].

{{Portal|Forge}}
[[Category:Test|Test team]]
[[Category:Tutorials|Test team]]
[[Category:Testing Team]]
[[Category:Ryzom Team]]
[[Category:Test]]
[[Category:Tutorials]]

Test Team roles

2022-03-20T05:38:42Z

Ledania:

<noinclude>{{WIP}}{{Trad|DE=Rollen des Test-Teams|EN=Test Team roles|H=1}}</noinclude>
The team is using the system of roles. It means that, based on your abilities and will, you can occupy various roles in the team. This system tries to join abilities of all team members.

=Theory=
Besides testers themselves, the [[Test Team]] also consists of many members who participate in other Ryzom teams. This and the matter of the team work makes it a place where a cooperation is highly needed. Most of team members are however volunteers and it would be unproductive to stick each member with only one position. That is the reason why we use a system of roles.

* [[#Coordinators|Coordinators]], who coordinate the team
* [[#Testers|Testers]], who perform all testing
* [[#Developers|Developers]], who fix discovered issues
* [[#Translators|Translators]], who fix discovered translation issues
* [[#Encyclopatysts_and_Marketing_team|Encyclopatysts and Marketing team]], who document changes and publish news
* [[#Artists.2C_designers_and_lorists|Artists, designers and lorists]], who fix discovered visual issues and provide background information

Each team member can temporarily act in any role he or she want, in case he meets its requirements, and his or her work emerge from the current role. This also means that different roles focus on different tasks and information. Roles are not permanent and you can switch it any time you want. It is not needed to tell others what role do you actually act in, make your decision and do what is needed. This might be a little confusing, that is why following chapters give you basic overview about tasks of each role.

=Testers=
This chapter describes how to start with a new testing from a tester's perspective. It is expected that you have [[The_Test_Team_Handbook/3_-_Setting_up_connection_to_non-public_Ryzom_servers|set up testing servers]] already (for testing on Yubo ang Gingo) and that you are a bit [[The_Test_Team_Handbook/4_-_On_a_testing_server|familiar with working on testing servers]]. Your work will mainly include:
* Participating on currently opened tests
* Re-testing issues reported by players or other Ryzom team members
* Testing for other Ryzom team members on-demand

While re-testing reported issues requires you own effort and testing on-demand is initiated by other member, regular testing starts on the [[The_Test_Team_Handbook/5_-_Test_board_organization|[Team] Test board]] on the Kan Board. There you can find all active tasks of the team. Following steps will help you to find a test you can do.

==Choose a server==
There are three columns where to look for a test you can do.
* '''Testing on Yubo''' for tests situated on the developers server
* '''Testing on Gingo''' for tests situated on the testing server
* '''Testing on Atys''' for tests opened for live server.
Choose one column and your testing will be placed on corresponding server.

==Choose a task==
Review tasks in the selected column. Priority is set by its position, so tasks on top are more important than those at bottom. Task colour indicates its state, if it is green, the test is running. In case there are some issues discovered already, the task is orange and you should know that the testing round might be closed soon. Find a task that you want to try and open it by clicking.

==Start working==
When you open a task details there is a lot of component and features that are not necessary to perform a test. You should however pay attention to:
* '''Description''' where you can find some overall details
* '''External links''' where you will find links to Testing PAD and other related external documents
* '''Comments''' where some additional task details might be placed
Most of testing tasks contain link to one or more Testing PADs, usually called as ''PAD (<server_name>)'' and listed in '''External links''' section. Find a PAD corresponding to the chosen server and open it. It includes all necessary details and all your reports will go to that Testing PAD. The actual form of the Testing PAD is fully up to the Test Guide. All PADs from previous testing are linked here as ''Archive PAD <date> (<server name>)'' and every newer PAD replaces previous document including all issues opened by that time. Some help with Testing PAD organization can be found in the [https://cloud.ryzom.com/f/36039 PAD help document] or look at self-describing [https://cloud.ryzom.com/f/36218 example PAD].

Please read [[The_Test_Team_Handbook/6_-_Testing_report_tips|Testing report tips]] to know more about what a tester's work covers.

===Tasks without a PAD===
Some minor tests might not have own testing PAD. In that case the task description should contain all necessary details and you put your testing report into the task Comments.

=Developers=
This chapter describes details useful for developers who would like to work on fixing found issues or unblocking testing tasks. In case you need the Test team to perform new testing, follow the [[How to request new testing]] article please. You need to be a [[Development_Team|Ryzom]] / [http://www.ryzomcore.com/ Ryzom Core] / [[Forge_Portal/Projects|Ryzom project]] developer (for example [[ARK]] team) or a member of either the [[Animation team|Animation]] or the [[Event team]]. Your main work in the team includes:
* Request new tests
* Provide testing tools and necessary details
* Solve known issues

==Choose a server==
First you need to choose a server you will work with. Tasks that being prepared for testing on a server are stored in columns on left to server one. '''Waiting for Yubo''' column contains tasks that will continue to testing on server Yubo, '''Waiting for Gingo''' being solved on Gingo server and '''Waiting for Atys''' are going to be (re)tested on Atys.

==Choose a task==
There are two types of board columns you should focus on:
===Non-Tester columns===
'''Blocked for Yubo''', '''Blocked for Gingo''' and '''Blocked for Atys'''. Here are new and troublesome tasks stored and those tasks are not in active testing at the moment. All such tasks are usually yellow (new) or orange (troublesome). Look for tasks with one of following tags on:
* '''⏳ patch''', orange tag, a task that needs to be patched to server first, to enable latest changes and fixes
* '''Clarify first''', yellow tag, for tasks that requires a discussion or more details
* '''Bugs reported''', orange tag, a task with reported issues to be fixed
* '''Bugs reported on Atys''', pink tag, a task with reported issues on Live server to be fixed

===Tester columns===
'''Testing on Yubo''', '''Testing on Gingo''' and '''Testing on Atys'''. All tasks here are currently in the testing. Look for tasks with orange '''Bugs reported''' tag on. Remember that in this case you affect actually running test, be careful and cooperative. Once you find a suitable task, open its details.

==Start working==
When you open a task details there is a lot of component and features that are not necessary for work of a developer. You should however pay attention to
* '''Description''' where you can find some overal details
* '''External links''' where you will find links to other related external documents
* '''Comments''' where some additional task details might be placed
In case the task is not being currently tested, all known issues should be listed as sub-tasks. Assign the sub-task in case you wish to start working on it.

===Tasks with a PAD===
Review current reports and issues in the appropriate Testing PAD (link to be found in External links section). Research a possibility to fix or clarify each reported issue and leave a note in the PAD (along with date and time) once there is any change you perform or you know about (fix, change, additional related details...). Do not mark issues as fixed, wait testers to confirm the fix. Some help with Testing PAD organization can be found in the [https://cloud.ryzom.com/f/36039 PAD help document] or look at self-describing [https://cloud.ryzom.com/f/36218 example PAD].

===Tasks without a PAD===
Some minor tests might not have own testing PAD. Research a possibility to fix or clarify each reported issue and leave a comment about any change you perform (fix, change or additional related details you know). Wait testers to confirm the fix.

=Translators=
Following chapter describes how can members of the Translation team get involved in testing and help solve translation issues. Translators can find a work in almost all parts of the testing process, however more right the task is placed on the board, more complete the change is. It is not common, but members of the Translation team can also request the Test team to perform a testing focused on translations, to look for missing strings or any string related issues like text over-floating and incorrectly encoded strings. In such case please read [[How to request new testing]] article. You need to be a member of the [[Translation|Translation team]] to act in this role. Your work is based on discovered translation issues and will mainly include:
* Fixing known translation issues
* Help testers
* Confirmation

==Choose a server==
First you need to choose a server. There is usually not much to do on Yubo while changes are in early stages there and it can significantly change before it is fully developed and used strings are final. Your best options are to focus on Gingo, where a testing before release is done or Atys where we hunt for missing or wrong translations.

==Choose a task==
Depending on target of your work, you focus on different board columns:

===Management columns, Blocked for Gingo and Blocked for Atys===
Here are new and troublesome tasks stored and those tasks are not in active testing at the moment. Look for tasks with purple Translation issue tag. You can help by fixing wrong or missing translations or by investigating why it is not possible to fix the translation.

===Testing columns, Testing on Gingo and Testing on Atys===
All tasks here are currently running a test. Look for tasks with purple Translation issue tag. You can help by taking care of newly discovered translation issues and giving support to testers in related questions. Some tasks also needs to verify translation issues on Atys. Remember that in this case you affect actually running test, be careful and cooperative. Do all your reports into the latest PAD and remember to mention date and time.

==Start working==
Each task supposed to have a minor issue subt-ask you can assign (if there are any known translation issues), however specific details are part of the latest Testing PAD usually called as ''PAD (<server_name>)'' and listed in '''External links''' section. Find a PAD corresponding to the chosen server and open it. All necessary details and all your reports will go to the Testing PAD. The actual form of the Testing PAD is fully up to the Test Guide. All PADs from previous testing are linked here as ''Archive PAD <date> (<server name>)'' and every newer PAD replaces previous document including all issues opened by that time.

===Fixing known translation issues===
Review all known translation issues and fix as many as possible. If there is a case of string that you are unable to fix as a translator, please investigate reasons. Once your work is done, please add a summary comment with all details into latest Testing PAD so the Test Guide can update the upcoming test or progress the task.

===Help testers===
Testers might have questions related to currently missing strings or other things related to translation. Review the latest Testing PAD and help to resolve those issues or open discussion directly on team chat.

===Confirm issues on Atys===
There might be translation issues that need to be confirmed on Atys. If you have power or suitable character on Atys, please join the test opened on Atys in role of a Tester and verify what is needed along the current Testing PAD.

=Encyclopatysts and Marketing team=
Following text describes what should members of those teams focus on at the Test board in case they collect information for the upcoming release notes. Also members of the Project Ryzom Wiki can start to create documentation based on Testing PAD and task details.It requires you to join the [[Ryzom_Wiki:About|Ryzom Wiki project]] or become member of the [[:Category:Communication-Marketing_Team|Communication & Marketing team]] to act in this role. Your work mainly includes:
* Create new documentation
* Update existing documentation
* Prepare patch notes

==Choose a server==
While Yubo is a testing server for purpose of development, there is nothing to find about completed changes. Important testing is being done on Gingo, all passed tasks approve a change to be released later on Atys. Also tasks being currently tested on Atys itself might give you information about latest bug fixes. You will also meet tasks that correspond to already published changes, however there are issues to solve and the Test team was unable to close those tasks yet.

==Choose a task==
There are two main columns you should choose tasks from:
* '''Blocked for Atys''', where all tasks that successfully passed testing on Gingo server are. These changes are ready to release or being tested on live server, from point of view of the Test team. Look for new tasks (yellow) that has arrived from Gingo or been fixed on Atys. Remember that Orange coloured tasks have some work to be done so even your documentation might not be complete before all is solved.
* '''Done''', where all completed tasks come at the end of own lifetime. These changes were re-tested on Atys and confirmed to be working as expected.
Once you find a suitable task, open its details.

==Start working==
When you open a task details there is a lot of component and features that are not necessary for work of a translator. You should however pay attention to
* '''Description''' where you can find some overal details
* '''External links''' where you will find links to other related external documents
* '''Comments''' where some additional task details might be placed

===Tasks with a PAD===
Review current reports and issues in the appropriate Testing PAD (listed in External links section) to see details about the change. Base your documentation on task description, task comments and latest Testing PAD details. Some help with Testing PAD organization can be found in the [https://cloud.ryzom.com/f/36039 PAD help document] or look at self-describing [https://cloud.ryzom.com/f/36218 example PAD].

===Tasks without a PAD===
Some minor tests might not have own testing PAD. Base your documentation on details in task description and comments.

=Artists, designers and lorists=
Members in this role do not actively participate on the team work, however their abilities are very important in some specific situations. The Test Team might discover missing or broken objects, graphics or design issues, need to clarify details along the Lore or, with your cooperation, suggest solutions for troublesome situations. Our goal is a good player experience after all. You have to be member of an [[Computer_graphics|artist]], a [[Level-Design|design]] or a [[Lore team|lore]] team team to act in this role.

=Coordinators=
Being a team coordinator is the most complicated role, because it includes all the management work. Management of task on the board, creating and evaluating of tests, keeping eye on known issues and communication with other teams represented by team members in roles described above. You need to be experienced with work of the team. It would be hard to describe all within this article so please read the [[Being a Test Team Coordinator]] article.

{{Portal|Forge}}
[[Category:Test|Test team]]
[[Category:Testing Team]]
[[Category:Ryzom Team]]
[[Category:Test]]
[[Category:Tutorials]]

Test Team roles

2022-03-20T05:38:07Z

Ledania:

<noinclude>{{WIP}}{{Trad|DE=Rollen des Testteams|EN=Test Team roles|H=1}}</noinclude>
The team is using the system of roles. It means that, based on your abilities and will, you can occupy various roles in the team. This system tries to join abilities of all team members.

=Theory=
Besides testers themselves, the [[Test Team]] also consists of many members who participate in other Ryzom teams. This and the matter of the team work makes it a place where a cooperation is highly needed. Most of team members are however volunteers and it would be unproductive to stick each member with only one position. That is the reason why we use a system of roles.

* [[#Coordinators|Coordinators]], who coordinate the team
* [[#Testers|Testers]], who perform all testing
* [[#Developers|Developers]], who fix discovered issues
* [[#Translators|Translators]], who fix discovered translation issues
* [[#Encyclopatysts_and_Marketing_team|Encyclopatysts and Marketing team]], who document changes and publish news
* [[#Artists.2C_designers_and_lorists|Artists, designers and lorists]], who fix discovered visual issues and provide background information

Each team member can temporarily act in any role he or she want, in case he meets its requirements, and his or her work emerge from the current role. This also means that different roles focus on different tasks and information. Roles are not permanent and you can switch it any time you want. It is not needed to tell others what role do you actually act in, make your decision and do what is needed. This might be a little confusing, that is why following chapters give you basic overview about tasks of each role.

=Testers=
This chapter describes how to start with a new testing from a tester's perspective. It is expected that you have [[The_Test_Team_Handbook/3_-_Setting_up_connection_to_non-public_Ryzom_servers|set up testing servers]] already (for testing on Yubo ang Gingo) and that you are a bit [[The_Test_Team_Handbook/4_-_On_a_testing_server|familiar with working on testing servers]]. Your work will mainly include:
* Participating on currently opened tests
* Re-testing issues reported by players or other Ryzom team members
* Testing for other Ryzom team members on-demand

While re-testing reported issues requires you own effort and testing on-demand is initiated by other member, regular testing starts on the [[The_Test_Team_Handbook/5_-_Test_board_organization|[Team] Test board]] on the Kan Board. There you can find all active tasks of the team. Following steps will help you to find a test you can do.

==Choose a server==
There are three columns where to look for a test you can do.
* '''Testing on Yubo''' for tests situated on the developers server
* '''Testing on Gingo''' for tests situated on the testing server
* '''Testing on Atys''' for tests opened for live server.
Choose one column and your testing will be placed on corresponding server.

==Choose a task==
Review tasks in the selected column. Priority is set by its position, so tasks on top are more important than those at bottom. Task colour indicates its state, if it is green, the test is running. In case there are some issues discovered already, the task is orange and you should know that the testing round might be closed soon. Find a task that you want to try and open it by clicking.

==Start working==
When you open a task details there is a lot of component and features that are not necessary to perform a test. You should however pay attention to:
* '''Description''' where you can find some overall details
* '''External links''' where you will find links to Testing PAD and other related external documents
* '''Comments''' where some additional task details might be placed
Most of testing tasks contain link to one or more Testing PADs, usually called as ''PAD (<server_name>)'' and listed in '''External links''' section. Find a PAD corresponding to the chosen server and open it. It includes all necessary details and all your reports will go to that Testing PAD. The actual form of the Testing PAD is fully up to the Test Guide. All PADs from previous testing are linked here as ''Archive PAD <date> (<server name>)'' and every newer PAD replaces previous document including all issues opened by that time. Some help with Testing PAD organization can be found in the [https://cloud.ryzom.com/f/36039 PAD help document] or look at self-describing [https://cloud.ryzom.com/f/36218 example PAD].

Please read [[The_Test_Team_Handbook/6_-_Testing_report_tips|Testing report tips]] to know more about what a tester's work covers.

===Tasks without a PAD===
Some minor tests might not have own testing PAD. In that case the task description should contain all necessary details and you put your testing report into the task Comments.

=Developers=
This chapter describes details useful for developers who would like to work on fixing found issues or unblocking testing tasks. In case you need the Test team to perform new testing, follow the [[How to request new testing]] article please. You need to be a [[Development_Team|Ryzom]] / [http://www.ryzomcore.com/ Ryzom Core] / [[Forge_Portal/Projects|Ryzom project]] developer (for example [[ARK]] team) or a member of either the [[Animation team|Animation]] or the [[Event team]]. Your main work in the team includes:
* Request new tests
* Provide testing tools and necessary details
* Solve known issues

==Choose a server==
First you need to choose a server you will work with. Tasks that being prepared for testing on a server are stored in columns on left to server one. '''Waiting for Yubo''' column contains tasks that will continue to testing on server Yubo, '''Waiting for Gingo''' being solved on Gingo server and '''Waiting for Atys''' are going to be (re)tested on Atys.

==Choose a task==
There are two types of board columns you should focus on:
===Non-Tester columns===
'''Blocked for Yubo''', '''Blocked for Gingo''' and '''Blocked for Atys'''. Here are new and troublesome tasks stored and those tasks are not in active testing at the moment. All such tasks are usually yellow (new) or orange (troublesome). Look for tasks with one of following tags on:
* '''⏳ patch''', orange tag, a task that needs to be patched to server first, to enable latest changes and fixes
* '''Clarify first''', yellow tag, for tasks that requires a discussion or more details
* '''Bugs reported''', orange tag, a task with reported issues to be fixed
* '''Bugs reported on Atys''', pink tag, a task with reported issues on Live server to be fixed

===Tester columns===
'''Testing on Yubo''', '''Testing on Gingo''' and '''Testing on Atys'''. All tasks here are currently in the testing. Look for tasks with orange '''Bugs reported''' tag on. Remember that in this case you affect actually running test, be careful and cooperative. Once you find a suitable task, open its details.

==Start working==
When you open a task details there is a lot of component and features that are not necessary for work of a developer. You should however pay attention to
* '''Description''' where you can find some overal details
* '''External links''' where you will find links to other related external documents
* '''Comments''' where some additional task details might be placed
In case the task is not being currently tested, all known issues should be listed as sub-tasks. Assign the sub-task in case you wish to start working on it.

===Tasks with a PAD===
Review current reports and issues in the appropriate Testing PAD (link to be found in External links section). Research a possibility to fix or clarify each reported issue and leave a note in the PAD (along with date and time) once there is any change you perform or you know about (fix, change, additional related details...). Do not mark issues as fixed, wait testers to confirm the fix. Some help with Testing PAD organization can be found in the [https://cloud.ryzom.com/f/36039 PAD help document] or look at self-describing [https://cloud.ryzom.com/f/36218 example PAD].

===Tasks without a PAD===
Some minor tests might not have own testing PAD. Research a possibility to fix or clarify each reported issue and leave a comment about any change you perform (fix, change or additional related details you know). Wait testers to confirm the fix.

=Translators=
Following chapter describes how can members of the Translation team get involved in testing and help solve translation issues. Translators can find a work in almost all parts of the testing process, however more right the task is placed on the board, more complete the change is. It is not common, but members of the Translation team can also request the Test team to perform a testing focused on translations, to look for missing strings or any string related issues like text over-floating and incorrectly encoded strings. In such case please read [[How to request new testing]] article. You need to be a member of the [[Translation|Translation team]] to act in this role. Your work is based on discovered translation issues and will mainly include:
* Fixing known translation issues
* Help testers
* Confirmation

==Choose a server==
First you need to choose a server. There is usually not much to do on Yubo while changes are in early stages there and it can significantly change before it is fully developed and used strings are final. Your best options are to focus on Gingo, where a testing before release is done or Atys where we hunt for missing or wrong translations.

==Choose a task==
Depending on target of your work, you focus on different board columns:

===Management columns, Blocked for Gingo and Blocked for Atys===
Here are new and troublesome tasks stored and those tasks are not in active testing at the moment. Look for tasks with purple Translation issue tag. You can help by fixing wrong or missing translations or by investigating why it is not possible to fix the translation.

===Testing columns, Testing on Gingo and Testing on Atys===
All tasks here are currently running a test. Look for tasks with purple Translation issue tag. You can help by taking care of newly discovered translation issues and giving support to testers in related questions. Some tasks also needs to verify translation issues on Atys. Remember that in this case you affect actually running test, be careful and cooperative. Do all your reports into the latest PAD and remember to mention date and time.

==Start working==
Each task supposed to have a minor issue subt-ask you can assign (if there are any known translation issues), however specific details are part of the latest Testing PAD usually called as ''PAD (<server_name>)'' and listed in '''External links''' section. Find a PAD corresponding to the chosen server and open it. All necessary details and all your reports will go to the Testing PAD. The actual form of the Testing PAD is fully up to the Test Guide. All PADs from previous testing are linked here as ''Archive PAD <date> (<server name>)'' and every newer PAD replaces previous document including all issues opened by that time.

===Fixing known translation issues===
Review all known translation issues and fix as many as possible. If there is a case of string that you are unable to fix as a translator, please investigate reasons. Once your work is done, please add a summary comment with all details into latest Testing PAD so the Test Guide can update the upcoming test or progress the task.

===Help testers===
Testers might have questions related to currently missing strings or other things related to translation. Review the latest Testing PAD and help to resolve those issues or open discussion directly on team chat.

===Confirm issues on Atys===
There might be translation issues that need to be confirmed on Atys. If you have power or suitable character on Atys, please join the test opened on Atys in role of a Tester and verify what is needed along the current Testing PAD.

=Encyclopatysts and Marketing team=
Following text describes what should members of those teams focus on at the Test board in case they collect information for the upcoming release notes. Also members of the Project Ryzom Wiki can start to create documentation based on Testing PAD and task details.It requires you to join the [[Ryzom_Wiki:About|Ryzom Wiki project]] or become member of the [[:Category:Communication-Marketing_Team|Communication & Marketing team]] to act in this role. Your work mainly includes:
* Create new documentation
* Update existing documentation
* Prepare patch notes

==Choose a server==
While Yubo is a testing server for purpose of development, there is nothing to find about completed changes. Important testing is being done on Gingo, all passed tasks approve a change to be released later on Atys. Also tasks being currently tested on Atys itself might give you information about latest bug fixes. You will also meet tasks that correspond to already published changes, however there are issues to solve and the Test team was unable to close those tasks yet.

==Choose a task==
There are two main columns you should choose tasks from:
* '''Blocked for Atys''', where all tasks that successfully passed testing on Gingo server are. These changes are ready to release or being tested on live server, from point of view of the Test team. Look for new tasks (yellow) that has arrived from Gingo or been fixed on Atys. Remember that Orange coloured tasks have some work to be done so even your documentation might not be complete before all is solved.
* '''Done''', where all completed tasks come at the end of own lifetime. These changes were re-tested on Atys and confirmed to be working as expected.
Once you find a suitable task, open its details.

==Start working==
When you open a task details there is a lot of component and features that are not necessary for work of a translator. You should however pay attention to
* '''Description''' where you can find some overal details
* '''External links''' where you will find links to other related external documents
* '''Comments''' where some additional task details might be placed

===Tasks with a PAD===
Review current reports and issues in the appropriate Testing PAD (listed in External links section) to see details about the change. Base your documentation on task description, task comments and latest Testing PAD details. Some help with Testing PAD organization can be found in the [https://cloud.ryzom.com/f/36039 PAD help document] or look at self-describing [https://cloud.ryzom.com/f/36218 example PAD].

===Tasks without a PAD===
Some minor tests might not have own testing PAD. Base your documentation on details in task description and comments.

=Artists, designers and lorists=
Members in this role do not actively participate on the team work, however their abilities are very important in some specific situations. The Test Team might discover missing or broken objects, graphics or design issues, need to clarify details along the Lore or, with your cooperation, suggest solutions for troublesome situations. Our goal is a good player experience after all. You have to be member of an [[Computer_graphics|artist]], a [[Level-Design|design]] or a [[Lore team|lore]] team team to act in this role.

=Coordinators=
Being a team coordinator is the most complicated role, because it includes all the management work. Management of task on the board, creating and evaluating of tests, keeping eye on known issues and communication with other teams represented by team members in roles described above. You need to be experienced with work of the team. It would be hard to describe all within this article so please read the [[Being a Test Team Coordinator]] article.

{{Portal|Forge}}
[[Category:Test|Test team]]
[[Category:Testing Team]]
[[Category:Ryzom Team]]
[[Category:Test]]
[[Category:Tutorials]]

New Tester's Checklist

2022-03-20T05:23:25Z

Ledania:

<noinclude>{{WIP}}{{Trad|DE=Checkliste für neue Tester|EN=New Tester's Checklist|H=1}}</noinclude>
This is a short checklist that you, as a new member of the [[Test Team]], can use to make sure everything is ready.

==Access to necessary chat channels==
Make sure you see all following channels on the Ryzom Chat and that you can speak there. Contact [[User:Tamarea|Tamarea]] to gain access.
* [https://chat.ryzom.com/group/announcements #announcements]
* [https://chat.ryzom.com/group/chat-general #chat-general]
* [https://chat.ryzom.com/group/t-qs_test #t-qs_test]

==Access to all game servers==
Make sure you have installed 3 separate clients to connect different servers and that you can connect to all of them. Contact [[Test_Team#Coordinators|Test Team coordinators]] if you have troubles to configure your clients and [[User:Tamarea|Tamarea]] to gain access.
* Yubo, the development server
* Gingo, the testing server
* Atys, the live server

==Access to Kanboard==
Make sure you are able to see the [https://board.ryzom.com/?controller=BoardViewController&action=show&project_id=51 Test Team Board] and display a task details. Contact [[User:Tamarea|Tamarea]] to gain access.

==Access to the Cloud==
Make sure you are able to see [https://cloud.ryzom.com/f/1355 Test-Team] folder on Ryzom Cloud including subfolders, make sure you can read files, mainly PADs. Contact [[User:Tamarea|Tamarea]] to gain access.

==Account on Wiki==
Make sure you have a valid account on the Ryzom Wiki and that you have added yourself into the [[Test_Team#Testers|list of testers]]. Contact [[User:Zorroargh|Zorroargh]] to create account.

{{Portal|Forge}}
[[Category:Test|Test team]]
[[Category:Tutorials|Test team]]
[[Category:Testing Team]]
[[Category:Ryzom Team]]
[[Category:Test]]
[[Category:Tutorials]]

The Test Team Handbook

2022-03-20T05:13:29Z

Ledania:

{{Trad
|DE =Das Test-Team-Handbuch|DEs=3
|EN =The Test Team Handbook|ENs=0
|ES =The Test Team Handbook|ESs=5
|FR =Manuel de l'équipe de test|FRs=5
|RU =The Test Team Handbook|RUs=5
|H =
|palette=Grey
}}
This document gives you quick overview about necessary steps you must undertake to join the [[Test Team]] and be able to do good work. It is enriched with links to other documents with more details in case such text exists. If you have any questions or suggestions, feel free ask on [https://chat.ryzom.com/group/chat-general #chat-general] (accessible for team members only) or [https://chat.ryzom.com/channel/pub-general #pub-general] (open for everybody).

=Step 1: Apply to join=
If you are willing to apply to become a member of the Testing team, please contact Tamarea, directly on [https://chat.ryzom.com/direct/Tamarea Ryzom chat] or by sending an e-mail to [mailto:tamarea@ryzom.com tamarea@ryzom.com]. You need to get access to team tools and private chat rooms. After this step use the [https://chat.ryzom.com/group/t-test #t-test] chat room for any questions related to testing.

'''More information:''' [[The Test Team Handbook/1 - Get in touch with Ryzom Forge|Get in touch with Ryzom Forge]]

=Step 2: Get familiar with team tools=
As next you need to become familiar with tools used by the Ryzom team. For planning we use Kan Board, for collaboration we have a cloud system and internal (team) chat rooms.

'''More information:''' [[The Test Team Handbook/2 - External team tools|External team tools]]

=Step 3: Configure Ryzom clients=
The most of team work and testing is closely tight to our testing servers. You need to create two separated client installations to have access to Yubo, the developers server, Gingo, the testing server and also to beta updates for Atys server.

'''More information:''' [[The Test Team Handbook/3 - Setting up connection to non-public Ryzom servers|Setting up connection to non-public Ryzom servers]]

=Step 4: Prepare for testing=
Once you have access to testing servers, you need to prepare some characters to perform tests and become familiar with in-game tools for testers. It will make your life much easier.

'''More information:''' [[The Test Team Handbook/4 - On a testing server|On a testing server]]

=Step 5: Choose a test=
Your work in the Test team is mostly up to you. You are free to join any test and you can use any procedure that fits you. However there are some rules that help cooperation with others, prevents fails. You need to get familiar with our Test board where we track all existing testing tasks.

'''More information:''' [[The Test Team Handbook/5 - Test board organization|Test board organization]]

=Step 6: Start testing=
Now you are getting to the core. Your work would be pointless if you could not provide all details from your testing. There are some tips that can help you in case you have no previous experience with a testing.

'''More information:''' [[The Test Team Handbook/6 - Testing report tips|Testing report tips]]

{{Portal|Forge}}
[[Category:Test|Test team]]
[[Category:Tutorials|Test team]]
[[Category:Testing Team]]
[[Category:Ryzom Team]]
[[Category:Test]]
[[Category:Tutorials]]

Region

2022-03-19T17:25:29Z

Ledania:

{{Trad
|DE = Region |DEs= 4
|EN = Region |ENs= 4
|ES = Región |ESs= 4
|FR = Région |FRs= 0
|RU = Регион |RUs= 1
|H =
|palette=
|ref=
|com=
}}
;Region : Somewhat homogeneous in terms of its mineral resources, [[Portal:Fauna|fauna]], [[Portal:Flora|flora]] and the [[tribes]] that occupy it, the [[region]]s are the smallest geographical subdivisions on Atys. However, some regions may have several different [[ecosystem]]s or their main [[ecosystem]] may not be that of the [[continent|subcontinent]] to which they belong. Examples include the de [[Grove of Confusion]], the [[Hidden Source]] or the [[Knot of Dementia]].
:Each region has "Localities", special places of interest, and [[outpost]]s that are usually abandoned.
:From a homine geography point of view, the regions are not as homogeneous as the official boundaries of nations might suggest. They are home to [[tribes]] that may be rebellious or even hostile to the nation dominating their territory.
 
 
*See also: [[Continent|Continent, Sub-continent]], [[island]], [[super-region]].
 
 
<noinclude>[[Category:Glossary]] [[Category:Geography]] [[Category:Atys|Continent]]
[[de:Region]] [[en:Region]] [[es:Región]] [[fr:Région]] [[ru:Регион]]</noinclude>

Rangers Assembly of Nivia 28, CA2 of Jena year 2603

2022-03-19T17:10:41Z

Ledania:

<noinclude>{{Trad
|DE =Ranger-Versammlung vom Nivia 28, CA2, Jena-Jahr 2603
|EN =Rangers Assembly of Nivia 28, CA2 of Jena year 2603
|ES =Asamblea de Rangers de Nivia 28, CA2 en el año de Jena 2603
|FR =Assemblée des Rangers du Nivia 28, CA2 de l’année de Jena 2603
|RU =Собрание рейнджеров, Нивии 28, CA2 в год Йены 2603.
|H =
|palette=ranger
}}
[[Category:Rangers]] [[Category:Ranger Literature]]</noinclude>
 
 [[File:Réunion Ranger au Bois d'Almati 1.png|thumb|400px|center|Ranger meeting with Wuaoi at [[Almati Wood]] ; Nivia 28, 2nd AC, 2603.]]
 
 
 
 
''Do’ro Thée gathers her sheets and the notes that CraftJenn kindly gave her. She carefully stores the pictures for the Great Library. Thanks to the Great Glouglou , the report will be complete, she thinks. A light but still fresh breeze reminds her that winter is not that far away, as she looks at the blossoming buds. Emotion invaded her as she thought of Wuaoi's unexpected retirement and Teeneemai's disappearance... she too was a real Ranger. A tear blurs her make-up and falls on the page.... She will really have to go to Silan more often....''
 

''She starts writing:''
 
 
:<big>Minutes of the Nivia Rangers Assembly 28, 2nd AC of the year of Jena 2603</big><ref>OOC May 20th 2019, https://app.ryzom.com/app_forum/index.php?page=topic/view/22110/87&post195630=en#87</ref><ref>'''Translations : [[User:Krill|Krill "Tyllwhee" Be'Luga]]''' • Additional translations : [[User:Dorothée|Do’Ro Thée]]</ref>

::Were present (in alphabetical order):

::[[:fr:user:Achnar|Achnar]], [[Apocamus Dradius]], [[:fr:user:Ashgan|Ashgan]], Atysa, [[:fr:user:Azazor|Azazor Eridlo Mirihus]], [[User:Bitttymacod|Bitttymacod]], Byiet, [[:fr:user:CraftJenn|Craftjenn]], Djiper, [[user:Dorothée|Do’ro Thée]], [[:fr:user:Eleanide|Eleanide]], Eolinius, Jyrvie, Kaissia, Karagoz, [[User:Kiwa Lie|Kiwa 'Lie]], [[User:Krill|Krill "Tyllwhee" Be'Luga]], [[fr:user:Krinseus|Krinseus]], [[fr:User:Kyriann Ba'Zephy|Kyriann Ba'Zephy Rie]], Laisuki, Meggy, Meubli, [[User:Moniq|Moniq]], [[:fr:Nilstilar|Nilstilar Thorec]], Ornella, Sich, [[:de:user:Tryroamer|Tryroamer]], Ubhal, Wixarika, [[Wuaoi Yai-Zhio]], Yaandor , Yki, [[user:Zorroargh|Zo'ro Argh]].

''She wonders why there is no Avian in Almati, she should have stayed in Crystabell and written on the beach... In the distance, a kincher roars...''

::'''Wuaoi Yai-Zhio''' announces: To all Rangers, aspiring Rangers and interested homins. Our meeting at Ranger Circle in Almati Wood begins immediately.

::'''Meggy''' (in the distance): I'm comiiiiiiiiiiiiiiiiiiiiiiiiiiiing!

::Bitttymacod: To all Rangers, aspiring Rangers and interested homins. Our meeting at Ranger Circle in Almati Wood begins immediately.

::Sorry Wuaoi I was relaying your message... ( he blushed) I meant: I was trying

::Crafjenn : The report will be available in a few days....

:''Apocamus Dradius comes out of the tower, walks forward and greets respectfully.''

:''The Rangers present responded to his greeting warmly.''

::'''Wuaoi Yai-Zhio''': Come and sit by the fire by my side.

::'''Apocamus''' Dradius : Thank you Wuaoi

::'''Tryroamer''' calls: I'm at Almati Wood now, no one at camp?

::'''Meggy''': We're at the Ranger circle, not far from the Kami transporter.

::'''Tryroamer''': strange

::'''Wuaoi Yai-Zhio''': Welcome Rangers, and to our visitors too!

:''Azazor nods his head''

:''Craftjenn winks at Azazor.''

::'''Byiet''': hello! How are you? (she greets all those present, who answer her)

::'''Wuaoi Yai-Zhio''': I asked you to come because I have an important announcement to make.

:''Kiwalie swallows her cookie quickly and opens her ears wide''

::'''Wuaoi Yai-Zhio''': My mind has been troubled for some time, and I asked to withdraw for a moment, so I could meditate on this.

::'''Jyrvie''': Oh!

:''Meggy and Kiwalie are worried about Wuaoi....''

::'''Wuaoi''': Let me reassure you, my physical health is good, but I have seen omens as I meditated on the Precepts

:''Wuaoi rolls his amber cube. This one stops on the Diligence side''

::'''Wuaoi''': Diligence. Ensure that the work is done

::'''Wuaoi''': My job was to train you and make you Rangers.

::That's what I did, as best I could.

:''Yki is looking for her ranger badge''

::'''Wuaoi Yai-Zhio''': Veteran Ranger [[Apocamus Dradius]] will supervise your actions from now on

:''Eolinius arrives (exchange of greetings)''

:''Wuaoi Yai-Zhio bows to the assembled Rangers and sits down.''

::'''Wuaoi''': Apocamus, please stand up and greet your Rangers

::'''Apocamus''': Greetings, Rangers. I am [[Apocamus Dradius]]. Grandson of [[Orphie Dradius]]

:'' Apocamus Dradius bows respectfully''

:'' (Greetings from the meeting)''

:'' Kyriann sits quietly''

::'''Apocamus''': Thank you Wuaoi. I was called back to take Wuaoi's place. I can never replace him, but I'll do my best.

:''Azazor ''(whispering to Wixarika)'': your hair grows fast

::'''Apocamus''': As a veteran ranger, my task is to observe and supervise the new Rangers

::Zo'Ro Argh ''(sitting down)'': Woren Siloy (Hi, Rangers) :)

:'' Kiwalie smiles as she thinks of Orphie and the TENANT treaty''

::'''Apocamus''' (grateful to Wuaoi): I will preside over the Rangers assemblies from now on. Thanks again to Wuaoi, for his long work and the passion he has put at the service of the Rangers

:''Meggy smiles at Nilstilar''

::'''Kiwalie''' approaches Wauoi, fills her bag with cookies and makes her a big kisu: thank you for all Wuaoi

::'''Wuaoi Yai-Zhio''' (whispers to Apocamus in a low voice): begins with the Oservators' reports.

::'''Apocamus''': We will start with the observers

:''Do'ro Thee thinks that the Rangers are quite dissipated tonight and should listen better.''

::'''Apocamus''': We will start with the Forest. Zorroargh, is there anything to report?

:''Kiwalie shakes Zo', Craftjenn elbows him.''

::'''Kyriann''' screams: CAL I SELAK!!!!!

::'''Nilstilar''': Hello! How are you doing? How are you?

::'''Kyriann''': if he's not awake with this....

:'' Eolinius laughs''

::'''Kiwalie''' screams: Kwkkwww Azazor!

:'' Achnar gives a big sledgehammer blow on Zo'Ro's foot''

:''Wuaoi is surprised and looks for the source of this disorder''

::'''Byiet''': There's slow, and then there's slower, and now there's

::'''Apocamus''': Does anyone else have anything to report?

::'''Kiwalie''': Sorry but Zo' seems to be sleeping....as far as the forest is concerned, they are victims of Kitins invasions too

::'''Byiet''': I think that means no… Can we continue, please?

::'''Kiwalie''': We destroyed a mound at the hidden source and I found another one at the psykopla mound

:''Nilstilar nods''

::'''Kiwalie''': Nilstilar who is here could give us more news I think

::'''Nilstilar''': ... and another near the Fugitive Garden?

:'' Azazor raises his hand''

:'' Nilstilar smiles

:'' Eolinius raises his hand

:''(Arrival of Laisuki, exchange of greetings)''

::'''Kyriann''': I found one near Pyr, a little to the west.

::'''Kiwalie''' smiles at Azazor: I'm going to come to that

:''Krill wonders if Pyr is in the Forest, and since when''

::'''Apocamus''': Anything to report, Nilstilar?

::'''Kyriann''' ''(obviously upset)'': Yeah, the forest first, huh? Pffffffff

:''Do'ro Thée stops writing and smiles as he thinks of Djiper and his awesome "pfffffffffff"s.''

::'''Nilstilar''' ''(responding to Krill)'': Not yet, but soon perhaps, An-Nair

::I'm kidding, of course.

::'''Byiet''': There were 4 Kitin invasions, one in each nation. They were very short and each was eliminated in a single evening

::'''Apocamus''': Anything to report in the Lakes?

::'''Jyrvie''': Lordoy, there was an assembly in the lakes. They want to organize a kind of market to provide equipment for new recruits from Silan

:'' Eolinius thinks that the speech is a little bit disjointed''

:'' Wuaoi takes a deep and noisy breath, head bent over''

::'''Byiet''': That's not necessary. Silan's missions provide everything that is necessary

::'''Jyrvie''' looks at Byiet: I'm just reporting it

::Nislitar: What is necessary is not what is asked

::'''Jyrvie''': And they have a new leader for their Federal Army, Lunakan

::'''Apocamus''': Thank you for the Jyrvie report

:''Kyriann raises her hand.''

::'''Apocamus''': Kyriann, yes?

::'''Jyrvie''': And they have a new leader for their Federal Army, Lunakan

:''Kyriann waits until Jyrvie has finished talking''

::'''Jyrvie''': And the Kitin invasions, you already know.

:''(she greets Apocamus)''

::'''Kyriann''': Nair Apocamus Dradius I just want to say a word about the market. Those who have left Silan for some time but have not yet joined a guild and who are struggling to find good quality equipment, between quality 50 and 110. We will respect very reasonable prices.

:''(Kyriann sits down again)''

::'''Apocamus''': Thank you Kyriann for your comments

::Are there any other reports about lakes?

::''(silence)''

::'''Apocamus''': A report to do for the Jungle?

:''Azazor grumbles a little''

:''Karagoz raises her hand''

::'''Apocamus''': Karagoz, you have the floor

::'''Karagoz''': I must say, Rangers, that many events have occurred that are worth reporting to this assembly

::'''Achnar''' ''(in a low voice)'': Did you see anything, Djiper?

::'''Karagoz''': But my memory is lacking, and also I could have brought more diligence to my duties. I would especially like to mention the Assembly of Circles in Zora, the first in a long time

:''Wuaoi raises his head to the mention of the Circles''

::'''Karagoz''': I did not attend the meeting, but I understand that it was important. I give my place to anyone who was there and who could give details about this meeting or who would have other information than the one I have at the moment. That's all, thank you. (She greets)

::'''Apocamus''': Thank you Kazagoz for this report; anything else about the jungle?

::We must also talk about the Desert. Anything to report there?

:'' Azazor is looking for eyes to represent the representative of the desert ranger''

::'''Apocamus''': Kiwalie, you are the Desert Observer. Do you have anything to report?

:'' Azazor raises his hand''

:'' Azazor lowered his hand while waiting, because well, the cramps....''

::'''Kiwalie''': The materials for Thesos' wall have been gathered! Good news, now it still has to be built

:'' Ubhal looks at the legionnaire''

::'''Kiwalie''': hoping it will be useful against the Kitins....

::'''Apocamus''': One moment, Azazor

:'' Nilstilar has difficulty holding his laughter back''

::'''Kiwalie''': The kitins attacked near Pyr, the mound was destroyed but we need to understand where they came from.

:'' Ubhal looks at Matis Ambassador ''

::'''Kiwalie''': Azazor who is present will also be able to tell us about it

::'''Kiwalie''' (turning his foot in sawdust): Can I ask you a question Apocamus?

:'' Eleanide poses discreetly, greeting her knowledge with head''

::'''Apocamus''': Of course Kiwalie

::'''Achnar''': Apoc' it suits him very well! we have nicknames also in the rangers

:''Meggy laughs loudly''

::'''Kiwalie''' smiles: how is your grandmother? Orphie, a long-time friend I miss very much.

::'''Kyriann''' grumbles: So I come after the grandmother.....

:'' Ubhal laughs''

::'''Apocamus''': She's fine, even though I don't see her often.... She's very busy with her homework.

::'''Kiwalie''': It's good to know she's healthy, thank you Apocamus!

::'''Apocamus''': You're welcome, Kiwalie. Thank you for your report 2

::'''Kiwalie''': I'll let Azazor speak to us about the desert in more detail.

:'' Azazor growls a little bit but gets up''

:'' Eleanide smiles''

::'''Kyriann''': Kiwalie has already told you about the mound near pyr, to the west to be precise.

::'''Apocamus''': Azazor, do you want to report back to us?

:'' Ubhal is blocking his ears in anticipation of screams''

::'''Kyriann''': But I have one question above all. Have you thought about making a map of the appearance of these mounds?

::'''Byiet''': I would like to talk about

::'''Kyriann''': It should also include the moments when they occurred. Or at least a niche. Maybe even the season? It seems that kitins are less active in winter. Could this be a way to check?

:'' Azazor sits down again''

::'''Apocamus''': Not yet Azazor, but it's a good idea. Do you want to take care of this card? Or another volunteer ranger perhaps? It should cover all nations.

::'''Kyriann''': I think that's your job. but I can help bring back the mounds found

::'''Kiwalie''': I have noted the regions of the mounds but I confess...not the seasons

::'''Apocamus''': After these reports, we will see if we need to replace or appoint new Observers

::'''Kyriann''': only regions? not specific locations?

::'''Kiwalie''' (laughing): It's sometimes difficult to write down the exact locations when the Kitins are trying to kill us (giggles)

::Arrival of Ornella: good evening to all!

::'''Apocamus''': Do the current Observers wish to continue?

:''Meggy raises her hand''

::'''Apocamus''': Meggy, did you want to say something?

::'''Meggy''': Yes, I wanted to speak for Karagoz. She had to leave.

::'''Apocamus''': Does Karagoz want to continue to be an Observer?

::'''Meggy''': She asked me to tell you that she would be happy to keep her job as an observer. However, she was a little busy with tasks outside the rangers. Yes, if someone wants to take over this job, she'll let him take over. She will understand the decision whatever it is. That's all.

:''Dorothee raises her hand''

::'''Apocamus''': Thank you Meggy

::'''Meggy''': Of course. I will forward to him the decision that will be taken today

::'''Apocamus''': Anyone want to help Karagoz observe the Jungle?

:''Meggy smiles,

:'' Zorroargh is grateful to Wuaoi.''

::'''Apocamus''': Dorothee, do you want to say something?

:''Azazor discreetly slips away''

::'''Nilstilar''' (low): He's back!

:''Zorroargh greets Apocamus with respect.''

::'''Dorothee''': First of all, I apologize for beeing late.

::Then I have two reports to make:

:''Wuaoi notices that his friend Zo'ro is awake again. ''

::'''Jyrvie''' screams: Ouch!.... Ouch!

::'''Kyriann''' gets up and asks: What?

::(astonished, her eyes turn to Jyrvie)

:'' Kyriann sits down because Jyrvie seems to be fine.''

::'''Dorothee''': The great Azazor Eridan Mirihus invited me to talk to the Bai Nhori Drakani about the Oflovak road.

:'' Eolinius rubs his eyes and doesn't understand much.''

::'''Jyrvie''': (sorry a macro sting)

::'''Dorothee''' wonders what kind of insect is a macro to sting so hard, she continues: They have many questions about the road itself, the signs Oflovak may have left behind, his safety, and I think, above all, his access to other homins than the Rangers.

::'''Zendae''' turning to Nilstilar: the... “great” Azazor?

::'''Dorothee''': They have a lot of questions about the road itself, the signs Oflovak might have left behind, his safety, and I think above all, his access to other homins than the Rangers

::I gave the answers I had, so not necessarily much, except that the kitins are still going through it and the refugees are not safe there

::'''Nilstilar''' (quietly, to Zendae): great mouth I suppose (smiling)

::'''Zendae''' replies: for on, di amataki

::'''Dorothee''': The second report I would like to present is a request from Belami (New Rangers) with my support. He proposes that we organize a large caravan, to support the Fyros people especially in summer, as has been done in the past. I've already worked on the idea, and asked for some help. I had some with the Trykers, but I can't yet offer you a choice of realistic solutions

::'''Nilstilar''' (low, to Zendae): A caravan of byrh, I think (Dorothee smiles)

::'''Dorothee''': I will do it as soon as I mowed my stingas short enough

:''Ubhal raises his hand''

::'''Apocamus''': Such caravans are the Trykers' responsibility, but the Rangers can help. It would be bad for our neutrality to organize this

::'''Dorothee''': I tried to keep it short. Thank you for listening to me.

::'''Apocamus''': Ubhal, you have the floor.

:'' Ubhal grateful to the campfire''

::'''Ubhal''': Are we talking here about providing substential aid to a nation?

::'''Dorothee''': I don't see how that would break our Neutrality... Our guide has his hall in Thesos and would also benefit from such a caravan

::'''Ubhal''': In the past I have solicited this assistance from the Rangers. I was told that rangers were not involved in the struggle between nations

:''Wuaoi snores softly, rocked by the voices that debate.''

::'''Dorothee''': The help would be for all the inhabitants of the Desert, not just the Fyros Empire

::'''Ubhal''': Apart from that, my information shows that the construction of the wall could be a case of war with the Matis kingdom. The participation of the Rangers as Rangers could be interpreted as favoritism towards the Fyros Empire and against the Matis Kingdom! Is that what we want?

::'''Kiwalie''' laughs: if the Matis want to invade the desert it's not a wall that will stop them, they just have to go through the root bonuses

::'''Ubhal''': after what each Ranger will do as an individual, looks at him. I'm done.

:''Ubhal greet Apocamus respectfully.''

::Eolinius scratches his head looking at Kiwalie: hmm, Azazor said exactly the same thing

::'''Kiwalie''' : Ubhal, I have always accompanied the convoys on the water and beer road, not to hit homins but to protect the precious cargo from aggressive animals

::'''Ubhal''': the wall can be the pretext, it seems to me that the Matis have a plan for the wall...

:'' Craftjenn raises her hand''

::'''Kiwalie''': I'm not an ambassador to the matis, I'm just an ambassador to the fyros

:'' Zendae raises her hand''

::'''Apocamus''': Thank you Ubhal

::'''Apocamus''': Craftjenn, you're up.

::'''Craftjenn''': Helping young people, helping them to have armor to their size, helping them for a trek help them find their way, all this is, in my opinion, part of the Rangers' work. The Kitine threat is there, to stay united in the long term, you have to take care of the young people. The kitin threat is still there. To remain united in the future, we have to take care of the youngsters. This delivery helps young people to see the country, to open their minds. That's why I like to participate in these convoys. Thank you.

::'''Apocamus''': Thank you Craftjenn.

::'''Zendae'''? Did you want to say something?

::'''Zendae''': sil naete

:''Tryroamer raises its hand''

::'''Zendae''': I will speak as a Matis ambassador to the Rangers di amataki

:''Ubhal listens and smiles as he looks at Zendae

::'''Zendae''': I wish to refute any accusation that the Kingdom has a plan for the fyros wall south of Thesos

::'''Achnar''': What is your Zendae plan to replace it?

:''Ubhal looks at the master of arms''

::'''Zendae''' ''(looking at Achnar)'': I also don't have a personal plan on this subject. I think this wall is useless di amatakizo.

::Next topic. There is no problem if you are accompanying a Water Route. But as your instructor said, don't you dare organize it di amaulca. I'm giving the floor back. Thank you.

::'''Apocamus''': Thank you Zendae

::'''Achnar''': We need help and any assistance from any nation is welcome

::'''Apocamus''' : Tryroamer, did you want to add something?

::'''Tryroamer''' (Salutes Apocamus and bows deeply): I have confidence in what most, if not all, Rangers know better than I do the origins of the history of the Rangers. The most impressive in the training was the assistance provided to fleeing refugees in their efforts to reach the New Land alive.

:'' Apocamus encourages Tryroamer, who thanks him.''

:'' Tryroamer is grateful''

:'' Ubhal smiles''

::'''Tryroamer''': Finally, I, in particular, became a Ranger because of the influence of this altruistic and self-assigned mission and I hoped to see it continue with the objective and identification of the Rangers as a faction. To help refugees, Silan's arrivals but also those who return after a long absence. That's what became my personal motivation as a Ranger

:''(Approvals and nods with heads nodding in the assembly)''

:'' Wuaoi Yai-Zhio breathes regularly and calmly, not quite snoring.''

::'''Tryroamer''': I hope that such assistance will not be reduced by these considerations of impartiality. I hope that we Rangers will be able to continue to help refugees in particular. And I thought I understood correctly that this was the reason why in particular we were going through the Roots Rewards that would otherwise make these trips difficult or even impossible; even if they are necessary for the refugees to get by on Atys. I hope I didn't hurt anyone with my opinions. Please excuse me if I ever hurt you. Thank you for listening to me.

:''A small breeze blows around Wuaoi''

:''Ubhal agrees with Tryroamer, Eolinius applauds vigorously

::'''Apocamus''': Thank you for those kind words, Tryroamer''

::'''Kiwalie''': Beautiful Tryroamer speech! It feels good to hear the word of a Ranger of hearts

:'' Achnar throws an ace of spades''

::'''Nilstilar''' (very low): The value does not wait for the number of years...

::'''Apocamus''': Wuaoi, sorry to bother you, but we need your attention please.

:''Wuaoi shivers with a fresh breeze and raises his head''

::'''Wuaoi Yai-Zhio''': Yes? I listened. (he gets up and stretches).

::'''Apocamus''': There is one last announcement to make

::'''Apocamus''': I was hoping you could help me

::'''Wuaoi''': Oh yes, about the Library It is very humbly that I announce that a small collection has been published and deposited in the Great Library <ref>OOC: in the wiki</ref>. It brings together some of my [[The Way of the Ranger|speeches on the Ranger's Way]].

::I am also proud to say that more volumes on the Rangers will soon join it.<ref>OOC: The wiki will soon be augmented by a real Rangers' Lore.</ref>

::And finally. Thank you all, Rangers, who have traveled with me on this path. I will leave, but I know you will continue to represent the Rangers with all your heart. I wish you a safe journey.

:'' Kiwalie throws cookies at Wuaoi Yai-Zhio while the assembly shows its appreciation and applause to Wuaoi.''

::'''Wuaoi''': Apocamus, they're all yours now.

::'''Kaissia''' (shed a tear): Have a good trip Wuaoi........

::'''Apocamus''': Thank you Wuaoi, I will take care of them

::Applause and congratulations as Dorothee takes some Lucios from Wuaoi, and Apocamus who kindly take the pose.

::'''Apocamus''': We are nearing the end of this assembly

:''Moniq raises her hand''

::'''Apocamus''': Yes Moniq?

::'''Moniq''': Since we're done with the meeting, I have a few questions if I can.

::'''Apocamus''': Go ahead

::'''Moniq''': I noticed some strange changes in the paths. I am curious: why do animals ignore me when I am near an exit and also, who provides the resurrection at these same exits? Does anyone know what this is about?

::'''Jyrvie''': The animals ignore you when you're still in the tunnels. They don't notice you.

::'''Moniq''' : They ignore me while I am at the entrance to the tunnel, even if it is not yet open.

::'''Dorothee''': Just like in every teleporter zone

::'''Moniq''': I don't understand that, Dorothee. Have you studied it more closely?

::'''Craftjenn''': I perceive the passages more like vortices

::'''Moniq''': I have also heard many rumours, but it seems that no one knows anything.

::'''Byiet''': As a ranger, is the safe area larger than for any other homin?

::'''Dorothee''': Around each teleporter and vortex there is a safe area. It remains safe unless you enter the field of vision of an aggressive monster

::'''Moniq''': That's not an answer. How is it possible to have safe areas, as you call them?

::'''Meggy''': I think what Moniq is asking for is who is providing protection?

::'''Moniq''': Yes, I don't understand why the passages work differently than they did in the past

::'''Meggy''': Near a Kami or Karavan teleporter, everyone has their own protectors, but who protect the Rangers?

::Bittty: Maybe Atys herself? I have often thought that our world is much more alive than we thought.

::'''Moniq''': Go ahead, Tryroamer, talk if you have any information

::'''Apocamus''': Tryroamer, go ahead

::'''Achnar''': ( no, it's too late, we sleep: D)

::'''Tryroamer''': I listened to your discussion and thought a lot about it. If I may, I would like to share my thoughts with this assembly

::'''Tryroamer''': I'll keep it short

::There are other phenomena of a similar nature. I think it is possible that this is the case here. The ranger passage is like a black hole, it seems to me.

::'''Jyrvie''': It's true that you can't see well in the passages

::'''Tryroamer''': And its network has an even stronger effect when you are in the immediate vicinity

::'''Tryroamer''': My feeling is that animals feel it and prefer not to interfere with it. They stay away for their safety when they don't need to get close to it. Thank you for listening to me.

::'''Dorothee''': Wuaoi is a specialist in magnetism, you should ask him for more details

::'''Dorothee''': Moniq, the safe areas of vortices and TPs are safe because the atoms in your body enter into hyper-fast vibration and remain so until you move. So the monsters can't see you. This affects homins only because the frequency of magnetic pathways is tuned to homin DNA

::'''Apocamus''': Thank you Tryroamer

::'''Apocamus''': It is time for me to leave you...

::'''Moniq''': Dorothee talks about teleporters and Vortices... this would only apply if the paths were some kind of vortex.

::'''Dorothee''': That's what I think right now.

::'''Moniq''': That's one of the theories I've heard

::'''Apocamus''': ((((HRP: Next meeting will take place in 2 or 3 months))

::'''Achnar''': We'll ask Wuaoi for more explanation

::'''Moniq''': I hadn't had the opportunity to ask the question for a very long time

::'''Apocamus''': Perhaps you will know more at the next meeting?

::'''Moniq''' : I'd like to know where to look, everyone has only speculation to offer.

::'''Dorothee''': I also think that the Kamis and Karavan made similar discoveries a long time ago, and that their TPs are different ways of controlling ambient and deep magnetism

::'''Moniq''': Yes, I heard that.

::'''Zendae''': If I may... vortices are not always resurrection points, think of those in lakes.

::'''Moniq''': Good point

::'''Zendae''': It seems there is a rule, have you noticed it di amatakima?

::'''Achnar''': I think you can leave Apoc'

::'''Byiet''': Can you give up the idea of magnetism, this world has no metal for

::'''Moniq''': Byiet, So what do magical cartographers do?

::'''Apocamus''': The magnetism on Atys has nothing to do with metal, but with amber.

::'''Apocamus Dradius''': Good night, Rangers. (he respectfully greets)
::The present: Good night, Apocamus…

''Do'Ro drops down her yber pen. Wuaoi looked really tired. Apocamus is quite attractive for a Fyros... and full of energy... a little too much maybe...''

''She thinks about the water caravan (with byrrh why not ? so she would be sure Krill would come). She will have to remind Apocamus and Ubhal of these words of Wuaoi that she had the chance to read while correcting the proofs. :''
{{Quotation|Wuaoi Yai-Zhio, ''[[The Way of the Ranger/Chapter 4|The Way of the Ranger, Chapter 4]]''|
neutrality means that we do not favour one nation over another. It is not inaction, but equivalent actions. We also supported the Beer and Water Routes between Trykers and Fyros, and assisted the Zorai in their fight against the Goo. If the Fyros needed help with a noble task, we would offer it to them as well.}}

''She will also have to put her observations on tunnels, vortices and teleporters as well as collisions in order and discuss them with our researcher Zo'''

''A rain drop falls on her cheek. The sun is setting... It is time to go to the tower where she will spend the night before going back to Liberty Lake after submitting its report.''

'''This work is dedicated to [[Teeneemai]] and [[Wuaoi Yai-Zhio]].'''

::::'''Do'Ro'''

Rangers Assembly of Nivia 28, CA2 of Jena year 2603

2022-03-16T10:57:36Z

Ledania:

Help:Interwiki

2022-03-16T10:40:54Z

Ledania:

<noinclude>{{TIP|DE=4|EN=0|ES=1|FR=3|RU=1}}{{Trad
|DE = Help:Interwiki |DEs= 4
|EN = Help:Interwiki |ENs= 0
|ES = Help:Interwiki |ESs= 1
|FR = Help:Interwiki |FRs= 3
|RU = Help:Интервики |RUs= 1
|H =
|palette= Grey
|ref=
|com=
}}

<div style = "float:right;"> __TOC__</div>
</noinclude>
==Introduction==
[[Help:Interwiki |Interwiki]] is a [[:mediawikiwiki:MediaWiki|MediaWiki]] extension that allows to use internal links format (i.e. <nowiki>[[something]]</nowiki>) instead of external ones, to link to other languages pages and some external wikis such as [[:wikipedia:Wikipedia|Wikipedia]], [[:mediawikiwiki:MediaWiki|MediaWiki]]... 

It uses a prefix table to redirect addresses, wich is stored in the page: '''[[Special:Interwiki]]'''.

==Interlanguages Links==
===Link to a page in another language ===
:Syntax:
::<code>[[''':'''<language_code>''':'''<Full_page_name>]]</code>
Here, available languages codes are: <code>de</code>(🇩🇪) , <code>en</code>(🇬🇧 , 🇺🇲), <code>es</code>(🇪🇸), <code>fr</code> (🇫🇷, 🇧🇪, 🇨🇦) and <code>ru</code> (🇷🇺) and <code>atys</code> for '''Ryzom Commons''' (mostly the pictures) <ref>but interwikis work badly with common See for ex some tests on [[:fr:Utilisatrice:Craftjenn/NotesCJ#test_interwiki]] (nginx error messages) </ref>
:Example :
: [[:fr:Guilde:Cercle du Bois d'Almati|<nowiki>[[:fr:Guilde:Cercle du Bois d'Almati]]</nowiki>]]
*'''The leading '''":"''' is important''' (see below).
*Note that Interwiki/interlanguages links have a different color than the other internal links.

===The Trad Template===

The [[Template:Trad|Trad Template]] displays a small languages banner as on the right of this line, which flags, when displayed, are linking to other languages pages. It can also provide a translation status information. See the '''[[Template:Trad]] page''' for full documentation.
:Call:
<nowiki>{{Trad
|DE = Page |DEs= (translation status code)
|EN = Page |ENs=
|ES = Page |ESs=
|FR = Page |FRs=
|RU = Page |RUs=
|H = (1 for horizontal)
|palette= Theme
|ref= Page_link
|com= Comment
}}</nowiki>

===The "In Other Languages" Menu===
Interwiki allows to insert an ''"In Other Languages"'' Menu in the ''"Navigation Bar"''<ref>See image on [[:atys:File:FR nav toolbar trad 2020-06-14.png]], this menu is related to MediaWiki:Sidebar</ref> which provides links to translated pages exactly as the Trad template does. To do so, just insert blind links to the translated pages with the following syntax ''(no leading '''":"''' )'':
<nowiki>[[language_code:Full_Page_Name]]</nowiki> (i.e. with the namespace)
For example, this page's ''"In Other Languages"'' Menu is obtained with :
<nowiki>[[de:Help:Interwiki]]
[[en:Help:Interwiki]]
[[es:Help:Interwiki]]
[[fr:Help:Interwiki]]
[[ru:Help:Интервики]]</nowiki>
Note that the '''Help:''' namespace does not need to be translated <ref>More on namespaces on [[Wiki Technical Guide#Namespaces]]. When canonical name are the same, no need to translate ns. For ex: https://en.wiki.ryzom.com/w/api.php?action=query&meta=siteinfo&siprop=namespaces show all ns on English wiki.</ref>.

==Linking to Other Wikis==

Linking to other wikis follows the same rule, just use the [[Special:Interwiki]] prefixes instead of language ones; (wikipedia linking secifies the language ''AFTER'' the prefix).
 
:Examples:
{| class="wikitable"
|-
! internal format !! Links to
|-
| [[:wikipedia:NPC|<nowiki>[[:wikipedia:NPC]]</nowiki>]] || https://en.wikipedia.org/wiki/NPC
|-
| [[:wikipedia:de:Nicht-Spieler-Charakter|<nowiki>[[:wikipedia:de:Nicht-Spieler-Charakter]]</nowiki>]] || https://de.wikipedia.org/wiki/Nicht-Spieler-Charakter
|-
| [[:mediawikiwiki:Help:Contents|<nowiki>[[:mediawikiwiki:Help:Contents]]</nowiki>]] || https://www.mediawiki.org/wiki/Help:Contents
|}

==Inter-Languages and Inter-Wiki Transclusion==
Transclusion of other languages are also possible. To include a page of another language just use:

::<code>{{''':'''<language_code>''':'''<Full_page_name>}}</code> or, more generally : {{''':'''<prefix>''':'''<Full_page_name>}}
thus exactly the same as if the page was in the same language space, but the beginning language code. Please note that the <code><nowiki><noinclude></noinclude></nowiki></code> and <code><nowiki><includeonly></includeonly></nowiki></code> seem to be ignored, and the whole page is transcluded.

As an example, this page is not translated but transcluded to the other languages instead ( this could change in the future).

==Notes and links ==
===Mediawiki Interwiki Documentation===
*[[:mediawikiwiki:Extension:Interwiki|Extension:Interwiki]]
*[[:mediawikiwiki:Manual:Interwiki|Manual:Interwiki]]
*[[:mediawikiwiki:Manual:interwiki table|Interwiki table]]
*[[:mediawikiwiki:Interwiki cache|Interwiki cache]]

===Note by --[[User:Dorothée|Dorothée]] ([[User talk:Dorothée|talk]]) 10:28, 13 June 2020 (CEST)===
* <s>At the moment, ''only transclusion of english pages are possible''</s>
* Use of templates of other languages ''by transclusion'' is not possible, nor copying a page with '''"subst:"'''. Copying them into their own page is thus required. (upd --[[User:Dorothée|Dorothée]] ([[User talk:Dorothée|talk]]) 07:14, 29 August 2021 (CEST))

<noinclude>
{{Reflist|subpages=}}
{{clear}}
[[de:Help:Interwiki]] [[en:Help:Interwiki]] [[es:Help:Interwiki]] [[fr:Help:Interwiki]] [[ru:Help:Интервики]] [[Category:WikipAtys]] [[Category:Help]] {{last version link|Help:Interwiki}}</noinclude>

Help:Interwiki

2022-03-15T18:55:05Z

Ledania:

<noinclude>{{TIP|DE=3|EN=0|ES=1|FR=3|RU=1}}{{Trad
|DE = Help:Interwiki |DEs= 3
|EN = Help:Interwiki |ENs= 0
|ES = Help:Interwiki |ESs= 1
|FR = Help:Interwiki |FRs= 3
|RU = Help:Интервики |RUs= 1
|H =
|palette= Grey
|ref=
|com=
}}

<div style = "float:right;"> __TOC__</div>
</noinclude>
==Introduction==
[[Help:Interwiki |Interwiki]] is a [[:mediawikiwiki:MediaWiki|MediaWiki]] extension that allows to use internal links format (i.e. <nowiki>[[something]]</nowiki>) instead of external ones, to link to other languages pages and some external wikis such as [[:wikipedia:Wikipedia|Wikipedia]], [[:mediawikiwiki:MediaWiki|MediaWiki]]... 

It uses a prefix table to redirect addresses, wich is stored in the page: '''[[Special:Interwiki]]'''.

==Interlanguages Links==
===Link to a page in another language ===
:Syntax:
::<code>[[''':'''<language_code>''':'''<Full_page_name>]]</code>
Here, available languages codes are: <code>de</code>(🇩🇪) , <code>en</code>(🇬🇧 , 🇺🇲), <code>es</code>(🇪🇸), <code>fr</code> (🇫🇷, 🇧🇪, 🇨🇦) and <code>ru</code> (🇷🇺) and <code>atys</code> for '''Ryzom Commons''' (mostly the pictures) <ref>but interwikis work badly with common See for ex some tests on [[:fr:Utilisatrice:Craftjenn/NotesCJ#test_interwiki]] (nginx error messages) </ref>
:Example :
: [[:fr:Guilde:Cercle du Bois d'Almati|<nowiki>[[:fr:Guilde:Cercle du Bois d'Almati]]</nowiki>]]
*'''The leading '''":"''' is important''' (see below).
*Note that Interwiki/interlanguages links have a different color than the other internal links.

===The Trad Template===

The [[Template:Trad|Trad Template]] displays a small languages banner as on the right of this line, which flags, when displayed, are linking to other languages pages. It can also provide a translation status information. See the '''[[Template:Trad]] page''' for full documentation.
:Call:
<nowiki>{{Trad
|DE = Page |DEs= (translation status code)
|EN = Page |ENs=
|ES = Page |ESs=
|FR = Page |FRs=
|RU = Page |RUs=
|H = (1 for horizontal)
|palette= Theme
|ref= Page_link
|com= Comment
}}</nowiki>

===The "In Other Languages" Menu===
Interwiki allows to insert an ''"In Other Languages"'' Menu in the ''"Navigation Bar"''<ref>See image on [[:atys:File:FR nav toolbar trad 2020-06-14.png]], this menu is related to MediaWiki:Sidebar</ref> which provides links to translated pages exactly as the Trad template does. To do so, just insert blind links to the translated pages with the following syntax ''(no leading '''":"''' )'':
<nowiki>[[language_code:Full_Page_Name]]</nowiki> (i.e. with the namespace)
For example, this page's ''"In Other Languages"'' Menu is obtained with :
<nowiki>[[de:Help:Interwiki]]
[[en:Help:Interwiki]]
[[es:Help:Interwiki]]
[[fr:Help:Interwiki]]
[[ru:Help:Интервики]]</nowiki>
Note that the '''Help:''' namespace does not need to be translated <ref>More on namespaces on [[Wiki Technical Guide#Namespaces]]. When canonical name are the same, no need to translate ns. For ex: https://en.wiki.ryzom.com/w/api.php?action=query&meta=siteinfo&siprop=namespaces show all ns on English wiki.</ref>.

==Linking to Other Wikis==

Linking to other wikis follows the same rule, just use the [[Special:Interwiki]] prefixes instead of language ones; (wikipedia linking secifies the language ''AFTER'' the prefix).
 
:Examples:
{| class="wikitable"
|-
! internal format !! Links to
|-
| [[:wikipedia:NPC|<nowiki>[[:wikipedia:NPC]]</nowiki>]] || https://en.wikipedia.org/wiki/NPC
|-
| [[:wikipedia:de:Nicht-Spieler-Charakter|<nowiki>[[:wikipedia:de:Nicht-Spieler-Charakter]]</nowiki>]] || https://de.wikipedia.org/wiki/Nicht-Spieler-Charakter
|-
| [[:mediawikiwiki:Help:Contents|<nowiki>[[:mediawikiwiki:Help:Contents]]</nowiki>]] || https://www.mediawiki.org/wiki/Help:Contents
|}

==Inter-Languages and Inter-Wiki Transclusion==
Transclusion of other languages are also possible. To include a page of another language just use:

::<code>{{''':'''<language_code>''':'''<Full_page_name>}}</code> or, more generally : {{''':'''<prefix>''':'''<Full_page_name>}}
thus exactly the same as if the page was in the same language space, but the beginning language code. Please note that the <code><nowiki><noinclude></noinclude></nowiki></code> and <code><nowiki><includeonly></includeonly></nowiki></code> seem to be ignored, and the whole page is transcluded.

As an example, this page is not translated but transcluded to the other languages instead ( this could change in the future).

==Notes and links ==
===Mediawiki Interwiki Documentation===
*[[:mediawikiwiki:Extension:Interwiki|Extension:Interwiki]]
*[[:mediawikiwiki:Manual:Interwiki|Manual:Interwiki]]
*[[:mediawikiwiki:Manual:interwiki table|Interwiki table]]
*[[:mediawikiwiki:Interwiki cache|Interwiki cache]]

===Note by --[[User:Dorothée|Dorothée]] ([[User talk:Dorothée|talk]]) 10:28, 13 June 2020 (CEST)===
* <s>At the moment, ''only transclusion of english pages are possible''</s>
* Use of templates of other languages ''by transclusion'' is not possible, nor copying a page with '''"subst:"'''. Copying them into their own page is thus required. (upd --[[User:Dorothée|Dorothée]] ([[User talk:Dorothée|talk]]) 07:14, 29 August 2021 (CEST))

<noinclude>
{{Reflist|subpages=}}
{{clear}}
[[de:Help:Interwiki]] [[en:Help:Interwiki]] [[es:Help:Interwiki]] [[fr:Help:Interwiki]] [[ru:Help:Интервики]] [[Category:WikipAtys]] [[Category:Help]] {{last version link|Help:Interwiki}}</noinclude>

A story I was told as a child

2022-03-15T14:19:15Z

Ledania:

<noinclude>{{Trad
|DE =Eine Geschichte, die mir als Kind erzählt wurde
|DEs =4
|ES =
|ESs = 5
|EN = A story I was told as a child
|ENs = 4
|FR =Une histoire qu'on me racontait petit
|FRs =0
|RU =
|RUs = 5
|H = 1
|palette=zorai
}}</noinclude>
'''It's a story that was told to me when I was a little child, to avoid me going for a walk alone…'''

There is an abandoned village in the Nexus.

Who created it? Why did the people leave? No one knows. On some nights you can see the fires smoking, the lanterns shining in the shelters that remain…

But there is nothing left in the morning.

It is only on the darkest nights that these little flames are seen. Nights like those when It is only on the darkest nights that these little flames are seen. Nights like those when the wind of Anlor Winn blows.

One day, a driller was surprised by a sudden storm. He took refuge in the village, despite his sinister reputation.There, in his wobbly shelter, shaken by the wind, he saw countless flames ignite. They were carried by translucent kamis, whose bones could be seen. These kamis came and went within the village whispering. Then they gathered in a circle in the center of the village.

A bit like us tonight.

The driller was very anxious, and did not move from his hideout. Then one of the kami spoke. His voice was that of the storm:

<q> <big>There is someone missing from our circle!</big> </q>

Nothing was moving. The kami said again:

<q> <big>Our circle is missing someone! And if he doesn't come, then death will spread over this country.</big> </q>

But again nothing was moving.

<q> <big>If our circle is not complete, all life on Atys will join the shadows, thundered the kami.</big> </q>

So the terrified driller thought that if anyone was going to complete the circle, it had to be him.

He wasn't a kami or a spirit, but he was there. So he joined the circle and sat down. He spent all night with the kami, in the cold and wind.

What was said, no one knows.

When dawn came, he was just another skeleton in the ruins…
{{Couillard}}
<div align=center>'''There is no moral to this story, just two questions:'''</div>

<div align=center>Was it better to avoid the ruins that night? Or did this homin and his courage save Atys?</div>

----
''This tale has been told by Haokan-ito on [[Anlor Winn/Storytelling JA2610|2610 Anlor Winn Convention]].'' (OOC : Halloween 2020)''
----

<noinclude>
[[Category:Tales]]
[[Category:Halloween]]
{{Portal|Literature}}
{{Portal|Animation}}
</noinclude>

The Wicked Wind

2022-03-15T13:53:18Z

Ledania:

<noinclude>{{Trad
|DE =Der tückische Wind
|DEs =4
|ES =El Viento Maligno
|ESs = 5
|EN =The Wicked Wind
|ENs = 4
|FR =Le Vent Mauvais
|FRs =0
|RU =Злой Ветер
|RUs = 5
|H =
|palette=tryker
}}</noinclude>
[[File:Krill telling.jpg|800px|center]]
{{Clear}}
'''''The Wind is closing in.'''''
:But Mac'Eoppy doesn't care. He prepares his caravan.
:Mac'Eoppy believes in Jena, and in the Karavan. Not in those ridiculous superstitions of drunken Trykers.
:He says seelagan to his wife, and joyfully leaves his village to increase his fortune.

'''''The Wind whispers.'''''
:The caravan is progressing well, and Mac'Eoppy is happy.
:He has already avoided a customs control, and his profit is increasing accordingly.
:The caravan progresses well, and Mac'Eoppy ignores the Wind. He counts the dappers in his head.

'''''The Wind bulks up.'''''
:And lifts the sawdust. He slaps and whips those who stand in its way.
:The mektoubs huddle together, and the homins take shelter near them.
:But Mac'Eoppy sees only an unexpected storm, and continues to move forward.

'''''The Wind is dropping.'''''
:A little. And in the debris of the storm, two mektoubs are missing.
:Broken bones, torn skins, putrefied flesh, the two poor beasts are quickly found.
:But Mac'Eoppy blames the wild beasts, and he only regrets the lost loads

'''''The Wind soughs.'''''
:Words of hatred and violence. And the caravan moves slowly.
:Mac'Eoppy is looking for the one who lost the two pack animals.
:And mistrust, and suspicion, spread in Mac'Eoppy's heart.

'''''The Wind sings.'''''
:One of the mektoubers has vanished, and Mac'Eoppy is contented.
:He's the culprit, of course. A rotten fruit that won't spoil the others.
:Mac'Eoppy carries on his way, not looking for him anymore.

'''''The Wind blackens.'''''
:The bandits were looking for the village. They found the caravan.
:They torture the homins, and plunder the mektoubs.
:Mac'Eoppy cries and does not hear the Wind in the midst of the suffering screams.

'''''The Wind has fallen.'''''
:For an hour, maybe a day. Finally a little respite.
:Mac'Eoppy and a few others managed to flee, abandoning injured ones.
:But the bandits know where to find the village, and intend to take revenge.

'''''The Wind whistles.'''''
:The fugitives move forward as they can, hands on their ears.
:Mac'Eoppy didn't see the two who fell, struck down by predators.
:He only thinks about his wife and his village. To get there before the bandits do..

'''''The Wind spits.'''''
:And the sawdust it lifts and throws, tears the skin off the homins.
:Mac'Eoppy has sheltered behind his aides until they fell one after the other.
:Now he moves forward alone, exhausted, mad with pain.

'''''The Wind howls.'''''
:And its voice fills Mac'Eoppy's head.
:He only has one thought left. To find his wife. To protect her.
:Arrive before the bandits. Go forward. Go forward. Go forward.

'''''The Wind falls silent.'''''
:And Mac'Eoppy finally sees his village. His house.
:Everything is quiet. Too quiet. Would the bandits have already taken everything.
:Slowly, he slips into the night, reaches the door of his house.

'''''The Wind listens.'''''
:Mac'Eoppy saw a shape moving.
:Screaming, he bounded. To protect his wife. To forget he betrayed his friends.
:He hits, he beats, he strikes, with all his limbs, with all his strength.

'''''The Wind sneers.'''''
:Neighbors come running up, asking what's going on. Who killed Mac'Eoppy's wife?
:The murderer ran away as discovering his victim.
:Shade in the night. Meeting the bandits who arrive.

----
''This tale♦ has been told by [[User:Krill|Krill]] on [[Anlor Winn/Storytelling JA2610|2610 Anlor Winn Convention]].'' (OOC : Halloween 2020)'' 
'''<big>♦</big>''' « ''Anlor Winn'' » is the [[Portal:Tryker/Language|Tyll]] for english « Wicked Wind »
----
<noinclude>
[[Category:Tales]]
[[Category:Halloween]]
{{Portal|Literature}}
{{Portal|Animation}}
</noinclude>