https://en.wiki.ryzom.com/w/api.php?action=feedcontributions&feedformat=atom&user=AmosysEncyclopAtys - User contributions [en]2026-06-04T00:32:07ZUser contributionsMediaWiki 1.29.1https://en.wiki.ryzom.com/w/index.php?title=Patch_2020&diff=34469Patch 20202020-02-23T13:08:38Z<p>Amosys: top link harmozination</p>
<hr />
<div>{{Trad<br />
|DE = Patch 2020 |DEs=<br />
|EN = Patch 2020 |ENs=4<br />
|ES = Patch 2020 |ESs=<br />
|FR = Patch 2020 |FRs=0<br />
|RU = Patch 2020 |RUs=<br />
|H = <br />
|palette= Thème<br />
|ref=[[:fr:Patch 2020]]<br />
|com=First draft (EN and FR), coming soon, see [[Patch 2019]] for now.<br />
}}<br />
<big>What's up in [[New2019|2019]], [[New 2018|2018]], [[New2017|2017]] '''''back to [[User Manual]].'''''</big><br />
* Access the [https://board.ryzom.com/?controller=BoardViewController&action=readonly&token=c46b5ea0f37c83d155f3eacc3acf6956ee75cbfca4afa3f2c107fcb4e74d&from_index=1 Roadmap] with some [https://app.ryzom.com/app_forum/index.php?page=post%2Fview%2F186177&lang=en explanation]<br />
* https://bitbucket.org/ryzom/ <br />
== Big changes ==<br />
<big>Ryzom Chat (chat.ryzom.com), Facebook https://www.facebook.com/groups/2347192496/ and Twitter https://twitter.com/ryzom</big><br />
* 2020.02.19 [[Patch 00791]]<br />
*<br />
== Patch 2020.02.19 ==<br />
[[File:V3 MP Batiment Brique.png|left|20px|A much lighter package]] https://app.ryzom.com/app_forum/index.php?page=topic/view/30283/1&post198844=en#1<br />
{{:Patch 00791}}<br />
<br />
==References==<br />
--[[User:Craftjenn|CraftJenn, Ranger du Cercle du Bois d&#39;Almati]] ([[User talk:Craftjenn|talk]]) January 2020 (UTC)<br />
===Sources===<br />
* [http://app.ryzom.com/app_forum/index.php?page=forum/view/1839/1 Forum, Official news]<br />
<br />
<!-- Ceci est un exemple de commentaire invisible à l'affichage.<br />
[[Category:Featured articles]]<br />
--> <br />
<br />
<br />
<br />
<noinclude><br />
----<br />
<references/><br />
----<br />
{{Portal|Forge|Gameplay}}<br />
[[Category:Updates]]</noinclude></div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Patch_2019&diff=34468Patch 20192020-02-23T13:07:01Z<p>Amosys: TOC under links, as orther pages + add link to Patch 2020</p>
<hr />
<div>{{Trad<br />
|DE = Patch 2019 |DEs=5<br />
|EN = Patch 2019 |ENs=4<br />
|ES = Patch 2019 |ESs=5<br />
|FR = Patch 2019 |FRs=0<br />
|RU = Patch 2019 |RUs=5<br />
|H = <br />
|palette= Alert<!-- <br />
|ref=[[:fr:Patch 2019]]<br />
|com=Thanks to read and correct this English version. --><br />
}}<br />
<big>What's up in [[Patch 2020]], [[New 2018|2018]], [[New2017|2017]] '''''back to [[User Manual]].'''''</big><br />
* Access the [https://board.ryzom.com/?controller=BoardViewController&action=readonly&token=c46b5ea0f37c83d155f3eacc3acf6956ee75cbfca4afa3f2c107fcb4e74d&from_index=1 Roadmap] with some [https://app.ryzom.com/app_forum/index.php?page=post%2Fview%2F186177&lang=en explanation]<br />
* https://bitbucket.org/ryzom/ <br />
__TOC__<br /><br />
<br />
== Big 2019 changes ==<br />
<big>Ryzom Chat (chat.ryzom.com), Facebook https://www.facebook.com/groups/2347192496/ and Twitter https://twitter.com/ryzom</big><br />
<br />
<br />
<br />
To learn more about upcoming additions: [[Patch_2019/Forge_Reports#Oct_28th_2019]] and [[Patch_2019/Forge_Reports#2019_Sept]].<br />
=== Late 2019 - JA 2606 ===<br />
====Daily missions (December 2,2019)====<br />
[[File:Daily missions -1-EN.png|300px|thumb|right|Daily Missions main window]]<br />
;Basic principle:<br />
Every day, you have the opportunity to carry out seven missions in the order of your choice, randomly selected from all the "Task" missions and/or "Occupation product donation" missions.A filtering option allows you to restrict the select-able missions according to the fames that you do not want to lower or raise.You also have the option of completing only certain types of missions, but de-selecting missions may have an impact on your final gain.You can abandon a mission at any time if you do not want to do it or do it later. However, this one is not replaced by another and will remain in the list of missions proposed for today.For the moment, Prime Roots missions are not available (who said "fiuuu!"?)<br />
;Filtering options:<br />
''Four filtering options are available:''<br />
* Filtering of the area in which to perform each type of mission:<br />
*: Select here the level of the area (50 --> 250) in which you want to perform each type of mission (craft, forage, combat, exploration). If you choose the "None" option, then no mission of this kind will be offered to you.<br />
:: [Note] Selecting only one type of mission will reduce the reward.<br />
* Filtering of fame that should not decrease:<br />
*:Here, you have the option to apply a filter to remove from the list those missions that would cause you to lose some of your fame. Thus, a Ranger should check all the boxes in the "Fame that you do not want to decrease" line.[[File:Daily missions -2-EN.png|300px|thumb|right|Filters window]]<br />
* Filtering of fame that should not increase:<br />
*: Here, you have an option to apply filter to remove from the list those missions that would cause you or win some fame. Thus, a Marauder should check all the boxes in the "Fame that you do not want to increase" line. <br />
* Filtering of occupations:<br />
*: Filter here which occupations can be offered to you. If you choose all of them, a maximum of four occupation missions can be randomly selected. Choosing all occupations considerably increases the reward.<br />
:: [Note] Occupation missions do not require that you have the occupation active but only occupation products to give, including those obtained by exchange or purchase.<br />
<br />
;The rewards:<br />
For each completed mission, you will be able to choose from three possible rewards:<br />
*Dappers<br />
*Involvement (Elyps)<br />
*Choice tokens for the wheel<br />
You can choose if you wish a different reward for each completed mission. The more daily missions you complete, the higher the reward rate will be.<br />
<br />
====From Involvement to Elyps (patch 764 2019/12/22)====<br />
https://app.ryzom.com/app_forum/index.php?page=topic/view/30121/1&post197888=en<br />
<br />
For some time now, you can earn Involvementpoints during dynamic events (DE). Other rewards will soon be added to those you already earn from official merchants (Imperial of Pyr, Royal of Yrkanis, Federal of Fairhaven, Dynastic of Zora and Marauder of the Camp).<br />
;Currency reform:<br />
The numbers of Involvement points distributed so far are very high ones, to the extent that we noticed players have now some difficulty to read them. That is the reason why the introduction of these new rewards will be coupled with a semblance of “currency reform”. Namely:<br />
* The number of Involvement points accumulated by each player character since the dynamic events were brought in game will be reduced to the hundredth of the current number;<br />
* The number of Involvement points distributed during a dynamic event will now be lower and will also depend on the nature of the said event;<br />
* The unit price in points of Involvement of rewards acquired from an official merchant will now also be divided by 100, thus exactly offsetting the loss mentioned above.<br />
* In order to make this reduction in the price of rewards arithmetically possible, official merchants will no longer sell their items by the piece, but in batches. Thus:<br />
* Generic raw materials and experience catalysers will now be offered for sale in 999 unit batches (i.e. a complete pack in Bag);<br />
* The sap crystals will now be offered for sale in 100 unit batches.<br />
<br />
;Nature of the new rewards:<br />
To start (other rewards will be added later), the Involvement points will allow their owners to get, in addition to the rewards already available:<br />
* From their official merchant, the reduction of the remainder of their death penalty by 25, 50, 75 or 100%;<br />
* From a groom in a capital city (or Marauder Camp), the (re)naming of their animals (mount, packer or Zig) with their own name, a random name or a name of their choice.<br />
* The cost in points of Involvement of this (re)naming (said “inscription in the register” in game) of an animal under a name chosen by its owner will first (at the moment this new reward will be introduced in game) be particularly high for all interested owners, but will decrease regularly thereafter, down to a stable, definitive cost.<br />
<br />
;About Involvement:<br />
These changes are for us an opportunity to clarify (or recall) the meaning of the Involvement points, or, more accurately, their inclusion in roleplaying and their interpretation by the Lore.In the same way that the dappers paid to ''New Horizons'' allow everyone to travel from one city to another in a few seconds thanks to a “time ellipsis”, the Involvement points allow actions that are usually time-consuming to perform in a few seconds.Therefore, they can be seen as units of suspended time allowing their owner to perform in a flash various and varied tasks, such as:<br />
* Carry out missions on behalf of a nation or organization represented by its official merchant, missions whose success is, as usual, rewarded; <br />
* Perform the actions usually required to reduce (until extinction) one's death penalty.<br />
<br />
It is therefore this interpretation that allows us to imagine, as “rewards” provided by the Involvement points, a wide range of new activities and capabilities...And leads us to rename the said "point": it becomes the '''Elyps'''!<br />
<br />
=== Patch 750 ===<br />
[[File:Ulukyn-portrait.png|100px|right|Saint Ulu Kyn]]'''25/26 Sept 2019''': Ulu works. [https://app.ryzom.com/app_forum/index.php?page=topic/view/29991/1 Announce on the forum.]<br />
* first phase of the migration of the game server to a new, more efficient machine. <br />
* '''Resolved the Friday, 27th''' (2pm French time): API not yet migrated => small gap between the atysian time and bm.<br />
* Removal of the 15-year-old island<br />
* Corrections: Nexus map is the right one, the underwear came back...<br />
<br />
<br />
<br />
'''2019-5-18''' Ryzom's 15 Years Celebration see https://app.ryzom.com/app_forum/index.php?page=topic/view/29956/1&post197059=en#1 in short:[[File:Confetis.gif|thumb]]<br />
* New visual elements for the Island<br />
* New rewards<br />
<br />
*Added display item buffs and enchant info directly on icon<br />
*Added target closest landmark command ('''/lmtar''')<br />
*Added set compass to target mode after successful /tar command<br />
* ingame browser improvements<br />
* Updated info behavior for healed sap and stamina<br />
*Updated unknown tribe fame visuals<br />
*Updated missions icons to be distinct but not confusing with nations backgrounds<br />
<br />
=== Patch - 2019-06-26 ===<br />
Various balancing of classic missions:<br />
* Reduction of the loss of reputation per mission for non-marauders.<br />
* Addition of a maximum limit of fame that can be won or lost per mission.<br />
* Correction of waiting times to resume a completed mission.<br />
* Enhancement of classic craft missions.<br />
[[File:V3 MP Batiment Brique.png|left|20px|A much lighter package]]Changes to upgrade the "camp tour" missions (Dappers, Nation Points): decrease in the weight of a package, in order to be able to carry out the mission without a Mektoub.<br />
<br />
More on https://app.ryzom.com/app_forum/index.php?page=topic/view/29804/1&post196134=en#1<br />
<br />
=== JY 2603 patch ===<br />
'''The 21th June''' Update on official forum [https://app.ryzom.com/app_forum/index.php?page=topic/view/29797/1#1 Revaluation of the game's missions to expand your fun].<br />
<br />
'''The 28th May''' Patch 745 is available. Fix the matis<->fyros fame switch and Nexus map.<br />
<br />
For US: '''May, 17th May''' after 22:00 UTC, and May 18th after midnight CEST. To [[Patch 2019/JY 2603 Documentation|JY 2603 Documentation]] (work in progress).<br />
[[File:PR flyer JY2603 en600.png|frame|center]]<br />
<br />
In short ([https://app.ryzom.com/app_forum/index.php?page=topic/view/29692/1&post195145=en#1 see full message on the official forum]), a client, data and server patching and a restart of the game server :<br />
<br />
====Additions:====<br />
* new interface for teleportation at Kamis and Karavan altars, Option to automatically rebuy a Kami or Kara pact after a TP (requires max fame)<br />
* ZIG me up: option to put a Zig in the bag, your Zig can be teleported with you<br />
* team Invite button in Guild Member List and Friend List<br />
* welcome message in chat channels<br />
<br />
====Improvements:====<br />
* Kami and Karavan teleport pacts no longer have weight/bulk in your bag<br />
* Ryzom installer (new URLs for download, erasing of a profile on MAC or Linux debugged)<br />
* New fresh backgrounds for icons<br />
* landmarks stored in XML file instead of ICFG file (meaning editable out of game)<br />
* new underwear icons (they now show the right color)<br />
<br />
This patch also includes the results of the work done on Dynamic Events (DE), New Horizons (NH) and the target command.<br /><br />
*Dynamic Events: addition of the "Kitin Invasion", "Puzzle" Dynamic Event, a new button in the Map (to display all Dynamic Events, with a new a blue round icon)<br />
*New Horizons: merger of New Horizons and Brotherhood of the Fortunate Gubani; global limit for "Support Missions" (fame rewards) removed; 1 000 dappers for all (whatever their fame)...<br />
*Target command now supports keyword search (e.g. for a yubo) as follows:<br />
** /tar yubo -- no quotes, target closest entity that contains 'yubo' in its name;<br />
** /tar suckling yubo -- no quotes, target closest entity that contains both 'suckling' and 'yubo' in its name;<br />
** Order not important, full words not needed '/tar y kling' would be a match. Also /tar "ora" -- with quotes, Will target an entity who's name '''starts''' with 'ora', as currently /tar "suckling yubo" -- with quotes, targets an entity who's name starts with 'suckling yubo';<br />
** some current old macros may need quotes now for short keywords, i.e. 'ora', but existing macros using quotes will continue to work.<br />
<br />
====Addendum: Evolution of hardware infrastructure====<br />
The month of March and the beginning of April were the occasion for a spring cleaning, including:<br />
* the moving of the billing server to https://account.ryzom.com<br />
* the migration of Ryzom Chat to another server while retaining its URL: https://chat.ryzom.com.<br />
* the migration of the Yubo server to a new, more powerful machine; it is now dedicated to the tests required by ongoing developments;<br />
* the installation, identical to that of Yubo, of a new server called Gingo, which hosts the tests for acceptance of completed developments before they are put into operation on Atys; this is the pre-production server whose implementation was long overdue;<br />
<br />
The next step in the hardware reconfiguration of the platform will see the migration of Atys, the game server, to new higher performing machine and the confirmation of Gingo as the Atys mirror server facilitating the application of patches and providing a rescue solution in the event of a failure of the latter.<br />
The Ryzom Team remains at your disposal for any additional information, and best wishes to you!<br />
<br />
More on the official forum https://app.ryzom.com/app_forum/index.php?page=topic/view/29692/1&post195145=en#1<br />
<br />
=== Jena Year 2602 Patch v3.5.0 ===<br />
[[File:Flyer1902 EN 600px.png|frame|center]]<br />
On the forum Patch 3.5.0 - 2019-02-08 https://app.ryzom.com/app_forum/index.php?page=topic/view/29373/1&post192850=en#1<br />
<br />
In very very short : a client, data and server patch + a restart of the game server, on February 8th, 2019 :<br />
* New rewards at Wheel of Fortune<br />
* [[Guild Island|Guild Islands]]<br />
* Yubokin comes to settle on the island of Silan<br />
* Change in OP battles: Removal of the neutral status during the battle<br />
* Ranger Gameplay balance, Marauder Improvments<br />
* Clients Improvements<br />
<br />
As an example of lovely Improvements : '''UI-Scale for all Clients''', let's have a look in System / Configuration / Graphics / General : <br />
<gallery><br />
Ech 1.5 2019-02-09.png|A big 1.50<br />
Ech 1.05 2019-02-09.png|Bigger at 1.05<br />
Ech1 2019-02-09.png|'''Normal value''' at 1.00<br />
Ech 0.95 2019-02-09.png|Smaller at 0.95<br />
</gallery><br />
It goes from 0.80 to 2.00.<br />
<br />
<br />
And new Inventory features, with a better quality filter (here, only mats, from q 50 to q 200) <br />
[[File:FiltreI2019-02-09.png|frameless]]<br />
<br />
<br />
To [[User:Craftjenn/Discovery of guild islands|Discovery of guild islands]], by CraftJenn.<br />
<br />
== Forge reports ==<br />
See [[Patch 2019/Forge Reports]].<br />
<br />
==References==<br />
--[[User:Craftjenn|CraftJenn, Ranger du Cercle du Bois d&#39;Almati]] ([[User talk:Craftjenn|talk]]) 10:18, 28 January 2019 (UTC)<br />
===Sources===<br />
* [http://app.ryzom.com/app_forum/index.php?page=forum/view/1839/1 Forum, Official news]<br />
<br />
<br />
[[Category:Featured articles]]<br />
<br />
<br />
<noinclude>{{Portal|Forge|Gameplay}}<br />
[[Category:Updates]][[Category:Game updates 2019]] </noinclude></div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Patch_2019&diff=34467Patch 20192020-02-23T13:05:42Z<p>Amosys: </p>
<hr />
<div>{{Trad<br />
|DE = Patch 2019 |DEs=5<br />
|EN = Patch 2019 |ENs=4<br />
|ES = Patch 2019 |ESs=5<br />
|FR = Patch 2019 |FRs=0<br />
|RU = Patch 2019 |RUs=5<br />
|H = <br />
|palette= Alert<!-- <br />
|ref=[[:fr:Patch 2019]]<br />
|com=Thanks to read and correct this English version. --><br />
}}__TOC__<br /><br />
<big>What's up in [[Patch 2020]], [[New 2018|2018]], [[New2017|2017]] '''''back to [[User Manual]].'''''</big><br />
* Access the [https://board.ryzom.com/?controller=BoardViewController&action=readonly&token=c46b5ea0f37c83d155f3eacc3acf6956ee75cbfca4afa3f2c107fcb4e74d&from_index=1 Roadmap] with some [https://app.ryzom.com/app_forum/index.php?page=post%2Fview%2F186177&lang=en explanation]<br />
* https://bitbucket.org/ryzom/ <br />
== Big 2019 changes ==<br />
<big>Ryzom Chat (chat.ryzom.com), Facebook https://www.facebook.com/groups/2347192496/ and Twitter https://twitter.com/ryzom</big><br />
<br />
<br />
<br />
To learn more about upcoming additions: [[Patch_2019/Forge_Reports#Oct_28th_2019]] and [[Patch_2019/Forge_Reports#2019_Sept]].<br />
=== Late 2019 - JA 2606 ===<br />
====Daily missions (December 2,2019)====<br />
[[File:Daily missions -1-EN.png|300px|thumb|right|Daily Missions main window]]<br />
;Basic principle:<br />
Every day, you have the opportunity to carry out seven missions in the order of your choice, randomly selected from all the "Task" missions and/or "Occupation product donation" missions.A filtering option allows you to restrict the select-able missions according to the fames that you do not want to lower or raise.You also have the option of completing only certain types of missions, but de-selecting missions may have an impact on your final gain.You can abandon a mission at any time if you do not want to do it or do it later. However, this one is not replaced by another and will remain in the list of missions proposed for today.For the moment, Prime Roots missions are not available (who said "fiuuu!"?)<br />
;Filtering options:<br />
''Four filtering options are available:''<br />
* Filtering of the area in which to perform each type of mission:<br />
*: Select here the level of the area (50 --> 250) in which you want to perform each type of mission (craft, forage, combat, exploration). If you choose the "None" option, then no mission of this kind will be offered to you.<br />
:: [Note] Selecting only one type of mission will reduce the reward.<br />
* Filtering of fame that should not decrease:<br />
*:Here, you have the option to apply a filter to remove from the list those missions that would cause you to lose some of your fame. Thus, a Ranger should check all the boxes in the "Fame that you do not want to decrease" line.[[File:Daily missions -2-EN.png|300px|thumb|right|Filters window]]<br />
* Filtering of fame that should not increase:<br />
*: Here, you have an option to apply filter to remove from the list those missions that would cause you or win some fame. Thus, a Marauder should check all the boxes in the "Fame that you do not want to increase" line. <br />
* Filtering of occupations:<br />
*: Filter here which occupations can be offered to you. If you choose all of them, a maximum of four occupation missions can be randomly selected. Choosing all occupations considerably increases the reward.<br />
:: [Note] Occupation missions do not require that you have the occupation active but only occupation products to give, including those obtained by exchange or purchase.<br />
<br />
;The rewards:<br />
For each completed mission, you will be able to choose from three possible rewards:<br />
*Dappers<br />
*Involvement (Elyps)<br />
*Choice tokens for the wheel<br />
You can choose if you wish a different reward for each completed mission. The more daily missions you complete, the higher the reward rate will be.<br />
<br />
====From Involvement to Elyps (patch 764 2019/12/22)====<br />
https://app.ryzom.com/app_forum/index.php?page=topic/view/30121/1&post197888=en<br />
<br />
For some time now, you can earn Involvementpoints during dynamic events (DE). Other rewards will soon be added to those you already earn from official merchants (Imperial of Pyr, Royal of Yrkanis, Federal of Fairhaven, Dynastic of Zora and Marauder of the Camp).<br />
;Currency reform:<br />
The numbers of Involvement points distributed so far are very high ones, to the extent that we noticed players have now some difficulty to read them. That is the reason why the introduction of these new rewards will be coupled with a semblance of “currency reform”. Namely:<br />
* The number of Involvement points accumulated by each player character since the dynamic events were brought in game will be reduced to the hundredth of the current number;<br />
* The number of Involvement points distributed during a dynamic event will now be lower and will also depend on the nature of the said event;<br />
* The unit price in points of Involvement of rewards acquired from an official merchant will now also be divided by 100, thus exactly offsetting the loss mentioned above.<br />
* In order to make this reduction in the price of rewards arithmetically possible, official merchants will no longer sell their items by the piece, but in batches. Thus:<br />
* Generic raw materials and experience catalysers will now be offered for sale in 999 unit batches (i.e. a complete pack in Bag);<br />
* The sap crystals will now be offered for sale in 100 unit batches.<br />
<br />
;Nature of the new rewards:<br />
To start (other rewards will be added later), the Involvement points will allow their owners to get, in addition to the rewards already available:<br />
* From their official merchant, the reduction of the remainder of their death penalty by 25, 50, 75 or 100%;<br />
* From a groom in a capital city (or Marauder Camp), the (re)naming of their animals (mount, packer or Zig) with their own name, a random name or a name of their choice.<br />
* The cost in points of Involvement of this (re)naming (said “inscription in the register” in game) of an animal under a name chosen by its owner will first (at the moment this new reward will be introduced in game) be particularly high for all interested owners, but will decrease regularly thereafter, down to a stable, definitive cost.<br />
<br />
;About Involvement:<br />
These changes are for us an opportunity to clarify (or recall) the meaning of the Involvement points, or, more accurately, their inclusion in roleplaying and their interpretation by the Lore.In the same way that the dappers paid to ''New Horizons'' allow everyone to travel from one city to another in a few seconds thanks to a “time ellipsis”, the Involvement points allow actions that are usually time-consuming to perform in a few seconds.Therefore, they can be seen as units of suspended time allowing their owner to perform in a flash various and varied tasks, such as:<br />
* Carry out missions on behalf of a nation or organization represented by its official merchant, missions whose success is, as usual, rewarded; <br />
* Perform the actions usually required to reduce (until extinction) one's death penalty.<br />
<br />
It is therefore this interpretation that allows us to imagine, as “rewards” provided by the Involvement points, a wide range of new activities and capabilities...And leads us to rename the said "point": it becomes the '''Elyps'''!<br />
<br />
=== Patch 750 ===<br />
[[File:Ulukyn-portrait.png|100px|right|Saint Ulu Kyn]]'''25/26 Sept 2019''': Ulu works. [https://app.ryzom.com/app_forum/index.php?page=topic/view/29991/1 Announce on the forum.]<br />
* first phase of the migration of the game server to a new, more efficient machine. <br />
* '''Resolved the Friday, 27th''' (2pm French time): API not yet migrated => small gap between the atysian time and bm.<br />
* Removal of the 15-year-old island<br />
* Corrections: Nexus map is the right one, the underwear came back...<br />
<br />
<br />
<br />
'''2019-5-18''' Ryzom's 15 Years Celebration see https://app.ryzom.com/app_forum/index.php?page=topic/view/29956/1&post197059=en#1 in short:[[File:Confetis.gif|thumb]]<br />
* New visual elements for the Island<br />
* New rewards<br />
<br />
*Added display item buffs and enchant info directly on icon<br />
*Added target closest landmark command ('''/lmtar''')<br />
*Added set compass to target mode after successful /tar command<br />
* ingame browser improvements<br />
* Updated info behavior for healed sap and stamina<br />
*Updated unknown tribe fame visuals<br />
*Updated missions icons to be distinct but not confusing with nations backgrounds<br />
<br />
=== Patch - 2019-06-26 ===<br />
Various balancing of classic missions:<br />
* Reduction of the loss of reputation per mission for non-marauders.<br />
* Addition of a maximum limit of fame that can be won or lost per mission.<br />
* Correction of waiting times to resume a completed mission.<br />
* Enhancement of classic craft missions.<br />
[[File:V3 MP Batiment Brique.png|left|20px|A much lighter package]]Changes to upgrade the "camp tour" missions (Dappers, Nation Points): decrease in the weight of a package, in order to be able to carry out the mission without a Mektoub.<br />
<br />
More on https://app.ryzom.com/app_forum/index.php?page=topic/view/29804/1&post196134=en#1<br />
<br />
=== JY 2603 patch ===<br />
'''The 21th June''' Update on official forum [https://app.ryzom.com/app_forum/index.php?page=topic/view/29797/1#1 Revaluation of the game's missions to expand your fun].<br />
<br />
'''The 28th May''' Patch 745 is available. Fix the matis<->fyros fame switch and Nexus map.<br />
<br />
For US: '''May, 17th May''' after 22:00 UTC, and May 18th after midnight CEST. To [[Patch 2019/JY 2603 Documentation|JY 2603 Documentation]] (work in progress).<br />
[[File:PR flyer JY2603 en600.png|frame|center]]<br />
<br />
In short ([https://app.ryzom.com/app_forum/index.php?page=topic/view/29692/1&post195145=en#1 see full message on the official forum]), a client, data and server patching and a restart of the game server :<br />
<br />
====Additions:====<br />
* new interface for teleportation at Kamis and Karavan altars, Option to automatically rebuy a Kami or Kara pact after a TP (requires max fame)<br />
* ZIG me up: option to put a Zig in the bag, your Zig can be teleported with you<br />
* team Invite button in Guild Member List and Friend List<br />
* welcome message in chat channels<br />
<br />
====Improvements:====<br />
* Kami and Karavan teleport pacts no longer have weight/bulk in your bag<br />
* Ryzom installer (new URLs for download, erasing of a profile on MAC or Linux debugged)<br />
* New fresh backgrounds for icons<br />
* landmarks stored in XML file instead of ICFG file (meaning editable out of game)<br />
* new underwear icons (they now show the right color)<br />
<br />
This patch also includes the results of the work done on Dynamic Events (DE), New Horizons (NH) and the target command.<br /><br />
*Dynamic Events: addition of the "Kitin Invasion", "Puzzle" Dynamic Event, a new button in the Map (to display all Dynamic Events, with a new a blue round icon)<br />
*New Horizons: merger of New Horizons and Brotherhood of the Fortunate Gubani; global limit for "Support Missions" (fame rewards) removed; 1 000 dappers for all (whatever their fame)...<br />
*Target command now supports keyword search (e.g. for a yubo) as follows:<br />
** /tar yubo -- no quotes, target closest entity that contains 'yubo' in its name;<br />
** /tar suckling yubo -- no quotes, target closest entity that contains both 'suckling' and 'yubo' in its name;<br />
** Order not important, full words not needed '/tar y kling' would be a match. Also /tar "ora" -- with quotes, Will target an entity who's name '''starts''' with 'ora', as currently /tar "suckling yubo" -- with quotes, targets an entity who's name starts with 'suckling yubo';<br />
** some current old macros may need quotes now for short keywords, i.e. 'ora', but existing macros using quotes will continue to work.<br />
<br />
====Addendum: Evolution of hardware infrastructure====<br />
The month of March and the beginning of April were the occasion for a spring cleaning, including:<br />
* the moving of the billing server to https://account.ryzom.com<br />
* the migration of Ryzom Chat to another server while retaining its URL: https://chat.ryzom.com.<br />
* the migration of the Yubo server to a new, more powerful machine; it is now dedicated to the tests required by ongoing developments;<br />
* the installation, identical to that of Yubo, of a new server called Gingo, which hosts the tests for acceptance of completed developments before they are put into operation on Atys; this is the pre-production server whose implementation was long overdue;<br />
<br />
The next step in the hardware reconfiguration of the platform will see the migration of Atys, the game server, to new higher performing machine and the confirmation of Gingo as the Atys mirror server facilitating the application of patches and providing a rescue solution in the event of a failure of the latter.<br />
The Ryzom Team remains at your disposal for any additional information, and best wishes to you!<br />
<br />
More on the official forum https://app.ryzom.com/app_forum/index.php?page=topic/view/29692/1&post195145=en#1<br />
<br />
=== Jena Year 2602 Patch v3.5.0 ===<br />
[[File:Flyer1902 EN 600px.png|frame|center]]<br />
On the forum Patch 3.5.0 - 2019-02-08 https://app.ryzom.com/app_forum/index.php?page=topic/view/29373/1&post192850=en#1<br />
<br />
In very very short : a client, data and server patch + a restart of the game server, on February 8th, 2019 :<br />
* New rewards at Wheel of Fortune<br />
* [[Guild Island|Guild Islands]]<br />
* Yubokin comes to settle on the island of Silan<br />
* Change in OP battles: Removal of the neutral status during the battle<br />
* Ranger Gameplay balance, Marauder Improvments<br />
* Clients Improvements<br />
<br />
As an example of lovely Improvements : '''UI-Scale for all Clients''', let's have a look in System / Configuration / Graphics / General : <br />
<gallery><br />
Ech 1.5 2019-02-09.png|A big 1.50<br />
Ech 1.05 2019-02-09.png|Bigger at 1.05<br />
Ech1 2019-02-09.png|'''Normal value''' at 1.00<br />
Ech 0.95 2019-02-09.png|Smaller at 0.95<br />
</gallery><br />
It goes from 0.80 to 2.00.<br />
<br />
<br />
And new Inventory features, with a better quality filter (here, only mats, from q 50 to q 200) <br />
[[File:FiltreI2019-02-09.png|frameless]]<br />
<br />
<br />
To [[User:Craftjenn/Discovery of guild islands|Discovery of guild islands]], by CraftJenn.<br />
<br />
== Forge reports ==<br />
See [[Patch 2019/Forge Reports]].<br />
<br />
==References==<br />
--[[User:Craftjenn|CraftJenn, Ranger du Cercle du Bois d&#39;Almati]] ([[User talk:Craftjenn|talk]]) 10:18, 28 January 2019 (UTC)<br />
===Sources===<br />
* [http://app.ryzom.com/app_forum/index.php?page=forum/view/1839/1 Forum, Official news]<br />
<br />
<br />
[[Category:Featured articles]]<br />
<br />
<br />
<noinclude>{{Portal|Forge|Gameplay}}<br />
[[Category:Updates]][[Category:Game updates 2019]] </noinclude></div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=New_2018&diff=34466New 20182020-02-23T13:04:21Z<p>Amosys: </p>
<hr />
<div>{{Trad|EN=New 2018|FR=Patch de 2018}} <br />
<big>What's up in [[Patch 2020]], [[New2019|2019]], [[New2017|2017]], '''''back to [[User Manual]].'''''</big><br />
* Access the [https://board.ryzom.com/?controller=BoardViewController&action=readonly&token=c46b5ea0f37c83d155f3eacc3acf6956ee75cbfca4afa3f2c107fcb4e74d&from_index=1 Roadmap] with some [https://app.ryzom.com/app_forum/index.php?page=post%2Fview%2F186177&lang=en explanation]<br />
* https://bitbucket.org/ryzom/ <br />
<br />
== Big changes ==<br />
<br />
* New [[Wheel of fortune]], with new stuffs to win<br />
* Ranger Faction improvements<br />
* Opening of Silan from Mainland<br />
<br />
== Patch 3.4.0 (2018-08-17)==<br />
See the [https://app.ryzom.com/app_forum/index.php?page=topic/view/28865/1&post190024=en#1 OFFICIAL NEWS]. <br />
Short extract :<br />
* New Wheel of Fortune (also a new one for Marauders) <br />
*Forage action icon has different background colour<br />
*Add Safe Zones to Ranger Path entries<br />
*Lots of [[Emote|emotes]] now have an animation, ...<br />
<br />
== Patch 3.3.0 - Ranger Rite (2018-03-23) == <br />
See <br />
*The [https://app.ryzom.com/app_forum/index.php?page=topic/view/28384/1&post187069=en#1 Official News]<br />
*[https://app.ryzom.com/app_forum/index.php?page=topic/view/28373/1&post187003=en#1 Ryzom improves with the Ranger Faction!] (2018-03-03)<br />
<br />
== Patch 3.2.1 - Way to Silan (2018-02-17)==<br />
See [https://app.ryzom.com/app_forum/index.php?page=topic/view/28179/1&post186392=en#1 Opening of Silan from Mainland] and the RolePlay (and NRP) announce [https://app.ryzom.com/app_forum/index.php?page=topic/view/28180/1&post186399=en#1 the Opening of a passage to Silan]<br />
<br />
==References==<br />
<br />
===See also===<br />
<br />
* To [[Emote]], to [[User Manual]]<br />
* For [[:Category:Events|events]], see [[Ryzom Wiki:Current events]]. <br /><br />
Please note [https://app.ryzom.com/app_forum/index.php?page=topic/view/28899/190290 Unveiling of the new Fortune Wheel] (2018-09-02).<br />
* There's lot of information (and '''spoilers''') in the [https://app.ryzom.com/app_forum/index.php?page=topic/view/28116/1 2018's Ryzom Forge post]<br />
*What's up [[New2017| in 2017]] too... [[File:Newlooticon.png|right|frameless|new loot locking system]] <br />
<br />
===Sources===<br />
* [http://app.ryzom.com/app_forum/index.php?page=forum/view/1839/1 Forum, Official news]<br />
<br /><br />
<br /><br />
----<br />
<references/><br />
----<br />
<noinclude><br />
{{Portal|Forge|Gameplay}}<br />
[[Category:Updates]] [[Category:Game updates 2018]]</noinclude></div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=New2017&diff=34465New20172020-02-23T13:03:36Z<p>Amosys: </p>
<hr />
<div><noinclude>{{Trad<br />
|DE=New2017<br />
|EN=New2017<br />
|ES=New2017<br />
|FR=Nouveautés 2017<br />
|RU=New2017<br />
}}</noinclude><br />
<big>What's up in [[Patch 2020]], [[New2019|2019]], [[New 2018|2018]], '''''back to [[User Manual]].'''''</big><br />
* Access the [https://board.ryzom.com/?controller=BoardViewController&action=readonly&token=c46b5ea0f37c83d155f3eacc3acf6956ee75cbfca4afa3f2c107fcb4e74d&from_index=1 Roadmap] with some [https://app.ryzom.com/app_forum/index.php?page=post%2Fview%2F186177&lang=en explanation]<br />
* https://bitbucket.org/ryzom/ <br />
<br />
==Big changes==<br />
<br />
===From Megacorp to Rocket===<br />
http://app.ryzom.com/app_forum/index.php?page=topic/view/26674/4#4<br />
<br />
Want to chat IG ? using a browser https://chat.ryzom.com/channel/pub-uni-en (login with your toon name and password).<br />
<br />
To [[Special command|Chat IG commands]]<br />
<br />
===A Scenographic editor===<br />
http://app.ryzom.com/app_forum/index.php?page=topic/view/26321/1&post176524=en#1<br />
<br />
The arrival of the Scenographic Editor is the first public stage of our great project to make the Ryzom Arkitect creation tool available to all our players.<br />
<br />
===Free premium===<br />
<br />
See http://app.ryzom.com/app_forum/index.php?page=topic/view/27050/1&post180553=en#1<br />
<br />
==Patch 3.2.0 - 2017/07/06==<br />
<br />
Very partial list (see forum for the full list) :[[File:Newlooticon.png|41px|right]]<br />
*[http://app.ryzom.com/app_forum/index.php?page=topic/view/27212/1&post181512=en#1 New loot locking system, on forum]<br />
<br />
*Map : more informations (next weather tooltip, humidity...) and remove map landmarks limit.<br />
<br />
*Groups (nice to moove armor and jewels, get dressed...) : new commands added in the IG chat, (for ex : '''/naked''' )<br />
*#get dressed (wear armor, jewels, tool, weapon) <br />
*#create your first group (for ex mygroup : ie '''/createGroup mygroup''' )<br />
*#See groups: '''/listGroup''' and delete with '''/deleteGroup mygroup'''<br />
*#Once your created your groups, some homins create macros, others use /naked and right clic in inventory (bag, toub, flat) in order to moove/wear...<br /><br />
: More on [https://app.ryzom.com/app_forum/index.php?page=topic/view/26843/1 using groups on the forum]<br />
<br />
*Same client for all OS.<br />
<br />
Source : [http://app.ryzom.com/app_forum/index.php?page=topic/view/27213 Forum, Patch 3.2.0 - 06/07/2017]<br />
<br />
== Patch 3.2.1 - 2017/07/18==<br />
<br />
Text search to inventory<br />
<br />
*200-230 for objects between quality 200 and 230, <br />
*200- for objects between quality 200 to max, <br />
*-200 for all objects from quality 0 to 200<br />
<br />
Source : http://app.ryzom.com/app_forum/index.php?page=topic/view/27287/10<br />
<br />
<br />
<br />
<br />
<br />
==References==<br />
Server merge (25/09/2012): now we are all on Atys.<br />
There was a time when there were several servers (some had more French/English/German than others (Aniro, Arispotle and Leanon were closed). All players migrated to Atys, via Silan, losing their possessions (they were offered transitional equipment).<br />
<br />
https://app.ryzom.com/app_forum/index.php?page=topic/view/13944/1#1 <br />
<br />
===See also===<br />
*[http://app.ryzom.com/app_forum/index.php?page=forum/view/1839/1 Forum, Official news]<br />
* To [[Emote]], to [[User Manual]] and What's up [[New 2018|in 2018]].<br />
<br />
===Sources===<br />
*[[User:Craftjenn|Craftjenn, Ranger du Cercle du Bois d&#39;Almati]] ([[User talk:Craftjenn|talk]]) 20:32, 12 August 2017 (CEST)<br />
{{Last version link|New2017}}<br />
<noinclude><br />
{{Portal Gameplay}}<br />
[[Category:Commands]] [[Category:Game updates 2017]] [[Category:Updates]]<br />
</noinclude></div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=New2017&diff=34464New20172020-02-23T13:02:56Z<p>Amosys: </p>
<hr />
<div><noinclude>{{Trad<br />
|DE=New2017<br />
|EN=New2017<br />
|ES=New2017<br />
|FR=Nouveautés 2017<br />
|RU=New2017<br />
}}</noinclude><br />
<big>What's up in [[Patch 2020]] [[New2019|2019]], [[New 2018|2018]], '''''back to [[User Manual]].'''''</big><br />
* Access the [https://board.ryzom.com/?controller=BoardViewController&action=readonly&token=c46b5ea0f37c83d155f3eacc3acf6956ee75cbfca4afa3f2c107fcb4e74d&from_index=1 Roadmap] with some [https://app.ryzom.com/app_forum/index.php?page=post%2Fview%2F186177&lang=en explanation]<br />
* https://bitbucket.org/ryzom/ <br />
<br />
==Big changes==<br />
<br />
===From Megacorp to Rocket===<br />
http://app.ryzom.com/app_forum/index.php?page=topic/view/26674/4#4<br />
<br />
Want to chat IG ? using a browser https://chat.ryzom.com/channel/pub-uni-en (login with your toon name and password).<br />
<br />
To [[Special command|Chat IG commands]]<br />
<br />
===A Scenographic editor===<br />
http://app.ryzom.com/app_forum/index.php?page=topic/view/26321/1&post176524=en#1<br />
<br />
The arrival of the Scenographic Editor is the first public stage of our great project to make the Ryzom Arkitect creation tool available to all our players.<br />
<br />
===Free premium===<br />
<br />
See http://app.ryzom.com/app_forum/index.php?page=topic/view/27050/1&post180553=en#1<br />
<br />
==Patch 3.2.0 - 2017/07/06==<br />
<br />
Very partial list (see forum for the full list) :[[File:Newlooticon.png|41px|right]]<br />
*[http://app.ryzom.com/app_forum/index.php?page=topic/view/27212/1&post181512=en#1 New loot locking system, on forum]<br />
<br />
*Map : more informations (next weather tooltip, humidity...) and remove map landmarks limit.<br />
<br />
*Groups (nice to moove armor and jewels, get dressed...) : new commands added in the IG chat, (for ex : '''/naked''' )<br />
*#get dressed (wear armor, jewels, tool, weapon) <br />
*#create your first group (for ex mygroup : ie '''/createGroup mygroup''' )<br />
*#See groups: '''/listGroup''' and delete with '''/deleteGroup mygroup'''<br />
*#Once your created your groups, some homins create macros, others use /naked and right clic in inventory (bag, toub, flat) in order to moove/wear...<br /><br />
: More on [https://app.ryzom.com/app_forum/index.php?page=topic/view/26843/1 using groups on the forum]<br />
<br />
*Same client for all OS.<br />
<br />
Source : [http://app.ryzom.com/app_forum/index.php?page=topic/view/27213 Forum, Patch 3.2.0 - 06/07/2017]<br />
<br />
== Patch 3.2.1 - 2017/07/18==<br />
<br />
Text search to inventory<br />
<br />
*200-230 for objects between quality 200 and 230, <br />
*200- for objects between quality 200 to max, <br />
*-200 for all objects from quality 0 to 200<br />
<br />
Source : http://app.ryzom.com/app_forum/index.php?page=topic/view/27287/10<br />
<br />
<br />
<br />
<br />
<br />
==References==<br />
Server merge (25/09/2012): now we are all on Atys.<br />
There was a time when there were several servers (some had more French/English/German than others (Aniro, Arispotle and Leanon were closed). All players migrated to Atys, via Silan, losing their possessions (they were offered transitional equipment).<br />
<br />
https://app.ryzom.com/app_forum/index.php?page=topic/view/13944/1#1 <br />
<br />
===See also===<br />
*[http://app.ryzom.com/app_forum/index.php?page=forum/view/1839/1 Forum, Official news]<br />
* To [[Emote]], to [[User Manual]] and What's up [[New 2018|in 2018]].<br />
<br />
===Sources===<br />
*[[User:Craftjenn|Craftjenn, Ranger du Cercle du Bois d&#39;Almati]] ([[User talk:Craftjenn|talk]]) 20:32, 12 August 2017 (CEST)<br />
{{Last version link|New2017}}<br />
<noinclude><br />
{{Portal Gameplay}}<br />
[[Category:Commands]] [[Category:Game updates 2017]] [[Category:Updates]]<br />
</noinclude></div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Webapps_main/list&diff=32857Webapps main/list2019-10-06T15:03:35Z<p>Amosys: </p>
<hr />
<div><big>This is the list of the current webapps (post JA 2603 patches), with link to the official forum. The 1st number is the ID (to use it in game, type in [[Chat]] '''<nowiki>/appzone ID</nowiki>''' - more on [[Special command]]s.<br />
</big><br />
<br />
== Current webapps ==<br />
<br />
1102. Armory - https://app.ryzom.com/app_forum/index.php?page=post/view/196340 - KO IG, to use with a browser (outside of the game) at https://www.ryzomarmory.com/home<br />
<br />
855. bm - https://ballisticmystix.net/<br />
<br />
1532. Book of SKA - https://app.ryzom.com/index.php?action=launch_app&appid=1532<br />
<br />
1823. Bunny tools - https://app.ryzom.com/app_forum/index.php?page=topic/view/25459/27<br />
<br />
1521. Dates <br />
<br />
2132. Fametracker - https://app.ryzom.com/app_forum/index.php?page=post/view/190043<br />
<br />
1976. Ryzom Bosses - http://www.ryzom-bosses.com/ <br />
<br />
1947. RygReg - https://app.ryzom.com/app_forum/index.php?page=topic/view/26435<br />
<br />
1960. Book of Guilds (/appzone 1960) - https://app.ryzom.com/app_forum/index.php?page=topic/view/26436<br />
<br />
2135 Langapp - https://app.ryzom.com/app_forum/index.php?page=topic/view/27506/<br />
<br />
2413. Blabla game and Blablator (/appzone 2413 and 2414) - https://app.ryzom.com/app_forum/index.php?page=topic/view/27506/16<br />
<br />
2324. Level Tracker - https://app.ryzom.com/app_forum/index.php?page=topic/view/28750<br />
<br />
800. RyzomTracker (/appzone 800)<br />
<br />
1977. Bag App - https://app.ryzom.com/app_forum/index.php?page=topic/view/28784<br />
<br />
2000. Cookie Clicker - https://app.ryzom.com/app_forum/index.php?page=topic/view/26430/1<br />
<br />
1713. Molly's Mansion - https://app.ryzom.com/app_forum/index.php?page=topic/view/24460/1<br />
<br />
1469. Molly's Materials - https://app.ryzom.com/app_forum/index.php?page=topic/view/28803/1<br />
<br />
1572. Molly's Recipes - https://app.ryzom.com/app_forum/index.php?page=topic/view/28803/1<br />
<br />
1799. R.O.X. (1799) - https://app.ryzom.com/app_forum/index.php?page=topic/view/24932/1<br />
<br />
2134. Story - https://app.ryzom.com/app_forum/index.php?page=topic/view/27365/1<br />
<br />
<br />
<br />
==Event related==<br />
<br />
2485. Public Inventory of the Harvest Party (/appzone 2485)<br />
<br />
<br />
-------------------------------------------------------------------------------------------------------------------<br />
<br />
==To be check==<br />
===Dead===<br />
<br />
=== list not complete ===<br />
<br />
2132. Alkiane /appzone 2132<br />
<br />
24.55 Atysian Tales /appzone 2455<br />
<br />
1521. ChatLog decoder /appzone 1521<br />
<br />
1975. Ryzom Database ryzom.silenda.de<br />
<br />
1578. Supremes Availability - website ok on the 2019 Oct<br />
<br />
1753. TabCraft - http://www.serane.fr/ryzom/RyzomCraft.html - website ok on the 2019 Oct. Nice for French homins (translation links to bm's map)<br />
<br />
<br />
{{Portal|Community|X-files}}<br />
[[Category:User interface]] [[Category:X-files]][[Category:Gameplay]][[Category:Community]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Webapps_main/list&diff=32856Webapps main/list2019-10-06T15:02:53Z<p>Amosys: </p>
<hr />
<div><big>This is the list of the current webapps (post JA 2603 patches), with link to the official forum. The 1st number is the ID (to use it in game, type in [[Chat]] '''<nowiki>/appzone ID</nowiki>''' - more on [[Special command]]s.<br />
</big><br />
<br />
<br />
<br />
1102. Armory - https://app.ryzom.com/app_forum/index.php?page=post/view/196340 - KO IG, to use with a browser (outside of the game) at https://www.ryzomarmory.com/home<br />
<br />
855. bm - https://ballisticmystix.net/<br />
<br />
1532. Book of SKA - https://app.ryzom.com/index.php?action=launch_app&appid=1532<br />
<br />
1823. Bunny tools - https://app.ryzom.com/app_forum/index.php?page=topic/view/25459/27<br />
<br />
1521. Dates <br />
<br />
2132. Fametracker - https://app.ryzom.com/app_forum/index.php?page=post/view/190043<br />
<br />
1976. Ryzom Bosses - http://www.ryzom-bosses.com/ <br />
<br />
1947. RygReg - https://app.ryzom.com/app_forum/index.php?page=topic/view/26435<br />
<br />
1960. Book of Guilds (/appzone 1960) - https://app.ryzom.com/app_forum/index.php?page=topic/view/26436<br />
<br />
2135 Langapp - https://app.ryzom.com/app_forum/index.php?page=topic/view/27506/<br />
<br />
2413. Blabla game and Blablator (/appzone 2413 and 2414) - https://app.ryzom.com/app_forum/index.php?page=topic/view/27506/16<br />
<br />
2324. Level Tracker - https://app.ryzom.com/app_forum/index.php?page=topic/view/28750<br />
<br />
800. RyzomTracker (/appzone 800)<br />
<br />
1977. Bag App - https://app.ryzom.com/app_forum/index.php?page=topic/view/28784<br />
<br />
2000. Cookie Clicker - https://app.ryzom.com/app_forum/index.php?page=topic/view/26430/1<br />
<br />
1713. Molly's Mansion - https://app.ryzom.com/app_forum/index.php?page=topic/view/24460/1<br />
<br />
1469. Molly's Materials - https://app.ryzom.com/app_forum/index.php?page=topic/view/28803/1<br />
<br />
1572. Molly's Recipes - https://app.ryzom.com/app_forum/index.php?page=topic/view/28803/1<br />
<br />
1799. R.O.X. (1799) - https://app.ryzom.com/app_forum/index.php?page=topic/view/24932/1<br />
<br />
2134. Story - https://app.ryzom.com/app_forum/index.php?page=topic/view/27365/1<br />
<br />
<br />
<br />
==Event related==<br />
<br />
2485. Public Inventory of the Harvest Party (/appzone 2485)<br />
<br />
<br />
-------------------------------------------------------------------------------------------------------------------<br />
<br />
==To be check==<br />
===Dead===<br />
<br />
=== list not complete ===<br />
<br />
2132. Alkiane /appzone 2132<br />
<br />
24.55 Atysian Tales /appzone 2455<br />
<br />
1521. ChatLog decoder /appzone 1521<br />
<br />
1975. Ryzom Database ryzom.silenda.de<br />
<br />
1578. Supremes Availability - website ok on the 2019 Oct<br />
<br />
1753. TabCraft - http://www.serane.fr/ryzom/RyzomCraft.html - website ok on the 2019 Oct. Nice for French homins (translation links to bm's map)<br />
<br />
<br />
{{Portal|Community|X-files}}<br />
[[Category:User interface]] [[Category:X-files]][[Category:Gameplay]][[Category:Community]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Webapps_main/list&diff=32855Webapps main/list2019-10-06T14:54:32Z<p>Amosys: </p>
<hr />
<div><big>This is the list of the current webapps (post JA 2603 patches), with link to the official forum.<br />
</big><br />
<br />
Armory (/appzone 1102) - https://app.ryzom.com/app_forum/index.php?page=post/view/196340 KO IG, to use with a browser (outside of the game) at https://www.ryzomarmory.com/home<br />
<br />
bm (/appzone 855) - https://ballisticmystix.net/<br />
<br />
bunny tools (/appzone 1823) - https://app.ryzom.com/app_forum/index.php?page=topic/view/25459/27<br />
<br />
Dates (/appzone 1521)<br />
<br />
fametracker (/appzone 2132) - https://app.ryzom.com/app_forum/index.php?page=post/view/190043<br />
<br />
Ryzom Bosses (/appzone 1976) - http://www.ryzom-bosses.com/ <br />
<br />
RygReg (/appzone 1947) - https://app.ryzom.com/app_forum/index.php?page=topic/view/26435<br />
<br />
Book of Guilds (/appzone 1960) - https://app.ryzom.com/app_forum/index.php?page=topic/view/26436<br />
<br />
Langapp (/appzone 2135) - https://app.ryzom.com/app_forum/index.php?page=topic/view/27506/<br />
<br />
Blabla game and Blablator (/appzone 2413 and 2414) - https://app.ryzom.com/app_forum/index.php?page=topic/view/27506/16<br />
<br />
Level Tracker (/appzone 2324)- https://app.ryzom.com/app_forum/index.php?page=topic/view/28750<br />
<br />
RyzomTracker (/appzone 800)<br />
<br />
Bag App (1977) - https://app.ryzom.com/app_forum/index.php?page=topic/view/28784<br />
<br />
Cookie Clicker (2000) - https://app.ryzom.com/app_forum/index.php?page=topic/view/26430/1<br />
<br />
Molly's Mansion (1713) - https://app.ryzom.com/app_forum/index.php?page=topic/view/24460/1<br />
<br />
Molly's Materials (1469) - https://app.ryzom.com/app_forum/index.php?page=topic/view/28803/1<br />
<br />
Molly's Recipes (1572) - https://app.ryzom.com/app_forum/index.php?page=topic/view/28803/1<br />
<br />
R.O.X. (1799) - https://app.ryzom.com/app_forum/index.php?page=topic/view/24932/1<br />
<br />
Story (2134) - https://app.ryzom.com/app_forum/index.php?page=topic/view/27365/1<br />
<br />
Book of SKA (1532) - https://app.ryzom.com/index.php?action=launch_app&appid=1532<br />
<br />
<br />
==Event related==<br />
<br />
Public Inventory of the Harvest Party (/appzone 2485)<br />
<br />
<br />
-------------------------------------------------------------------------------------------------------------------<br />
<br />
==To be check==<br />
===Dead===<br />
<br />
=== list not complete ===<br />
<br />
Alkiane /appzone 2132<br />
<br />
Atysian Tales /appzone 2455<br />
<br />
ChatLog decoder /appzone 1521<br />
<br />
Ryzom Database /appzone 1975 ryzom.silenda.de<br />
<br />
Supremes Availability /appzone 1578 website ok on the 2019 Oct<br />
<br />
TabCraft /appzone 1753 http://www.serane.fr/ryzom/RyzomCraft.html website ok on the 2019 Oct. Nice for French<br />
<br />
<br />
{{Portal|Community|X-files}}<br />
[[Category:User interface]] [[Category:X-files]][[Category:Gameplay]][[Category:Community]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Webapps_main/list&diff=32854Webapps main/list2019-10-06T14:44:25Z<p>Amosys: </p>
<hr />
<div><big>This is the list of the current webapps (post JA 2603 patches), with link to the official forum.<br />
</big><br />
<br />
Armory (/appzone 1102) - https://app.ryzom.com/app_forum/index.php?page=post/view/196340 KO IG, to use with a browser (outside of the game) at https://www.ryzomarmory.com/home<br />
<br />
bm (/appzone 855) - https://ballisticmystix.net/<br />
<br />
bunny tools (/appzone 1823) - https://app.ryzom.com/app_forum/index.php?page=topic/view/25459/27<br />
<br />
Dates (/appzone 1521)<br />
<br />
fametracker (/appzone 2132) - https://app.ryzom.com/app_forum/index.php?page=post/view/190043<br />
<br />
Ryzom Bosses (/appzone 1976) - http://www.ryzom-bosses.com/ <br />
<br />
RygReg - https://app.ryzom.com/app_forum/index.php?page=topic/view/26435<br />
<br />
Book of Guilds (/appzone 1960) - https://app.ryzom.com/app_forum/index.php?page=topic/view/26436<br />
<br />
Langapp - https://app.ryzom.com/app_forum/index.php?page=topic/view/27506/<br />
<br />
Blabla game and Blablator - https://app.ryzom.com/app_forum/index.php?page=topic/view/27506/16<br />
<br />
Level Tracker - https://app.ryzom.com/app_forum/index.php?page=topic/view/28750<br />
<br />
RyzomTracker (/appzone 800)<br />
<br />
Bag App - https://app.ryzom.com/app_forum/index.php?page=topic/view/28784<br />
<br />
Cookie Clicker - https://app.ryzom.com/app_forum/index.php?page=topic/view/26430/1<br />
<br />
Molly's Mansion - https://app.ryzom.com/app_forum/index.php?page=topic/view/24460/1<br />
<br />
Molly's Materials - https://app.ryzom.com/app_forum/index.php?page=topic/view/28803/1<br />
<br />
Molly's Recipes - https://app.ryzom.com/app_forum/index.php?page=topic/view/28803/1<br />
<br />
R.O.X. - https://app.ryzom.com/app_forum/index.php?page=topic/view/24932/1<br />
<br />
Story - https://app.ryzom.com/app_forum/index.php?page=topic/view/27365/1<br />
<br />
Book of SKA - https://app.ryzom.com/index.php?action=launch_app&appid=1532<br />
<br />
<br />
==Event related==<br />
<br />
Public Inventory of the Harvest Party (/appzone 2485)<br />
<br />
<br />
-------------------------------------------------------------------------------------------------------------------<br />
<br />
==To be check==<br />
===Dead===<br />
<br />
=== list not complete ===<br />
<br />
Alkiane /appzone 2132<br />
<br />
Atysian Tales /appzone 2455<br />
<br />
ChatLog decoder /appzone 1521<br />
<br />
Ryzom Database /appzone 1975 ryzom.silenda.de<br />
<br />
Supremes Availability /appzone 1578 website ok on the 2019 Oct<br />
<br />
TabCraft /appzone 1753 http://www.serane.fr/ryzom/RyzomCraft.html website ok on the 2019 Oct. Nice for French<br />
<br />
<br />
{{Portal|Community|X-files}}<br />
[[Category:User interface]] [[Category:X-files]][[Category:Gameplay]][[Category:Community]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Webapps_main/list&diff=32853Webapps main/list2019-10-06T14:43:46Z<p>Amosys: /* To be check */</p>
<hr />
<div><big>This is the list of the current webapps (post JA 2603 patches), with link to the official forum.<br />
</big><br />
<br />
Armory (/appzone 1102) - https://app.ryzom.com/app_forum/index.php?page=post/view/196340 KO IG, to use with a browser (outside of the game) at https://www.ryzomarmory.com/home<br />
<br />
bm (/appzone 855) - https://ballisticmystix.net/<br />
<br />
bunny tools (/appzone 1823) - https://app.ryzom.com/app_forum/index.php?page=topic/view/25459/27<br />
<br />
Dates (/appzone 1521)<br />
<br />
fametracker (/appzone 2132) - https://app.ryzom.com/app_forum/index.php?page=post/view/190043<br />
<br />
Ryzom Bosses (/appzone 1976) - http://www.ryzom-bosses.com/ <br />
<br />
RygReg - https://app.ryzom.com/app_forum/index.php?page=topic/view/26435<br />
<br />
Book of Guilds (/appzone 1960) - https://app.ryzom.com/app_forum/index.php?page=topic/view/26436<br />
<br />
Langapp - https://app.ryzom.com/app_forum/index.php?page=topic/view/27506/<br />
<br />
Blabla game and Blablator - https://app.ryzom.com/app_forum/index.php?page=topic/view/27506/16<br />
<br />
Level Tracker - https://app.ryzom.com/app_forum/index.php?page=topic/view/28750<br />
<br />
RyzomTracker (/appzone 800)<br />
<br />
Bag App - https://app.ryzom.com/app_forum/index.php?page=topic/view/28784<br />
<br />
Cookie Clicker - https://app.ryzom.com/app_forum/index.php?page=topic/view/26430/1<br />
<br />
Molly's Mansion - https://app.ryzom.com/app_forum/index.php?page=topic/view/24460/1<br />
<br />
Molly's Materials - https://app.ryzom.com/app_forum/index.php?page=topic/view/28803/1<br />
<br />
Molly's Recipes - https://app.ryzom.com/app_forum/index.php?page=topic/view/28803/1<br />
<br />
R.O.X. - https://app.ryzom.com/app_forum/index.php?page=topic/view/24932/1<br />
<br />
Story - https://app.ryzom.com/app_forum/index.php?page=topic/view/27365/1<br />
<br />
Book of SKA - https://app.ryzom.com/index.php?action=launch_app&appid=1532<br />
<br />
<br />
==Event related==<br />
<br />
Public Inventory of the Harvest Party (/appzone 2485)<br />
<br />
<br />
-------------------------------------------------------------------------------------------------------------------<br />
<br />
==To be check==<br />
===Dead===<br />
<br />
=== list not complete ===<br />
<br />
Alkiane /appzone 2132<br />
<br />
Atysian Tales /appzone 2455<br />
<br />
ChatLog decoder /appzone 1521<br />
<br />
Ryzom Database /appzone 1975 ryzom.silenda.de<br />
<br />
Supremes Availability /appzone 1578 website ok on the 2019 Oct<br />
<br />
TabCraft /appzone 1753 http://www.serane.fr/ryzom/RyzomCraft.html website ok on the 2019 Oct. Nice for French<br />
<br />
<br />
{{Portal|Community|Craft}}<br />
[[Category:User interface]] [[Category:X-files]][[Category:Gameplay]][[Category:Community]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Webapps_main/list&diff=32852Webapps main/list2019-10-06T14:41:54Z<p>Amosys: </p>
<hr />
<div><big>This is the list of the current webapps (post JA 2603 patches), with link to the official forum.<br />
</big><br />
<br />
Armory (/appzone 1102) - https://app.ryzom.com/app_forum/index.php?page=post/view/196340 KO IG, to use with a browser (outside of the game) at https://www.ryzomarmory.com/home<br />
<br />
bm (/appzone 855) - https://ballisticmystix.net/<br />
<br />
bunny tools (/appzone 1823) - https://app.ryzom.com/app_forum/index.php?page=topic/view/25459/27<br />
<br />
Dates (/appzone 1521)<br />
<br />
fametracker (/appzone 2132) - https://app.ryzom.com/app_forum/index.php?page=post/view/190043<br />
<br />
Ryzom Bosses (/appzone 1976) - http://www.ryzom-bosses.com/ <br />
<br />
RygReg - https://app.ryzom.com/app_forum/index.php?page=topic/view/26435<br />
<br />
Book of Guilds (/appzone 1960) - https://app.ryzom.com/app_forum/index.php?page=topic/view/26436<br />
<br />
Langapp - https://app.ryzom.com/app_forum/index.php?page=topic/view/27506/<br />
<br />
Blabla game and Blablator - https://app.ryzom.com/app_forum/index.php?page=topic/view/27506/16<br />
<br />
Level Tracker - https://app.ryzom.com/app_forum/index.php?page=topic/view/28750<br />
<br />
RyzomTracker (/appzone 800)<br />
<br />
Bag App - https://app.ryzom.com/app_forum/index.php?page=topic/view/28784<br />
<br />
Cookie Clicker - https://app.ryzom.com/app_forum/index.php?page=topic/view/26430/1<br />
<br />
Molly's Mansion - https://app.ryzom.com/app_forum/index.php?page=topic/view/24460/1<br />
<br />
Molly's Materials - https://app.ryzom.com/app_forum/index.php?page=topic/view/28803/1<br />
<br />
Molly's Recipes - https://app.ryzom.com/app_forum/index.php?page=topic/view/28803/1<br />
<br />
R.O.X. - https://app.ryzom.com/app_forum/index.php?page=topic/view/24932/1<br />
<br />
Story - https://app.ryzom.com/app_forum/index.php?page=topic/view/27365/1<br />
<br />
Book of SKA - https://app.ryzom.com/index.php?action=launch_app&appid=1532<br />
<br />
<br />
==Event related==<br />
<br />
Public Inventory of the Harvest Party (/appzone 2485)<br />
<br />
<br />
-------------------------------------------------------------------------------------------------------------------<br />
<br />
==To be check==<br />
===Dead===<br />
<br />
=== list not complete ===<br />
<br />
Alkiane /appzone 2132<br />
<br />
Atysian Tales /appzone 2455<br />
<br />
ChatLog decoder /appzone 1521<br />
<br />
Ryzom Database /appzone 1975 ryzom.silenda.de<br />
<br />
Supremes Availability /appzone 1578 website ok on the 2019 Oct<br />
<br />
{{Portal|Community|Craft}}<br />
[[Category:User interface]] [[Category:X-files]][[Category:Gameplay]][[Category:Community]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Armour_and_Shields&diff=30527Armour and Shields2019-06-30T14:25:16Z<p>Amosys: </p>
<hr />
<div>'''Type:''' Crafting<br />
<br />
'''Race:''' Zoraï<br />
<br />
=Prerequisites=<br />
==Special order for armour (Nai-Da Fuangi, Zora trainers)==<br />
* Zoraï fame 0+<br />
<br />
* 2 x Tan-ko pants x40 (Zoraï BQ heavy pants)<br />
* 2 x Shaï-don sleeves q30 (Zoraï BQ medium sleeves)<br />
==Nai-Da Fuangi needs armour==<br />
* Zoraï fame 0+<br />
<br />
* 8 x Pakmon Shield q11<br />
* 2 x Kastu Buckler q35<br />
==Wu Zhong (Zora, South Gate) wants made-to-order armour==<br />
* Zoraï fame +0<br />
<br />
* 5 x Tan-ko Boots q12 (Zoraï BQ heavy boots)<br />
* 5 x Shaï-don Vest q18 (Zoraï BQ medium vest)<br />
* 18 minute timer<br />
<br />
==Rite Mission==<br />
La-Po Len (Zora, Highmart District), The old Zoraï Smith<br />
* Craft lvl 25+<br />
* Zoraï fame 34<br />
[[Category:Rites]] [[Category:Craft]] [[Category:Zoraï]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=30526Wiki Technical Guide2019-06-30T14:24:14Z<p>Amosys: /* Other advanced stuffs */</p>
<hr />
<div><noinclude>{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=4<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}</noinclude><br />
'''''A short technical guide for experienced contributors and documentation managers.''''' See [[Writing Guide]] for basic wiki knowledge.<br />
<br />
=='''<big>Working as a team</big>'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''<code><nowiki>[[Talk:{{FULLPAGENAME}}]]</nowiki></code>'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''<code><nowiki>===Title of the topic==</nowiki></code>'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''<code><nowiki>~~~~</nowiki></code>'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more <code>:</code> than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''<code><nowiki>==Title of the topic {{OK}}==</nowiki></code>'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''<code><nowiki>{{KO}}</nowiki></code>'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''<big>Translations</big>'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''<big>Edition</big>'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''<code><nowiki><!--</nowiki></code>''' and to follow it with '''<code><nowiki>--></nowiki></code>'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''<code><nowiki><noinclude><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></noinclude></nowiki></code>'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''<code><nowiki>{{WIP|~~~~}}</nowiki></code>''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''<code><nowiki>{{WIP}}</nowiki></code>'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''<code><nowiki>[[Utilisateur:Zorroargh/Brouillons/...]]</nowiki></code>'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''<big>Validation of content</big>'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
<big>A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.</big><br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''<code><nowiki>{{Official Lore}}</nowiki></code>''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''<code><nowiki>{{Lore Validation Request}}</nowiki></code>''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''<big>Categories</big>'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
<div style="text-align:center;"><br />
{{3DText|3D=outset|group=ranger|text=<span style="font-size:large;font-variant: small-caps;font-weight: bold;">'''''Portal …'''''</span>}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''<code><nowiki>There are for now {{Number of pages}} pages on …</nowiki></code>'''<br />
</div><br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use <code><nowiki>{{Number of pages}}</nowiki></code> that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article <big>'''''[[Categorization]]'''''</big>. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
<div style="text-align:center;">'''—• Six wikis, six category systems, all images in common •—'''</div><br />
<br />
=='''<big>Template</big>'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
<br />
===Naming your Template===<br />
Some rules for naming templates.<br />
<br />
===All templates===<br />
<big>'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.</big><br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''<big>Portal</big>'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''<code><nowiki>{{Portal bottom}}</nowiki></code>'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''<code><nowiki>{{Portal bottom}}</nowiki></code>''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''<code><nowiki>{{:DOCNAME}}</nowiki></code>''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class="wikitable centre"<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || <nowiki>{{:Featured article/...}}</nowiki> || <nowiki>{{:Lumière sur/...}}</nowiki><br />
|-<br />
| Every day of the week || <nowiki>{{:Featured article/GBA/Week/{{CURRENTDOW}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}</nowiki><br />
|-<br />
| Every day of the month || <nowiki>{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}</nowiki><br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''<pre><nowiki>{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|xxx}}<br />
[[Category:yyyy]]</noinclude></nowiki></pre>'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''<code><nowiki><noinclude></nowiki></code>''' and '''<code><nowiki></noinclude></noinclude></nowiki></code>''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''<code><nowiki><onlyinclude></nowiki></code>''' and '''<code><nowiki></onlyinclude></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''<code><nowiki><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''<code><nowiki>{{read more|<<the original article>}}</nowiki></code>''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''<big>Home page</big>'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
<br />
== Other advanced stuffs ==<br />
API, tips on Special commands...<br />
<br />
[[Wiki Technical Guide/Comparaison of lists ns and other]]<br />
=== namespaces ===<br />
Code used: <nowiki>{{Special:AllPages|namespace=1}}</nowiki><br />
<br />
Usually, the talk has ns+1. To be bief, no talk here (see more detailled pages) BUT un-usual.<br />
<br />
Commons to all:<br />
<br />
*Namespace 1 - Talk (in fr Discussion)<br />
*Namespace 2 - User (in fr, or Utilisateur or Utilisatrices)<br />
* Namespace 6 - File - Fichier <br />
*Namespace 8 - MediaWiki <br />
*Namespace 10 - Modèle - Template <br />
*Namespace 12 - Aide - Help<br />
*Namespace 14 - Category - Catégorie<br />
<br />
==== FR ns ====<br />
see [[:fr:Guide Technique du wiki/FR ns liste]] (commands are KO in here)<br />
<br />
*Namespace 4 - '''EncyclopAtys'''<br />
*Namespace 100 - Guilde<br />
*Namespace 106 - '''Portail - Portal'''<br />
<br />
==== EN ns ====<br />
see [[Wiki Technical Guide/EN ns list]]<br />
<br />
But:<br />
*Namespace '''4 - Ryzom Wiki''' and 5 Namespace 5 - Ryzom Wiki talk<br />
*Namespace '''104 - Event'''<br />
<br />
==== DE ns ====<br />
[[:de:Technischer Wiki-Leitfaden/DE ns list]]<br />
<br />
Looks like the EN, but no Event namespace, less pages and talk<br />
<br />
==== Atys Common ns ====<br />
See [https://atys.wiki.ryzom.com/wiki/User:Heernis/Common_ns_list Common ns list on atys common]<br />
<br />
As the DE/EN wikis: User (ns 2), File (ns 6), Template 10, Help (ns 12) 3p, Category (ns 14)<br />
<br />
* Namespace 4 - '''Ryzom Commons (ns 4)'''<br />
<br />
=== Wiki codes about categories ===<br />
* on common, Heernis used <nowiki><categorytree mode="all" depth="20" showcount"on" hideprefix="never">Wikipatys</categorytree></nowiki> to get result: Wikipatys, Deutsch, English, Graphic Charter, Hidden categories<br />
* The code <nowiki><categorytree>Foo</categorytree></nowiki> on a wiki page, will show the contents of '''category Foo''' as a dynamic tree on that page.<br />
<br />
<br />
From https://www.mediawiki.org/wiki/Extension:CategoryTree#Usage :<br />
* let's try a all mode on Encyclopatys <nowiki><categorytree mode="all" depth="20" showcount"on" hideprefix="never">Encyclopatys</categorytree></nowiki>:<br />
<categorytree style="margin-left: 30px;" mode="all" depth="20" showcount"on" hideprefix="never">Encyclopatys</categorytree><br />
* a parent mode <nowiki><categorytree mode="parents" depth="20" showcount"on" hideprefix="never">Mysteries</categorytree></nowiki>:<br />
<categorytree style="margin-left: 30px;" mode="parents" depth="20" showcount"on" hideprefix="never">Mysteries</categorytree><br />
* let's try an other <nowiki><categorytree namespaces="talk" style="margin-left: 30px;" mode="pages" depth="20" >Encyclopatys</categorytree></nowiki> plus categories:<br />
<categorytree style="margin-left: 30px;" mode="pages" depth="20" namespaces="talk<br />
Category">Encyclopatys</categorytree><br />
<br />
<br />
* With mode=parents we can see all parents of a category :) But how from EN wiki get the FR/EN values ? (tried fr:CategoryName and :fr:CategoryName)<br />
* depth default is 1. 0 will give roots categories<br />
* hideroot: set this to "on" to hide the "root" node of the tree (ex: <nowiki>hideroot=on</nowiki>)<br />
* The <nowiki>{{#categorytree:Foo|hideroot|mode=pages}}</nowiki> parser function, same but with other syntax. Using the parser function syntax has the advantage that it allows you to use [https://www.mediawiki.org/wiki/Help:Magic_words magic words] (such <nowiki>{{#categorytree:{{PAGENAME}}}}</nowiki>), templates (<nowiki>{{#categorytree:{{root category}}}}</nowiki>) and template parameters when specifying the category to show.<br />
<br />
=== Other links ===<br />
*[[Wiki Technical Guide/Special Pages]]<br />
* [[Wiki Technical Guide/API]]<br />
<br />
Other usefull links<br />
* https://regex101.com/<br />
* https://www.mediawiki.org/wiki/Manual%3APywikibot and [[User:Amosys/Pywiki]] (for tests)<br />
<br />
<br />
<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide/Comparaison_of_lists_ns_and_other&diff=30524Wiki Technical Guide/Comparaison of lists ns and other2019-06-30T14:22:04Z<p>Amosys: Created page with "From the Heernis work == Names spaces (ns) == Ex of namespaces: Talk:, User: To discover them, it seems he used the code <nowiki>{{Special:AllPages|namespace=1}}</nowiki>,..."</p>
<hr />
<div>From the Heernis work <br />
<br />
== Names spaces (ns) ==<br />
Ex of namespaces: Talk:, User: <br />
To discover them, it seems he used the code <nowiki>{{Special:AllPages|namespace=1}}</nowiki>, adding +1 until reach 105 (event talk) <br />
<br />
Here are the namespace value and content (with notes or questions)<br />
=== EN wiki ===<br />
[[Wiki Technical Guide/EN ns list]]<br />
<br />
1. Talk <br />
2. User (som ip in here) <br />
3. User talk <br />
<br />
4. Ryzom wiki <br />
5. Ryzom wiki talk<br />
<br />
'''6. File''' (it's when someone added a local description) <br />
7. looks like empty <br />
8. MediaWiki (some .js and .css ... is it to archive ?) <br />
9. looks like empty <br />
<br />
'''10. Template''' <br />
11. Template talk <br />
12. Help (about wiki) <br />
13. Help talk <br />
<br />
'''14. Category''' <br />
15. Category talk <br />
<br />
100. Guild <br />
101. Guild talk <br />
<br />
104. Event<br />
105. Event talk<br />
<br />
=== FR ns ===<br />
[[Wiki Technical Guide/FR ns liste]]<br />
<br />
== templates ==<br />
<br />
== users ==<br />
<br />
<br />
== categories ==<br />
<br />
== pages ==</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=30522Wiki Technical Guide2019-06-30T13:48:27Z<p>Amosys: /* Wiki codes about categories */</p>
<hr />
<div><noinclude>{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=4<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}</noinclude><br />
'''''A short technical guide for experienced contributors and documentation managers.''''' See [[Writing Guide]] for basic wiki knowledge.<br />
<br />
=='''<big>Working as a team</big>'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''<code><nowiki>[[Talk:{{FULLPAGENAME}}]]</nowiki></code>'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''<code><nowiki>===Title of the topic==</nowiki></code>'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''<code><nowiki>~~~~</nowiki></code>'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more <code>:</code> than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''<code><nowiki>==Title of the topic {{OK}}==</nowiki></code>'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''<code><nowiki>{{KO}}</nowiki></code>'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''<big>Translations</big>'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''<big>Edition</big>'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''<code><nowiki><!--</nowiki></code>''' and to follow it with '''<code><nowiki>--></nowiki></code>'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''<code><nowiki><noinclude><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></noinclude></nowiki></code>'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''<code><nowiki>{{WIP|~~~~}}</nowiki></code>''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''<code><nowiki>{{WIP}}</nowiki></code>'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''<code><nowiki>[[Utilisateur:Zorroargh/Brouillons/...]]</nowiki></code>'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''<big>Validation of content</big>'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
<big>A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.</big><br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''<code><nowiki>{{Official Lore}}</nowiki></code>''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''<code><nowiki>{{Lore Validation Request}}</nowiki></code>''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''<big>Categories</big>'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
<div style="text-align:center;"><br />
{{3DText|3D=outset|group=ranger|text=<span style="font-size:large;font-variant: small-caps;font-weight: bold;">'''''Portal …'''''</span>}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''<code><nowiki>There are for now {{Number of pages}} pages on …</nowiki></code>'''<br />
</div><br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use <code><nowiki>{{Number of pages}}</nowiki></code> that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article <big>'''''[[Categorization]]'''''</big>. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
<div style="text-align:center;">'''—• Six wikis, six category systems, all images in common •—'''</div><br />
<br />
=='''<big>Template</big>'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
<br />
===Naming your Template===<br />
Some rules for naming templates.<br />
<br />
===All templates===<br />
<big>'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.</big><br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''<big>Portal</big>'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''<code><nowiki>{{Portal bottom}}</nowiki></code>'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''<code><nowiki>{{Portal bottom}}</nowiki></code>''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''<code><nowiki>{{:DOCNAME}}</nowiki></code>''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class="wikitable centre"<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || <nowiki>{{:Featured article/...}}</nowiki> || <nowiki>{{:Lumière sur/...}}</nowiki><br />
|-<br />
| Every day of the week || <nowiki>{{:Featured article/GBA/Week/{{CURRENTDOW}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}</nowiki><br />
|-<br />
| Every day of the month || <nowiki>{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}</nowiki><br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''<pre><nowiki>{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|xxx}}<br />
[[Category:yyyy]]</noinclude></nowiki></pre>'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''<code><nowiki><noinclude></nowiki></code>''' and '''<code><nowiki></noinclude></noinclude></nowiki></code>''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''<code><nowiki><onlyinclude></nowiki></code>''' and '''<code><nowiki></onlyinclude></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''<code><nowiki><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''<code><nowiki>{{read more|<<the original article>}}</nowiki></code>''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''<big>Home page</big>'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
<br />
== Other advanced stuffs ==<br />
API, tips on Special commands...<br />
=== namespaces ===<br />
Code used: <nowiki>{{Special:AllPages|namespace=1}}</nowiki><br />
<br />
Usually, the talk has ns+1. To be bief, no talk here (see more detailled pages) BUT un-usual.<br />
<br />
Commons to all:<br />
<br />
*Namespace 1 - Talk (in fr Discussion)<br />
*Namespace 2 - User (in fr, or Utilisateur or Utilisatrices)<br />
* Namespace 6 - File - Fichier <br />
*Namespace 8 - MediaWiki <br />
*Namespace 10 - Modèle - Template <br />
*Namespace 12 - Aide - Help<br />
*Namespace 14 - Category - Catégorie<br />
<br />
==== FR ns ====<br />
see [[:fr:Guide Technique du wiki/FR ns liste]] (commands are KO in here)<br />
<br />
Namespace 4 - '''EncyclopAtys'''<br />
<br />
Namespace 100 - Guilde<br />
<br />
Namespace 106 - '''Portail - Portal'''<br />
<br />
==== EN ns ====<br />
see [[Wiki Technical Guide/EN ns list]]<br />
<br />
But:<br />
*Namespace '''4 - Ryzom Wiki''' and 5 Namespace 5 - Ryzom Wiki talk<br />
*Namespace '''104 - Event'''<br />
<br />
==== DE ns ====<br />
[[:de:Technischer Wiki-Leitfaden/DE ns list]]<br />
<br />
Looks like the EN, but no Event namespace, less pages and talk<br />
<br />
==== Atys Common ns ====<br />
See [https://atys.wiki.ryzom.com/wiki/User:Heernis/Common_ns_list Common ns list on atys common]<br />
<br />
As the DE/EN wikis: User (ns 2), File (ns 6), Template 10, Help (ns 12) 3p, Category (ns 14)<br />
<br />
* Namespace 4 - '''Ryzom Commons (ns 4)'''<br />
<br />
=== Wiki codes about categories ===<br />
* on common, Heernis used <nowiki><categorytree mode="all" depth="20" showcount"on" hideprefix="never">Wikipatys</categorytree></nowiki> to get result: Wikipatys, Deutsch, English, Graphic Charter, Hidden categories<br />
* The code <nowiki><categorytree>Foo</categorytree></nowiki> on a wiki page, will show the contents of '''category Foo''' as a dynamic tree on that page.<br />
<br />
<br />
From https://www.mediawiki.org/wiki/Extension:CategoryTree#Usage :<br />
* let's try a all mode on Encyclopatys <nowiki><categorytree mode="all" depth="20" showcount"on" hideprefix="never">Encyclopatys</categorytree></nowiki>:<br />
<categorytree style="margin-left: 30px;" mode="all" depth="20" showcount"on" hideprefix="never">Encyclopatys</categorytree><br />
* a parent mode <nowiki><categorytree mode="parents" depth="20" showcount"on" hideprefix="never">Mysteries</categorytree></nowiki>:<br />
<categorytree style="margin-left: 30px;" mode="parents" depth="20" showcount"on" hideprefix="never">Mysteries</categorytree><br />
* let's try an other <nowiki><categorytree namespaces="talk" style="margin-left: 30px;" mode="pages" depth="20" >Encyclopatys</categorytree></nowiki> plus categories:<br />
<categorytree style="margin-left: 30px;" mode="pages" depth="20" namespaces="talk<br />
Category">Encyclopatys</categorytree><br />
<br />
<br />
* With mode=parents we can see all parents of a category :) But how from EN wiki get the FR/EN values ? (tried fr:CategoryName and :fr:CategoryName)<br />
* depth default is 1. 0 will give roots categories<br />
* hideroot: set this to "on" to hide the "root" node of the tree (ex: <nowiki>hideroot=on</nowiki>)<br />
* The <nowiki>{{#categorytree:Foo|hideroot|mode=pages}}</nowiki> parser function, same but with other syntax. Using the parser function syntax has the advantage that it allows you to use [https://www.mediawiki.org/wiki/Help:Magic_words magic words] (such <nowiki>{{#categorytree:{{PAGENAME}}}}</nowiki>), templates (<nowiki>{{#categorytree:{{root category}}}}</nowiki>) and template parameters when specifying the category to show.<br />
<br />
=== Other links ===<br />
*[[Wiki Technical Guide/Special Pages]]<br />
* [[Wiki Technical Guide/API]]<br />
<br />
Other usefull links<br />
* https://regex101.com/<br />
* https://www.mediawiki.org/wiki/Manual%3APywikibot and [[User:Amosys/Pywiki]] (for tests)<br />
<br />
<br />
<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=30520Wiki Technical Guide2019-06-30T13:20:11Z<p>Amosys: /* Wiki codes about categories */</p>
<hr />
<div><noinclude>{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=4<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}</noinclude><br />
'''''A short technical guide for experienced contributors and documentation managers.''''' See [[Writing Guide]] for basic wiki knowledge.<br />
<br />
=='''<big>Working as a team</big>'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''<code><nowiki>[[Talk:{{FULLPAGENAME}}]]</nowiki></code>'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''<code><nowiki>===Title of the topic==</nowiki></code>'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''<code><nowiki>~~~~</nowiki></code>'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more <code>:</code> than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''<code><nowiki>==Title of the topic {{OK}}==</nowiki></code>'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''<code><nowiki>{{KO}}</nowiki></code>'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''<big>Translations</big>'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''<big>Edition</big>'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''<code><nowiki><!--</nowiki></code>''' and to follow it with '''<code><nowiki>--></nowiki></code>'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''<code><nowiki><noinclude><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></noinclude></nowiki></code>'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''<code><nowiki>{{WIP|~~~~}}</nowiki></code>''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''<code><nowiki>{{WIP}}</nowiki></code>'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''<code><nowiki>[[Utilisateur:Zorroargh/Brouillons/...]]</nowiki></code>'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''<big>Validation of content</big>'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
<big>A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.</big><br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''<code><nowiki>{{Official Lore}}</nowiki></code>''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''<code><nowiki>{{Lore Validation Request}}</nowiki></code>''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''<big>Categories</big>'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
<div style="text-align:center;"><br />
{{3DText|3D=outset|group=ranger|text=<span style="font-size:large;font-variant: small-caps;font-weight: bold;">'''''Portal …'''''</span>}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''<code><nowiki>There are for now {{Number of pages}} pages on …</nowiki></code>'''<br />
</div><br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use <code><nowiki>{{Number of pages}}</nowiki></code> that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article <big>'''''[[Categorization]]'''''</big>. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
<div style="text-align:center;">'''—• Six wikis, six category systems, all images in common •—'''</div><br />
<br />
=='''<big>Template</big>'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
<br />
===Naming your Template===<br />
Some rules for naming templates.<br />
<br />
===All templates===<br />
<big>'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.</big><br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''<big>Portal</big>'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''<code><nowiki>{{Portal bottom}}</nowiki></code>'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''<code><nowiki>{{Portal bottom}}</nowiki></code>''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''<code><nowiki>{{:DOCNAME}}</nowiki></code>''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class="wikitable centre"<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || <nowiki>{{:Featured article/...}}</nowiki> || <nowiki>{{:Lumière sur/...}}</nowiki><br />
|-<br />
| Every day of the week || <nowiki>{{:Featured article/GBA/Week/{{CURRENTDOW}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}</nowiki><br />
|-<br />
| Every day of the month || <nowiki>{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}</nowiki><br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''<pre><nowiki>{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|xxx}}<br />
[[Category:yyyy]]</noinclude></nowiki></pre>'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''<code><nowiki><noinclude></nowiki></code>''' and '''<code><nowiki></noinclude></noinclude></nowiki></code>''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''<code><nowiki><onlyinclude></nowiki></code>''' and '''<code><nowiki></onlyinclude></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''<code><nowiki><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''<code><nowiki>{{read more|<<the original article>}}</nowiki></code>''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''<big>Home page</big>'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
<br />
== Other advanced stuffs ==<br />
API, tips on Special commands...<br />
=== namespaces ===<br />
Code used: <nowiki>{{Special:AllPages|namespace=1}}</nowiki><br />
<br />
Usually, the talk has ns+1. To be bief, no talk here (see more detailled pages) BUT un-usual.<br />
<br />
Commons to all:<br />
<br />
*Namespace 1 - Talk (in fr Discussion)<br />
*Namespace 2 - User (in fr, or Utilisateur or Utilisatrices)<br />
* Namespace 6 - File - Fichier <br />
*Namespace 8 - MediaWiki <br />
*Namespace 10 - Modèle - Template <br />
*Namespace 12 - Aide - Help<br />
*Namespace 14 - Category - Catégorie<br />
<br />
==== FR ns ====<br />
see [[:fr:Guide Technique du wiki/FR ns liste]] (commands are KO in here)<br />
<br />
Namespace 4 - '''EncyclopAtys'''<br />
<br />
Namespace 100 - Guilde<br />
<br />
Namespace 106 - '''Portail - Portal'''<br />
<br />
==== EN ns ====<br />
see [[Wiki Technical Guide/EN ns list]]<br />
<br />
But:<br />
*Namespace '''4 - Ryzom Wiki''' and 5 Namespace 5 - Ryzom Wiki talk<br />
*Namespace '''104 - Event'''<br />
<br />
==== DE ns ====<br />
[[:de:Technischer Wiki-Leitfaden/DE ns list]]<br />
<br />
Looks like the EN, but no Event namespace, less pages and talk<br />
<br />
==== Atys Common ns ====<br />
See [https://atys.wiki.ryzom.com/wiki/User:Heernis/Common_ns_list Common ns list on atys common]<br />
<br />
As the DE/EN wikis: User (ns 2), File (ns 6), Template 10, Help (ns 12) 3p, Category (ns 14)<br />
<br />
* Namespace 4 - '''Ryzom Commons (ns 4)'''<br />
<br />
=== Wiki codes about categories ===<br />
* on common, Heernis used <nowiki><categorytree mode="all" depth="20" showcount"on" hideprefix="never">Wikipatys</categorytree></nowiki> to get result: Wikipatys, Deutsch, English, Graphic Charter, Hidden categories<br />
* The code <nowiki><categorytree>Foo</categorytree></nowiki> on a wiki page, will show the contents of '''category Foo''' as a dynamic tree on that page.<br />
<br />
<br />
From https://www.mediawiki.org/wiki/Extension:CategoryTree#Usage :<br />
* let's try a all mode on Encyclopatys <nowiki><categorytree mode="all" depth="20" showcount"on" hideprefix="never">Encyclopatys</categorytree></nowiki>:<br />
<categorytree mode="all" depth="20" showcount"on" hideprefix="never">Encyclopatys</categorytree><br />
* a parent mode <nowiki><categorytree mode="parents" depth="20" showcount"on" hideprefix="never">Mysteries</categorytree></nowiki>:<br />
<categorytree mode="parents" depth="20" showcount"on" hideprefix="never">Mysteries</categorytree><br />
* let's try an other hideprefix <nowiki><categorytree mode="all" depth="20" showcount"on" hideprefix="categories" style=""margin-left:50px">Encyclopatys</categorytree></nowiki>:<br />
<categorytree mode="all" depth="20" showcount"on" hideprefix="categories">Encyclopatys</categorytree><br />
<br />
<br />
* With mode=parents we can see all parents of a category :) But how from EN wiki get the FR/EN values ? (tried fr:CategoryName and :fr:CategoryName)<br />
* depth default is 1. 0 will give roots categories<br />
* hideroot: set this to "on" to hide the "root" node of the tree (ex: <nowiki>hideroot=on</nowiki>)<br />
<br />
=== Other links ===<br />
*[[Wiki Technical Guide/Special Pages]]<br />
* [[Wiki Technical Guide/API]]<br />
<br />
Other usefull links<br />
* https://regex101.com/<br />
* https://www.mediawiki.org/wiki/Manual%3APywikibot and [[User:Amosys/Pywiki]] (for tests)<br />
<br />
<br />
<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=30519Wiki Technical Guide2019-06-30T13:16:55Z<p>Amosys: /* Wiki codes about categories */</p>
<hr />
<div><noinclude>{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=4<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}</noinclude><br />
'''''A short technical guide for experienced contributors and documentation managers.''''' See [[Writing Guide]] for basic wiki knowledge.<br />
<br />
=='''<big>Working as a team</big>'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''<code><nowiki>[[Talk:{{FULLPAGENAME}}]]</nowiki></code>'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''<code><nowiki>===Title of the topic==</nowiki></code>'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''<code><nowiki>~~~~</nowiki></code>'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more <code>:</code> than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''<code><nowiki>==Title of the topic {{OK}}==</nowiki></code>'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''<code><nowiki>{{KO}}</nowiki></code>'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''<big>Translations</big>'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''<big>Edition</big>'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''<code><nowiki><!--</nowiki></code>''' and to follow it with '''<code><nowiki>--></nowiki></code>'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''<code><nowiki><noinclude><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></noinclude></nowiki></code>'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''<code><nowiki>{{WIP|~~~~}}</nowiki></code>''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''<code><nowiki>{{WIP}}</nowiki></code>'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''<code><nowiki>[[Utilisateur:Zorroargh/Brouillons/...]]</nowiki></code>'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''<big>Validation of content</big>'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
<big>A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.</big><br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''<code><nowiki>{{Official Lore}}</nowiki></code>''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''<code><nowiki>{{Lore Validation Request}}</nowiki></code>''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''<big>Categories</big>'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
<div style="text-align:center;"><br />
{{3DText|3D=outset|group=ranger|text=<span style="font-size:large;font-variant: small-caps;font-weight: bold;">'''''Portal …'''''</span>}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''<code><nowiki>There are for now {{Number of pages}} pages on …</nowiki></code>'''<br />
</div><br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use <code><nowiki>{{Number of pages}}</nowiki></code> that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article <big>'''''[[Categorization]]'''''</big>. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
<div style="text-align:center;">'''—• Six wikis, six category systems, all images in common •—'''</div><br />
<br />
=='''<big>Template</big>'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
<br />
===Naming your Template===<br />
Some rules for naming templates.<br />
<br />
===All templates===<br />
<big>'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.</big><br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''<big>Portal</big>'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''<code><nowiki>{{Portal bottom}}</nowiki></code>'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''<code><nowiki>{{Portal bottom}}</nowiki></code>''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''<code><nowiki>{{:DOCNAME}}</nowiki></code>''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class="wikitable centre"<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || <nowiki>{{:Featured article/...}}</nowiki> || <nowiki>{{:Lumière sur/...}}</nowiki><br />
|-<br />
| Every day of the week || <nowiki>{{:Featured article/GBA/Week/{{CURRENTDOW}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}</nowiki><br />
|-<br />
| Every day of the month || <nowiki>{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}</nowiki><br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''<pre><nowiki>{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|xxx}}<br />
[[Category:yyyy]]</noinclude></nowiki></pre>'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''<code><nowiki><noinclude></nowiki></code>''' and '''<code><nowiki></noinclude></noinclude></nowiki></code>''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''<code><nowiki><onlyinclude></nowiki></code>''' and '''<code><nowiki></onlyinclude></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''<code><nowiki><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''<code><nowiki>{{read more|<<the original article>}}</nowiki></code>''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''<big>Home page</big>'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
<br />
== Other advanced stuffs ==<br />
API, tips on Special commands...<br />
=== namespaces ===<br />
Code used: <nowiki>{{Special:AllPages|namespace=1}}</nowiki><br />
<br />
Usually, the talk has ns+1. To be bief, no talk here (see more detailled pages) BUT un-usual.<br />
<br />
Commons to all:<br />
<br />
*Namespace 1 - Talk (in fr Discussion)<br />
*Namespace 2 - User (in fr, or Utilisateur or Utilisatrices)<br />
* Namespace 6 - File - Fichier <br />
*Namespace 8 - MediaWiki <br />
*Namespace 10 - Modèle - Template <br />
*Namespace 12 - Aide - Help<br />
*Namespace 14 - Category - Catégorie<br />
<br />
==== FR ns ====<br />
see [[:fr:Guide Technique du wiki/FR ns liste]] (commands are KO in here)<br />
<br />
Namespace 4 - '''EncyclopAtys'''<br />
<br />
Namespace 100 - Guilde<br />
<br />
Namespace 106 - '''Portail - Portal'''<br />
<br />
==== EN ns ====<br />
see [[Wiki Technical Guide/EN ns list]]<br />
<br />
But:<br />
*Namespace '''4 - Ryzom Wiki''' and 5 Namespace 5 - Ryzom Wiki talk<br />
*Namespace '''104 - Event'''<br />
<br />
==== DE ns ====<br />
[[:de:Technischer Wiki-Leitfaden/DE ns list]]<br />
<br />
Looks like the EN, but no Event namespace, less pages and talk<br />
<br />
==== Atys Common ns ====<br />
See [https://atys.wiki.ryzom.com/wiki/User:Heernis/Common_ns_list Common ns list on atys common]<br />
<br />
As the DE/EN wikis: User (ns 2), File (ns 6), Template 10, Help (ns 12) 3p, Category (ns 14)<br />
<br />
* Namespace 4 - '''Ryzom Commons (ns 4)'''<br />
<br />
=== Wiki codes about categories ===<br />
* on common, Heernis used <nowiki><categorytree mode="all" depth="20" showcount"on" hideprefix="never">Wikipatys</categorytree></nowiki> to get result: Wikipatys, Deutsch, English, Graphic Charter, Hidden categories<br />
* The code <nowiki><categorytree>Foo</categorytree></nowiki> on a wiki page, will show the contents of '''category Foo''' as a dynamic tree on that page.<br />
<br />
<br />
From https://www.mediawiki.org/wiki/Extension:CategoryTree#Usage :<br />
* let's try a all mode on Encyclopatys <nowiki><categorytree mode="all" depth="20" showcount"on" hideprefix="never">Encyclopatys</categorytree></nowiki>:<br />
<categorytree mode="all" depth="20" showcount"on" hideprefix="never">Encyclopatys</categorytree><br />
* a parent mode <nowiki><categorytree mode="parents" depth="20" showcount"on" hideprefix="never">Mysteries</categorytree></nowiki>:<br />
<categorytree mode="parents" depth="20" showcount"on" hideprefix="never">Mysteries</categorytree><br />
* let's try an other hideprefix <nowiki><categorytree mode="all" depth="20" showcount"on" hideprefix="never">Encyclopatys</categorytree></nowiki>:<br />
<categorytree mode="all" depth="20" showcount"on" hideprefix="never">Encyclopatys</categorytree><br />
<br />
<br />
* With mode=parents we can see all parents of a category :) But how from EN wiki get the FR/EN values ? (tried fr:CategoryName and :fr:CategoryName)<br />
* depth default is 1. 0 will give roots categories<br />
* hideroot: set this to "on" to hide the "root" node of the tree (ex: <nowiki>hideroot=on</nowiki>)<br />
<br />
=== Other links ===<br />
*[[Wiki Technical Guide/Special Pages]]<br />
* [[Wiki Technical Guide/API]]<br />
<br />
Other usefull links<br />
* https://regex101.com/<br />
* https://www.mediawiki.org/wiki/Manual%3APywikibot and [[User:Amosys/Pywiki]] (for tests)<br />
<br />
<br />
<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=30518Wiki Technical Guide2019-06-30T12:59:43Z<p>Amosys: /* Other links */</p>
<hr />
<div><noinclude>{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=4<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}</noinclude><br />
'''''A short technical guide for experienced contributors and documentation managers.''''' See [[Writing Guide]] for basic wiki knowledge.<br />
<br />
=='''<big>Working as a team</big>'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''<code><nowiki>[[Talk:{{FULLPAGENAME}}]]</nowiki></code>'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''<code><nowiki>===Title of the topic==</nowiki></code>'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''<code><nowiki>~~~~</nowiki></code>'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more <code>:</code> than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''<code><nowiki>==Title of the topic {{OK}}==</nowiki></code>'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''<code><nowiki>{{KO}}</nowiki></code>'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''<big>Translations</big>'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''<big>Edition</big>'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''<code><nowiki><!--</nowiki></code>''' and to follow it with '''<code><nowiki>--></nowiki></code>'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''<code><nowiki><noinclude><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></noinclude></nowiki></code>'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''<code><nowiki>{{WIP|~~~~}}</nowiki></code>''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''<code><nowiki>{{WIP}}</nowiki></code>'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''<code><nowiki>[[Utilisateur:Zorroargh/Brouillons/...]]</nowiki></code>'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''<big>Validation of content</big>'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
<big>A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.</big><br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''<code><nowiki>{{Official Lore}}</nowiki></code>''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''<code><nowiki>{{Lore Validation Request}}</nowiki></code>''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''<big>Categories</big>'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
<div style="text-align:center;"><br />
{{3DText|3D=outset|group=ranger|text=<span style="font-size:large;font-variant: small-caps;font-weight: bold;">'''''Portal …'''''</span>}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''<code><nowiki>There are for now {{Number of pages}} pages on …</nowiki></code>'''<br />
</div><br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use <code><nowiki>{{Number of pages}}</nowiki></code> that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article <big>'''''[[Categorization]]'''''</big>. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
<div style="text-align:center;">'''—• Six wikis, six category systems, all images in common •—'''</div><br />
<br />
=='''<big>Template</big>'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
<br />
===Naming your Template===<br />
Some rules for naming templates.<br />
<br />
===All templates===<br />
<big>'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.</big><br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''<big>Portal</big>'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''<code><nowiki>{{Portal bottom}}</nowiki></code>'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''<code><nowiki>{{Portal bottom}}</nowiki></code>''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''<code><nowiki>{{:DOCNAME}}</nowiki></code>''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class="wikitable centre"<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || <nowiki>{{:Featured article/...}}</nowiki> || <nowiki>{{:Lumière sur/...}}</nowiki><br />
|-<br />
| Every day of the week || <nowiki>{{:Featured article/GBA/Week/{{CURRENTDOW}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}</nowiki><br />
|-<br />
| Every day of the month || <nowiki>{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}</nowiki><br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''<pre><nowiki>{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|xxx}}<br />
[[Category:yyyy]]</noinclude></nowiki></pre>'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''<code><nowiki><noinclude></nowiki></code>''' and '''<code><nowiki></noinclude></noinclude></nowiki></code>''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''<code><nowiki><onlyinclude></nowiki></code>''' and '''<code><nowiki></onlyinclude></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''<code><nowiki><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''<code><nowiki>{{read more|<<the original article>}}</nowiki></code>''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''<big>Home page</big>'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
<br />
== Other advanced stuffs ==<br />
API, tips on Special commands...<br />
=== namespaces ===<br />
Code used: <nowiki>{{Special:AllPages|namespace=1}}</nowiki><br />
<br />
Usually, the talk has ns+1. To be bief, no talk here (see more detailled pages) BUT un-usual.<br />
<br />
Commons to all:<br />
<br />
*Namespace 1 - Talk (in fr Discussion)<br />
*Namespace 2 - User (in fr, or Utilisateur or Utilisatrices)<br />
* Namespace 6 - File - Fichier <br />
*Namespace 8 - MediaWiki <br />
*Namespace 10 - Modèle - Template <br />
*Namespace 12 - Aide - Help<br />
*Namespace 14 - Category - Catégorie<br />
<br />
==== FR ns ====<br />
see [[:fr:Guide Technique du wiki/FR ns liste]] (commands are KO in here)<br />
<br />
Namespace 4 - '''EncyclopAtys'''<br />
<br />
Namespace 100 - Guilde<br />
<br />
Namespace 106 - '''Portail - Portal'''<br />
<br />
==== EN ns ====<br />
see [[Wiki Technical Guide/EN ns list]]<br />
<br />
But:<br />
*Namespace '''4 - Ryzom Wiki''' and 5 Namespace 5 - Ryzom Wiki talk<br />
*Namespace '''104 - Event'''<br />
<br />
==== DE ns ====<br />
[[:de:Technischer Wiki-Leitfaden/DE ns list]]<br />
<br />
Looks like the EN, but no Event namespace, less pages and talk<br />
<br />
==== Atys Common ns ====<br />
See [https://atys.wiki.ryzom.com/wiki/User:Heernis/Common_ns_list Common ns list on atys common]<br />
<br />
As the DE/EN wikis: User (ns 2), File (ns 6), Template 10, Help (ns 12) 3p, Category (ns 14)<br />
<br />
* Namespace 4 - '''Ryzom Commons (ns 4)'''<br />
<br />
=== Wiki codes about categories ===<br />
* on common, Heernis used <nowiki><categorytree mode="all" depth="20" showcount"on" hideprefix="never">Wikipatys</categorytree></nowiki> to get result: Wikipatys, Deutsch, English, Graphic Charter, Hidden categories<br />
<br />
From https://www.mediawiki.org/wiki/Extension:CategoryTree#Usage :<br />
<br />
* The code <nowiki><categorytree>Foo</categorytree></nowiki> on a wiki page, will show the contents of category Foo as a dynamic tree on that page.<br />
** let's try a <nowiki><categorytree>Wikipatys categorytree ex</categorytree></nowiki> : no bubcat<br />
<br />
<categorytree>Encyclopatys categorytree ex</categorytree><br />
<br />
<br />
* With mode=parents its show all parents of a category ?<br />
* depth default is 1<br />
<br />
=== Other links ===<br />
*[[Wiki Technical Guide/Special Pages]]<br />
* [[Wiki Technical Guide/API]]<br />
<br />
Other usefull links<br />
* https://regex101.com/<br />
* https://www.mediawiki.org/wiki/Manual%3APywikibot and [[User:Amosys/Pywiki]] (for tests)<br />
<br />
<br />
<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=30514Wiki Technical Guide2019-06-30T12:38:24Z<p>Amosys: /* namespaces */</p>
<hr />
<div><noinclude>{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=4<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}</noinclude><br />
'''''A short technical guide for experienced contributors and documentation managers.''''' See [[Writing Guide]] for basic wiki knowledge.<br />
<br />
=='''<big>Working as a team</big>'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''<code><nowiki>[[Talk:{{FULLPAGENAME}}]]</nowiki></code>'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''<code><nowiki>===Title of the topic==</nowiki></code>'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''<code><nowiki>~~~~</nowiki></code>'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more <code>:</code> than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''<code><nowiki>==Title of the topic {{OK}}==</nowiki></code>'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''<code><nowiki>{{KO}}</nowiki></code>'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''<big>Translations</big>'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''<big>Edition</big>'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''<code><nowiki><!--</nowiki></code>''' and to follow it with '''<code><nowiki>--></nowiki></code>'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''<code><nowiki><noinclude><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></noinclude></nowiki></code>'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''<code><nowiki>{{WIP|~~~~}}</nowiki></code>''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''<code><nowiki>{{WIP}}</nowiki></code>'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''<code><nowiki>[[Utilisateur:Zorroargh/Brouillons/...]]</nowiki></code>'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''<big>Validation of content</big>'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
<big>A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.</big><br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''<code><nowiki>{{Official Lore}}</nowiki></code>''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''<code><nowiki>{{Lore Validation Request}}</nowiki></code>''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''<big>Categories</big>'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
<div style="text-align:center;"><br />
{{3DText|3D=outset|group=ranger|text=<span style="font-size:large;font-variant: small-caps;font-weight: bold;">'''''Portal …'''''</span>}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''<code><nowiki>There are for now {{Number of pages}} pages on …</nowiki></code>'''<br />
</div><br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use <code><nowiki>{{Number of pages}}</nowiki></code> that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article <big>'''''[[Categorization]]'''''</big>. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
<div style="text-align:center;">'''—• Six wikis, six category systems, all images in common •—'''</div><br />
<br />
=='''<big>Template</big>'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
<br />
===Naming your Template===<br />
Some rules for naming templates.<br />
<br />
===All templates===<br />
<big>'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.</big><br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''<big>Portal</big>'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''<code><nowiki>{{Portal bottom}}</nowiki></code>'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''<code><nowiki>{{Portal bottom}}</nowiki></code>''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''<code><nowiki>{{:DOCNAME}}</nowiki></code>''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class="wikitable centre"<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || <nowiki>{{:Featured article/...}}</nowiki> || <nowiki>{{:Lumière sur/...}}</nowiki><br />
|-<br />
| Every day of the week || <nowiki>{{:Featured article/GBA/Week/{{CURRENTDOW}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}</nowiki><br />
|-<br />
| Every day of the month || <nowiki>{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}</nowiki><br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''<pre><nowiki>{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|xxx}}<br />
[[Category:yyyy]]</noinclude></nowiki></pre>'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''<code><nowiki><noinclude></nowiki></code>''' and '''<code><nowiki></noinclude></noinclude></nowiki></code>''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''<code><nowiki><onlyinclude></nowiki></code>''' and '''<code><nowiki></onlyinclude></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''<code><nowiki><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''<code><nowiki>{{read more|<<the original article>}}</nowiki></code>''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''<big>Home page</big>'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
<br />
== Other advanced stuffs ==<br />
API, tips on Special commands...<br />
=== namespaces ===<br />
Code used: <nowiki>{{Special:AllPages|namespace=1}}</nowiki><br />
<br />
Usually, the talk has ns+1. To be bief, no talk here (see more detailled pages) BUT un-usual.<br />
<br />
Commons to all:<br />
<br />
*Namespace 1 - Talk (in fr Discussion)<br />
*Namespace 2 - User (in fr, or Utilisateur or Utilisatrices)<br />
* Namespace 6 - File - Fichier <br />
*Namespace 8 - MediaWiki <br />
*Namespace 10 - Modèle - Template <br />
*Namespace 12 - Aide - Help<br />
*Namespace 14 - Category - Catégorie<br />
<br />
==== FR ns ====<br />
see [[:fr:Guide Technique du wiki/FR ns liste]] (commands are KO in here)<br />
<br />
Namespace 4 - '''EncyclopAtys'''<br />
<br />
Namespace 100 - Guilde<br />
<br />
Namespace 106 - '''Portail - Portal'''<br />
<br />
==== EN ns ====<br />
see [[Wiki Technical Guide/EN ns list]]<br />
<br />
But:<br />
*Namespace '''4 - Ryzom Wiki''' and 5 Namespace 5 - Ryzom Wiki talk<br />
*Namespace '''104 - Event'''<br />
<br />
==== DE ns ====<br />
[[:de:Technischer Wiki-Leitfaden/DE ns list]]<br />
<br />
Looks like the EN, but no Event namespace, less pages and talk<br />
<br />
==== Atys Common ns ====<br />
See [https://atys.wiki.ryzom.com/wiki/User:Heernis/Common_ns_list Common ns list on atys common]<br />
<br />
As the DE/EN wikis: User (ns 2), File (ns 6), Template 10, Help (ns 12) 3p, Category (ns 14)<br />
<br />
* Namespace 4 - '''Ryzom Commons (ns 4)'''<br />
<br />
=== Other links ===<br />
*[[Wiki Technical Guide/Special Pages]]<br />
* [[Wiki Technical Guide/API]]<br />
<br />
Other usefull links<br />
* https://regex101.com/<br />
* https://www.mediawiki.org/wiki/Manual%3APywikibot and [[User:Amosys/Pywiki]] (for tests)<br />
<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=30513Wiki Technical Guide2019-06-30T12:33:47Z<p>Amosys: /* FR ns */</p>
<hr />
<div><noinclude>{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=4<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}</noinclude><br />
'''''A short technical guide for experienced contributors and documentation managers.''''' See [[Writing Guide]] for basic wiki knowledge.<br />
<br />
=='''<big>Working as a team</big>'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''<code><nowiki>[[Talk:{{FULLPAGENAME}}]]</nowiki></code>'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''<code><nowiki>===Title of the topic==</nowiki></code>'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''<code><nowiki>~~~~</nowiki></code>'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more <code>:</code> than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''<code><nowiki>==Title of the topic {{OK}}==</nowiki></code>'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''<code><nowiki>{{KO}}</nowiki></code>'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''<big>Translations</big>'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''<big>Edition</big>'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''<code><nowiki><!--</nowiki></code>''' and to follow it with '''<code><nowiki>--></nowiki></code>'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''<code><nowiki><noinclude><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></noinclude></nowiki></code>'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''<code><nowiki>{{WIP|~~~~}}</nowiki></code>''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''<code><nowiki>{{WIP}}</nowiki></code>'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''<code><nowiki>[[Utilisateur:Zorroargh/Brouillons/...]]</nowiki></code>'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''<big>Validation of content</big>'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
<big>A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.</big><br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''<code><nowiki>{{Official Lore}}</nowiki></code>''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''<code><nowiki>{{Lore Validation Request}}</nowiki></code>''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''<big>Categories</big>'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
<div style="text-align:center;"><br />
{{3DText|3D=outset|group=ranger|text=<span style="font-size:large;font-variant: small-caps;font-weight: bold;">'''''Portal …'''''</span>}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''<code><nowiki>There are for now {{Number of pages}} pages on …</nowiki></code>'''<br />
</div><br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use <code><nowiki>{{Number of pages}}</nowiki></code> that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article <big>'''''[[Categorization]]'''''</big>. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
<div style="text-align:center;">'''—• Six wikis, six category systems, all images in common •—'''</div><br />
<br />
=='''<big>Template</big>'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
<br />
===Naming your Template===<br />
Some rules for naming templates.<br />
<br />
===All templates===<br />
<big>'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.</big><br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''<big>Portal</big>'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''<code><nowiki>{{Portal bottom}}</nowiki></code>'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''<code><nowiki>{{Portal bottom}}</nowiki></code>''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''<code><nowiki>{{:DOCNAME}}</nowiki></code>''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class="wikitable centre"<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || <nowiki>{{:Featured article/...}}</nowiki> || <nowiki>{{:Lumière sur/...}}</nowiki><br />
|-<br />
| Every day of the week || <nowiki>{{:Featured article/GBA/Week/{{CURRENTDOW}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}</nowiki><br />
|-<br />
| Every day of the month || <nowiki>{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}</nowiki><br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''<pre><nowiki>{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|xxx}}<br />
[[Category:yyyy]]</noinclude></nowiki></pre>'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''<code><nowiki><noinclude></nowiki></code>''' and '''<code><nowiki></noinclude></noinclude></nowiki></code>''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''<code><nowiki><onlyinclude></nowiki></code>''' and '''<code><nowiki></onlyinclude></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''<code><nowiki><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''<code><nowiki>{{read more|<<the original article>}}</nowiki></code>''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''<big>Home page</big>'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
<br />
== Other advanced stuffs ==<br />
API, tips on Special commands...<br />
=== namespaces ===<br />
Code used: <nowiki>{{Special:AllPages|namespace=1}}</nowiki><br />
<br />
Usually, the talk has ns+1. To be bief, no talk here (see more detailled pages) BUt un-usual.<br />
==== FR ns ====<br />
see [[:fr:Guide Technique du wiki/FR ns liste]] (commands are KO in here)<br />
<br />
Namespace 1 - Talk (in fr Discussion)<br />
<br />
Namespace 2 - User (in fr, or Utilisateur or Utilisatrices)<br />
<br />
Namespace 4 - '''EncyclopAtys'''<br />
<br />
Namespace 6 - File - Fichier <br />
<br />
Namespace 8 - MediaWiki <br />
<br />
<br />
Namespace 10 - Modèle - Template <br />
<br />
Namespace 12 - Aide - Help<br />
<br />
<br />
Namespace 14 - Category - Catégorie<br />
<br />
Namespace 100 - Guilde<br />
<br />
Namespace 106 - '''Portail - Portal'''<br />
<br />
==== EN ns ====<br />
see [[Wiki Technical Guide/EN ns list]]<br />
<br />
same as FR but:<br />
* Namespace 1 - Talk<br />
*Namespace '''4 - Ryzom Wiki''' and 5 Namespace 5 - Ryzom Wiki talk<br />
*Namespace '''104 - Event'''<br />
<br />
==== DE ns ====<br />
[[:de:Technischer Wiki-Leitfaden/DE ns list]]<br />
<br />
Looks like the EN, but no Event namespace, less pages and talk<br />
<br />
==== Atys Common ns ====<br />
See [https://atys.wiki.ryzom.com/wiki/User:Heernis/Common_ns_list Common ns list on atys common]<br />
<br />
As the DE/EN wikis: User (ns 2), File (ns 6), Template 10, Help (ns 12) 3p, Category (ns 14)<br />
<br />
* '''Ryzom Commons (ns 4)'''<br />
<br />
=== Other links ===<br />
*[[Wiki Technical Guide/Special Pages]]<br />
* [[Wiki Technical Guide/API]]<br />
<br />
Other usefull links<br />
* https://regex101.com/<br />
* https://www.mediawiki.org/wiki/Manual%3APywikibot and [[User:Amosys/Pywiki]] (for tests)<br />
<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=30512Wiki Technical Guide2019-06-30T12:32:08Z<p>Amosys: /* EN ns */</p>
<hr />
<div><noinclude>{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=4<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}</noinclude><br />
'''''A short technical guide for experienced contributors and documentation managers.''''' See [[Writing Guide]] for basic wiki knowledge.<br />
<br />
=='''<big>Working as a team</big>'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''<code><nowiki>[[Talk:{{FULLPAGENAME}}]]</nowiki></code>'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''<code><nowiki>===Title of the topic==</nowiki></code>'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''<code><nowiki>~~~~</nowiki></code>'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more <code>:</code> than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''<code><nowiki>==Title of the topic {{OK}}==</nowiki></code>'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''<code><nowiki>{{KO}}</nowiki></code>'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''<big>Translations</big>'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''<big>Edition</big>'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''<code><nowiki><!--</nowiki></code>''' and to follow it with '''<code><nowiki>--></nowiki></code>'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''<code><nowiki><noinclude><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></noinclude></nowiki></code>'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''<code><nowiki>{{WIP|~~~~}}</nowiki></code>''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''<code><nowiki>{{WIP}}</nowiki></code>'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''<code><nowiki>[[Utilisateur:Zorroargh/Brouillons/...]]</nowiki></code>'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''<big>Validation of content</big>'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
<big>A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.</big><br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''<code><nowiki>{{Official Lore}}</nowiki></code>''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''<code><nowiki>{{Lore Validation Request}}</nowiki></code>''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''<big>Categories</big>'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
<div style="text-align:center;"><br />
{{3DText|3D=outset|group=ranger|text=<span style="font-size:large;font-variant: small-caps;font-weight: bold;">'''''Portal …'''''</span>}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''<code><nowiki>There are for now {{Number of pages}} pages on …</nowiki></code>'''<br />
</div><br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use <code><nowiki>{{Number of pages}}</nowiki></code> that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article <big>'''''[[Categorization]]'''''</big>. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
<div style="text-align:center;">'''—• Six wikis, six category systems, all images in common •—'''</div><br />
<br />
=='''<big>Template</big>'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
<br />
===Naming your Template===<br />
Some rules for naming templates.<br />
<br />
===All templates===<br />
<big>'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.</big><br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''<big>Portal</big>'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''<code><nowiki>{{Portal bottom}}</nowiki></code>'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''<code><nowiki>{{Portal bottom}}</nowiki></code>''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''<code><nowiki>{{:DOCNAME}}</nowiki></code>''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class="wikitable centre"<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || <nowiki>{{:Featured article/...}}</nowiki> || <nowiki>{{:Lumière sur/...}}</nowiki><br />
|-<br />
| Every day of the week || <nowiki>{{:Featured article/GBA/Week/{{CURRENTDOW}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}</nowiki><br />
|-<br />
| Every day of the month || <nowiki>{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}</nowiki><br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''<pre><nowiki>{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|xxx}}<br />
[[Category:yyyy]]</noinclude></nowiki></pre>'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''<code><nowiki><noinclude></nowiki></code>''' and '''<code><nowiki></noinclude></noinclude></nowiki></code>''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''<code><nowiki><onlyinclude></nowiki></code>''' and '''<code><nowiki></onlyinclude></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''<code><nowiki><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''<code><nowiki>{{read more|<<the original article>}}</nowiki></code>''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''<big>Home page</big>'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
<br />
== Other advanced stuffs ==<br />
API, tips on Special commands...<br />
=== namespaces ===<br />
Code used: <nowiki>{{Special:AllPages|namespace=1}}</nowiki><br />
<br />
Usually, the talk has ns+1. To be bief, no talk here (see more detailled pages) BUt un-usual.<br />
==== FR ns ====<br />
see [[:fr:Guide Technique du wiki/FR ns liste]] (commands are KO in here)<br />
<br />
Namespace 1 - ARK talk <br />
<br />
Namespace 2 - Utilisateur et Utilisatrices - User<br />
<br />
Namespace 4 - '''EncyclopAtys'''<br />
<br />
Namespace 6 - File - Fichier <br />
<br />
Namespace 8 - MediaWiki <br />
<br />
<br />
Namespace 10 - Modèle - Template <br />
<br />
Namespace 12 - Aide - Help<br />
<br />
<br />
Namespace 14 - Catégorie - Category <br />
<br />
Namespace 100 - Guilde<br />
<br />
Namespace 106 - '''Portail - Portal'''<br />
<br />
==== EN ns ====<br />
see [[Wiki Technical Guide/EN ns list]]<br />
<br />
same as FR but:<br />
* Namespace 1 - Talk<br />
*Namespace '''4 - Ryzom Wiki''' and 5 Namespace 5 - Ryzom Wiki talk<br />
*Namespace '''104 - Event'''<br />
<br />
==== DE ns ====<br />
[[:de:Technischer Wiki-Leitfaden/DE ns list]]<br />
<br />
Looks like the EN, but no Event namespace, less pages and talk<br />
<br />
==== Atys Common ns ====<br />
See [https://atys.wiki.ryzom.com/wiki/User:Heernis/Common_ns_list Common ns list on atys common]<br />
<br />
As the DE/EN wikis: User (ns 2), File (ns 6), Template 10, Help (ns 12) 3p, Category (ns 14)<br />
<br />
* '''Ryzom Commons (ns 4)'''<br />
<br />
=== Other links ===<br />
*[[Wiki Technical Guide/Special Pages]]<br />
* [[Wiki Technical Guide/API]]<br />
<br />
Other usefull links<br />
* https://regex101.com/<br />
* https://www.mediawiki.org/wiki/Manual%3APywikibot and [[User:Amosys/Pywiki]] (for tests)<br />
<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=30511Wiki Technical Guide2019-06-30T12:29:38Z<p>Amosys: /* Atys Common ns */</p>
<hr />
<div><noinclude>{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=4<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}</noinclude><br />
'''''A short technical guide for experienced contributors and documentation managers.''''' See [[Writing Guide]] for basic wiki knowledge.<br />
<br />
=='''<big>Working as a team</big>'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''<code><nowiki>[[Talk:{{FULLPAGENAME}}]]</nowiki></code>'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''<code><nowiki>===Title of the topic==</nowiki></code>'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''<code><nowiki>~~~~</nowiki></code>'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more <code>:</code> than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''<code><nowiki>==Title of the topic {{OK}}==</nowiki></code>'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''<code><nowiki>{{KO}}</nowiki></code>'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''<big>Translations</big>'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''<big>Edition</big>'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''<code><nowiki><!--</nowiki></code>''' and to follow it with '''<code><nowiki>--></nowiki></code>'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''<code><nowiki><noinclude><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></noinclude></nowiki></code>'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''<code><nowiki>{{WIP|~~~~}}</nowiki></code>''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''<code><nowiki>{{WIP}}</nowiki></code>'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''<code><nowiki>[[Utilisateur:Zorroargh/Brouillons/...]]</nowiki></code>'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''<big>Validation of content</big>'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
<big>A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.</big><br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''<code><nowiki>{{Official Lore}}</nowiki></code>''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''<code><nowiki>{{Lore Validation Request}}</nowiki></code>''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''<big>Categories</big>'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
<div style="text-align:center;"><br />
{{3DText|3D=outset|group=ranger|text=<span style="font-size:large;font-variant: small-caps;font-weight: bold;">'''''Portal …'''''</span>}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''<code><nowiki>There are for now {{Number of pages}} pages on …</nowiki></code>'''<br />
</div><br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use <code><nowiki>{{Number of pages}}</nowiki></code> that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article <big>'''''[[Categorization]]'''''</big>. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
<div style="text-align:center;">'''—• Six wikis, six category systems, all images in common •—'''</div><br />
<br />
=='''<big>Template</big>'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
<br />
===Naming your Template===<br />
Some rules for naming templates.<br />
<br />
===All templates===<br />
<big>'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.</big><br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''<big>Portal</big>'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''<code><nowiki>{{Portal bottom}}</nowiki></code>'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''<code><nowiki>{{Portal bottom}}</nowiki></code>''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''<code><nowiki>{{:DOCNAME}}</nowiki></code>''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class="wikitable centre"<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || <nowiki>{{:Featured article/...}}</nowiki> || <nowiki>{{:Lumière sur/...}}</nowiki><br />
|-<br />
| Every day of the week || <nowiki>{{:Featured article/GBA/Week/{{CURRENTDOW}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}</nowiki><br />
|-<br />
| Every day of the month || <nowiki>{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}</nowiki><br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''<pre><nowiki>{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|xxx}}<br />
[[Category:yyyy]]</noinclude></nowiki></pre>'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''<code><nowiki><noinclude></nowiki></code>''' and '''<code><nowiki></noinclude></noinclude></nowiki></code>''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''<code><nowiki><onlyinclude></nowiki></code>''' and '''<code><nowiki></onlyinclude></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''<code><nowiki><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''<code><nowiki>{{read more|<<the original article>}}</nowiki></code>''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''<big>Home page</big>'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
<br />
== Other advanced stuffs ==<br />
API, tips on Special commands...<br />
=== namespaces ===<br />
Code used: <nowiki>{{Special:AllPages|namespace=1}}</nowiki><br />
<br />
Usually, the talk has ns+1. To be bief, no talk here (see more detailled pages) BUt un-usual.<br />
==== FR ns ====<br />
see [[:fr:Guide Technique du wiki/FR ns liste]] (commands are KO in here)<br />
<br />
Namespace 1 - ARK talk <br />
<br />
Namespace 2 - Utilisateur et Utilisatrices - User<br />
<br />
Namespace 4 - '''EncyclopAtys'''<br />
<br />
Namespace 6 - File - Fichier <br />
<br />
Namespace 8 - MediaWiki <br />
<br />
<br />
Namespace 10 - Modèle - Template <br />
<br />
Namespace 12 - Aide - Help<br />
<br />
<br />
Namespace 14 - Catégorie - Category <br />
<br />
Namespace 100 - Guilde<br />
<br />
Namespace 106 - '''Portail - Portal'''<br />
<br />
==== EN ns ====<br />
see [[Wiki Technical Guide/EN ns list]]<br />
<br />
same as FR but:<br />
*Namespace '''4 - Ryzom Wiki''' and 5 Namespace 5 - Ryzom Wiki talk<br />
*Namespace '''104 - Event'''<br />
<br />
==== DE ns ====<br />
[[:de:Technischer Wiki-Leitfaden/DE ns list]]<br />
<br />
Looks like the EN, but no Event namespace, less pages and talk<br />
<br />
==== Atys Common ns ====<br />
See [https://atys.wiki.ryzom.com/wiki/User:Heernis/Common_ns_list Common ns list on atys common]<br />
<br />
As the DE/EN wikis: User (ns 2), File (ns 6), Template 10, Help (ns 12) 3p, Category (ns 14)<br />
<br />
* '''Ryzom Commons (ns 4)'''<br />
<br />
=== Other links ===<br />
*[[Wiki Technical Guide/Special Pages]]<br />
* [[Wiki Technical Guide/API]]<br />
<br />
Other usefull links<br />
* https://regex101.com/<br />
* https://www.mediawiki.org/wiki/Manual%3APywikibot and [[User:Amosys/Pywiki]] (for tests)<br />
<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=30510Wiki Technical Guide2019-06-30T12:29:03Z<p>Amosys: /* Atys Common ns */</p>
<hr />
<div><noinclude>{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=4<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}</noinclude><br />
'''''A short technical guide for experienced contributors and documentation managers.''''' See [[Writing Guide]] for basic wiki knowledge.<br />
<br />
=='''<big>Working as a team</big>'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''<code><nowiki>[[Talk:{{FULLPAGENAME}}]]</nowiki></code>'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''<code><nowiki>===Title of the topic==</nowiki></code>'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''<code><nowiki>~~~~</nowiki></code>'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more <code>:</code> than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''<code><nowiki>==Title of the topic {{OK}}==</nowiki></code>'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''<code><nowiki>{{KO}}</nowiki></code>'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''<big>Translations</big>'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''<big>Edition</big>'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''<code><nowiki><!--</nowiki></code>''' and to follow it with '''<code><nowiki>--></nowiki></code>'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''<code><nowiki><noinclude><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></noinclude></nowiki></code>'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''<code><nowiki>{{WIP|~~~~}}</nowiki></code>''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''<code><nowiki>{{WIP}}</nowiki></code>'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''<code><nowiki>[[Utilisateur:Zorroargh/Brouillons/...]]</nowiki></code>'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''<big>Validation of content</big>'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
<big>A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.</big><br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''<code><nowiki>{{Official Lore}}</nowiki></code>''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''<code><nowiki>{{Lore Validation Request}}</nowiki></code>''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''<big>Categories</big>'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
<div style="text-align:center;"><br />
{{3DText|3D=outset|group=ranger|text=<span style="font-size:large;font-variant: small-caps;font-weight: bold;">'''''Portal …'''''</span>}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''<code><nowiki>There are for now {{Number of pages}} pages on …</nowiki></code>'''<br />
</div><br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use <code><nowiki>{{Number of pages}}</nowiki></code> that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article <big>'''''[[Categorization]]'''''</big>. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
<div style="text-align:center;">'''—• Six wikis, six category systems, all images in common •—'''</div><br />
<br />
=='''<big>Template</big>'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
<br />
===Naming your Template===<br />
Some rules for naming templates.<br />
<br />
===All templates===<br />
<big>'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.</big><br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''<big>Portal</big>'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''<code><nowiki>{{Portal bottom}}</nowiki></code>'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''<code><nowiki>{{Portal bottom}}</nowiki></code>''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''<code><nowiki>{{:DOCNAME}}</nowiki></code>''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class="wikitable centre"<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || <nowiki>{{:Featured article/...}}</nowiki> || <nowiki>{{:Lumière sur/...}}</nowiki><br />
|-<br />
| Every day of the week || <nowiki>{{:Featured article/GBA/Week/{{CURRENTDOW}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}</nowiki><br />
|-<br />
| Every day of the month || <nowiki>{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}</nowiki><br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''<pre><nowiki>{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|xxx}}<br />
[[Category:yyyy]]</noinclude></nowiki></pre>'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''<code><nowiki><noinclude></nowiki></code>''' and '''<code><nowiki></noinclude></noinclude></nowiki></code>''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''<code><nowiki><onlyinclude></nowiki></code>''' and '''<code><nowiki></onlyinclude></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''<code><nowiki><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''<code><nowiki>{{read more|<<the original article>}}</nowiki></code>''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''<big>Home page</big>'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
<br />
== Other advanced stuffs ==<br />
API, tips on Special commands...<br />
=== namespaces ===<br />
Code used: <nowiki>{{Special:AllPages|namespace=1}}</nowiki><br />
<br />
Usually, the talk has ns+1. To be bief, no talk here (see more detailled pages) BUt un-usual.<br />
==== FR ns ====<br />
see [[:fr:Guide Technique du wiki/FR ns liste]] (commands are KO in here)<br />
<br />
Namespace 1 - ARK talk <br />
<br />
Namespace 2 - Utilisateur et Utilisatrices - User<br />
<br />
Namespace 4 - '''EncyclopAtys'''<br />
<br />
Namespace 6 - File - Fichier <br />
<br />
Namespace 8 - MediaWiki <br />
<br />
<br />
Namespace 10 - Modèle - Template <br />
<br />
Namespace 12 - Aide - Help<br />
<br />
<br />
Namespace 14 - Catégorie - Category <br />
<br />
Namespace 100 - Guilde<br />
<br />
Namespace 106 - '''Portail - Portal'''<br />
<br />
==== EN ns ====<br />
see [[Wiki Technical Guide/EN ns list]]<br />
<br />
same as FR but:<br />
*Namespace '''4 - Ryzom Wiki''' and 5 Namespace 5 - Ryzom Wiki talk<br />
*Namespace '''104 - Event'''<br />
<br />
==== DE ns ====<br />
[[:de:Technischer Wiki-Leitfaden/DE ns list]]<br />
<br />
Looks like the EN, but no Event namespace, less pages and talk<br />
<br />
==== Atys Common ns ====<br />
See [https://atys.wiki.ryzom.com/wiki/User:Heernis/Common_ns_list Common ns list on atys common]<br />
<br />
As the DE/EN wikis: User (ns 2), File (ns 6), Template 10, Help (ns 12) 3p, Category (ns 14)<br />
<br />
Ryzom Commons (ns 4)<br />
<br />
=== Other links ===<br />
*[[Wiki Technical Guide/Special Pages]]<br />
* [[Wiki Technical Guide/API]]<br />
<br />
Other usefull links<br />
* https://regex101.com/<br />
* https://www.mediawiki.org/wiki/Manual%3APywikibot and [[User:Amosys/Pywiki]] (for tests)<br />
<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=30509Wiki Technical Guide2019-06-30T11:57:14Z<p>Amosys: /* DE ns */</p>
<hr />
<div><noinclude>{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=4<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}</noinclude><br />
'''''A short technical guide for experienced contributors and documentation managers.''''' See [[Writing Guide]] for basic wiki knowledge.<br />
<br />
=='''<big>Working as a team</big>'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''<code><nowiki>[[Talk:{{FULLPAGENAME}}]]</nowiki></code>'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''<code><nowiki>===Title of the topic==</nowiki></code>'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''<code><nowiki>~~~~</nowiki></code>'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more <code>:</code> than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''<code><nowiki>==Title of the topic {{OK}}==</nowiki></code>'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''<code><nowiki>{{KO}}</nowiki></code>'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''<big>Translations</big>'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''<big>Edition</big>'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''<code><nowiki><!--</nowiki></code>''' and to follow it with '''<code><nowiki>--></nowiki></code>'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''<code><nowiki><noinclude><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></noinclude></nowiki></code>'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''<code><nowiki>{{WIP|~~~~}}</nowiki></code>''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''<code><nowiki>{{WIP}}</nowiki></code>'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''<code><nowiki>[[Utilisateur:Zorroargh/Brouillons/...]]</nowiki></code>'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''<big>Validation of content</big>'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
<big>A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.</big><br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''<code><nowiki>{{Official Lore}}</nowiki></code>''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''<code><nowiki>{{Lore Validation Request}}</nowiki></code>''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''<big>Categories</big>'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
<div style="text-align:center;"><br />
{{3DText|3D=outset|group=ranger|text=<span style="font-size:large;font-variant: small-caps;font-weight: bold;">'''''Portal …'''''</span>}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''<code><nowiki>There are for now {{Number of pages}} pages on …</nowiki></code>'''<br />
</div><br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use <code><nowiki>{{Number of pages}}</nowiki></code> that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article <big>'''''[[Categorization]]'''''</big>. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
<div style="text-align:center;">'''—• Six wikis, six category systems, all images in common •—'''</div><br />
<br />
=='''<big>Template</big>'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
<br />
===Naming your Template===<br />
Some rules for naming templates.<br />
<br />
===All templates===<br />
<big>'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.</big><br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''<big>Portal</big>'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''<code><nowiki>{{Portal bottom}}</nowiki></code>'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''<code><nowiki>{{Portal bottom}}</nowiki></code>''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''<code><nowiki>{{:DOCNAME}}</nowiki></code>''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class="wikitable centre"<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || <nowiki>{{:Featured article/...}}</nowiki> || <nowiki>{{:Lumière sur/...}}</nowiki><br />
|-<br />
| Every day of the week || <nowiki>{{:Featured article/GBA/Week/{{CURRENTDOW}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}</nowiki><br />
|-<br />
| Every day of the month || <nowiki>{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}</nowiki><br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''<pre><nowiki>{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|xxx}}<br />
[[Category:yyyy]]</noinclude></nowiki></pre>'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''<code><nowiki><noinclude></nowiki></code>''' and '''<code><nowiki></noinclude></noinclude></nowiki></code>''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''<code><nowiki><onlyinclude></nowiki></code>''' and '''<code><nowiki></onlyinclude></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''<code><nowiki><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''<code><nowiki>{{read more|<<the original article>}}</nowiki></code>''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''<big>Home page</big>'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
<br />
== Other advanced stuffs ==<br />
API, tips on Special commands...<br />
=== namespaces ===<br />
Code used: <nowiki>{{Special:AllPages|namespace=1}}</nowiki><br />
<br />
Usually, the talk has ns+1. To be bief, no talk here (see more detailled pages) BUt un-usual.<br />
==== FR ns ====<br />
see [[:fr:Guide Technique du wiki/FR ns liste]] (commands are KO in here)<br />
<br />
Namespace 1 - ARK talk <br />
<br />
Namespace 2 - Utilisateur et Utilisatrices - User<br />
<br />
Namespace 4 - '''EncyclopAtys'''<br />
<br />
Namespace 6 - File - Fichier <br />
<br />
Namespace 8 - MediaWiki <br />
<br />
<br />
Namespace 10 - Modèle - Template <br />
<br />
Namespace 12 - Aide - Help<br />
<br />
<br />
Namespace 14 - Catégorie - Category <br />
<br />
Namespace 100 - Guilde<br />
<br />
Namespace 106 - '''Portail - Portal'''<br />
<br />
==== EN ns ====<br />
see [[Wiki Technical Guide/EN ns list]]<br />
<br />
same as FR but:<br />
*Namespace '''4 - Ryzom Wiki''' and 5 Namespace 5 - Ryzom Wiki talk<br />
*Namespace '''104 - Event'''<br />
<br />
==== DE ns ====<br />
[[:de:Technischer Wiki-Leitfaden/DE ns list]]<br />
<br />
Looks like the EN, but no Event namespace, less pages and talk<br />
<br />
==== Atys Common ns ====<br />
<br />
<br />
=== Other links ===<br />
*[[Wiki Technical Guide/Special Pages]]<br />
* [[Wiki Technical Guide/API]]<br />
<br />
Other usefull links<br />
* https://regex101.com/<br />
* https://www.mediawiki.org/wiki/Manual%3APywikibot and [[User:Amosys/Pywiki]] (for tests)<br />
<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=30508Wiki Technical Guide2019-06-30T11:56:32Z<p>Amosys: /* EN ns */</p>
<hr />
<div><noinclude>{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=4<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}</noinclude><br />
'''''A short technical guide for experienced contributors and documentation managers.''''' See [[Writing Guide]] for basic wiki knowledge.<br />
<br />
=='''<big>Working as a team</big>'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''<code><nowiki>[[Talk:{{FULLPAGENAME}}]]</nowiki></code>'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''<code><nowiki>===Title of the topic==</nowiki></code>'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''<code><nowiki>~~~~</nowiki></code>'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more <code>:</code> than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''<code><nowiki>==Title of the topic {{OK}}==</nowiki></code>'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''<code><nowiki>{{KO}}</nowiki></code>'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''<big>Translations</big>'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''<big>Edition</big>'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''<code><nowiki><!--</nowiki></code>''' and to follow it with '''<code><nowiki>--></nowiki></code>'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''<code><nowiki><noinclude><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></noinclude></nowiki></code>'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''<code><nowiki>{{WIP|~~~~}}</nowiki></code>''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''<code><nowiki>{{WIP}}</nowiki></code>'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''<code><nowiki>[[Utilisateur:Zorroargh/Brouillons/...]]</nowiki></code>'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''<big>Validation of content</big>'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
<big>A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.</big><br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''<code><nowiki>{{Official Lore}}</nowiki></code>''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''<code><nowiki>{{Lore Validation Request}}</nowiki></code>''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''<big>Categories</big>'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
<div style="text-align:center;"><br />
{{3DText|3D=outset|group=ranger|text=<span style="font-size:large;font-variant: small-caps;font-weight: bold;">'''''Portal …'''''</span>}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''<code><nowiki>There are for now {{Number of pages}} pages on …</nowiki></code>'''<br />
</div><br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use <code><nowiki>{{Number of pages}}</nowiki></code> that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article <big>'''''[[Categorization]]'''''</big>. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
<div style="text-align:center;">'''—• Six wikis, six category systems, all images in common •—'''</div><br />
<br />
=='''<big>Template</big>'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
<br />
===Naming your Template===<br />
Some rules for naming templates.<br />
<br />
===All templates===<br />
<big>'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.</big><br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''<big>Portal</big>'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''<code><nowiki>{{Portal bottom}}</nowiki></code>'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''<code><nowiki>{{Portal bottom}}</nowiki></code>''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''<code><nowiki>{{:DOCNAME}}</nowiki></code>''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class="wikitable centre"<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || <nowiki>{{:Featured article/...}}</nowiki> || <nowiki>{{:Lumière sur/...}}</nowiki><br />
|-<br />
| Every day of the week || <nowiki>{{:Featured article/GBA/Week/{{CURRENTDOW}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}</nowiki><br />
|-<br />
| Every day of the month || <nowiki>{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}</nowiki><br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''<pre><nowiki>{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|xxx}}<br />
[[Category:yyyy]]</noinclude></nowiki></pre>'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''<code><nowiki><noinclude></nowiki></code>''' and '''<code><nowiki></noinclude></noinclude></nowiki></code>''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''<code><nowiki><onlyinclude></nowiki></code>''' and '''<code><nowiki></onlyinclude></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''<code><nowiki><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''<code><nowiki>{{read more|<<the original article>}}</nowiki></code>''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''<big>Home page</big>'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
<br />
== Other advanced stuffs ==<br />
API, tips on Special commands...<br />
=== namespaces ===<br />
Code used: <nowiki>{{Special:AllPages|namespace=1}}</nowiki><br />
<br />
Usually, the talk has ns+1. To be bief, no talk here (see more detailled pages) BUt un-usual.<br />
==== FR ns ====<br />
see [[:fr:Guide Technique du wiki/FR ns liste]] (commands are KO in here)<br />
<br />
Namespace 1 - ARK talk <br />
<br />
Namespace 2 - Utilisateur et Utilisatrices - User<br />
<br />
Namespace 4 - '''EncyclopAtys'''<br />
<br />
Namespace 6 - File - Fichier <br />
<br />
Namespace 8 - MediaWiki <br />
<br />
<br />
Namespace 10 - Modèle - Template <br />
<br />
Namespace 12 - Aide - Help<br />
<br />
<br />
Namespace 14 - Catégorie - Category <br />
<br />
Namespace 100 - Guilde<br />
<br />
Namespace 106 - '''Portail - Portal'''<br />
<br />
==== EN ns ====<br />
see [[Wiki Technical Guide/EN ns list]]<br />
<br />
same as FR but:<br />
*Namespace '''4 - Ryzom Wiki''' and 5 Namespace 5 - Ryzom Wiki talk<br />
*Namespace '''104 - Event'''<br />
<br />
==== DE ns ====<br />
[[:de:Technischer Wiki-Leitfaden/DE ns list]]<br />
Looks like the EN, but no Event namespace<br />
<br />
==== Atys Common ns ====<br />
<br />
<br />
=== Other links ===<br />
*[[Wiki Technical Guide/Special Pages]]<br />
* [[Wiki Technical Guide/API]]<br />
<br />
Other usefull links<br />
* https://regex101.com/<br />
* https://www.mediawiki.org/wiki/Manual%3APywikibot and [[User:Amosys/Pywiki]] (for tests)<br />
<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=30507Wiki Technical Guide2019-06-30T11:55:45Z<p>Amosys: /* DE ns */</p>
<hr />
<div><noinclude>{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=4<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}</noinclude><br />
'''''A short technical guide for experienced contributors and documentation managers.''''' See [[Writing Guide]] for basic wiki knowledge.<br />
<br />
=='''<big>Working as a team</big>'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''<code><nowiki>[[Talk:{{FULLPAGENAME}}]]</nowiki></code>'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''<code><nowiki>===Title of the topic==</nowiki></code>'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''<code><nowiki>~~~~</nowiki></code>'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more <code>:</code> than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''<code><nowiki>==Title of the topic {{OK}}==</nowiki></code>'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''<code><nowiki>{{KO}}</nowiki></code>'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''<big>Translations</big>'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''<big>Edition</big>'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''<code><nowiki><!--</nowiki></code>''' and to follow it with '''<code><nowiki>--></nowiki></code>'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''<code><nowiki><noinclude><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></noinclude></nowiki></code>'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''<code><nowiki>{{WIP|~~~~}}</nowiki></code>''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''<code><nowiki>{{WIP}}</nowiki></code>'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''<code><nowiki>[[Utilisateur:Zorroargh/Brouillons/...]]</nowiki></code>'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''<big>Validation of content</big>'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
<big>A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.</big><br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''<code><nowiki>{{Official Lore}}</nowiki></code>''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''<code><nowiki>{{Lore Validation Request}}</nowiki></code>''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''<big>Categories</big>'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
<div style="text-align:center;"><br />
{{3DText|3D=outset|group=ranger|text=<span style="font-size:large;font-variant: small-caps;font-weight: bold;">'''''Portal …'''''</span>}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''<code><nowiki>There are for now {{Number of pages}} pages on …</nowiki></code>'''<br />
</div><br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use <code><nowiki>{{Number of pages}}</nowiki></code> that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article <big>'''''[[Categorization]]'''''</big>. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
<div style="text-align:center;">'''—• Six wikis, six category systems, all images in common •—'''</div><br />
<br />
=='''<big>Template</big>'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
<br />
===Naming your Template===<br />
Some rules for naming templates.<br />
<br />
===All templates===<br />
<big>'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.</big><br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''<big>Portal</big>'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''<code><nowiki>{{Portal bottom}}</nowiki></code>'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''<code><nowiki>{{Portal bottom}}</nowiki></code>''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''<code><nowiki>{{:DOCNAME}}</nowiki></code>''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class="wikitable centre"<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || <nowiki>{{:Featured article/...}}</nowiki> || <nowiki>{{:Lumière sur/...}}</nowiki><br />
|-<br />
| Every day of the week || <nowiki>{{:Featured article/GBA/Week/{{CURRENTDOW}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}</nowiki><br />
|-<br />
| Every day of the month || <nowiki>{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}</nowiki><br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''<pre><nowiki>{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|xxx}}<br />
[[Category:yyyy]]</noinclude></nowiki></pre>'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''<code><nowiki><noinclude></nowiki></code>''' and '''<code><nowiki></noinclude></noinclude></nowiki></code>''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''<code><nowiki><onlyinclude></nowiki></code>''' and '''<code><nowiki></onlyinclude></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''<code><nowiki><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''<code><nowiki>{{read more|<<the original article>}}</nowiki></code>''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''<big>Home page</big>'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
<br />
== Other advanced stuffs ==<br />
API, tips on Special commands...<br />
=== namespaces ===<br />
Code used: <nowiki>{{Special:AllPages|namespace=1}}</nowiki><br />
<br />
Usually, the talk has ns+1. To be bief, no talk here (see more detailled pages) BUt un-usual.<br />
==== FR ns ====<br />
see [[:fr:Guide Technique du wiki/FR ns liste]] (commands are KO in here)<br />
<br />
Namespace 1 - ARK talk <br />
<br />
Namespace 2 - Utilisateur et Utilisatrices - User<br />
<br />
Namespace 4 - '''EncyclopAtys'''<br />
<br />
Namespace 6 - File - Fichier <br />
<br />
Namespace 8 - MediaWiki <br />
<br />
<br />
Namespace 10 - Modèle - Template <br />
<br />
Namespace 12 - Aide - Help<br />
<br />
<br />
Namespace 14 - Catégorie - Category <br />
<br />
Namespace 100 - Guilde<br />
<br />
Namespace 106 - '''Portail - Portal'''<br />
<br />
==== EN ns ====<br />
see [[Wiki Technical Guide/EN ns list]]<br />
<br />
same as FR but:<br />
4 Namespace 4 - Ryzom Wiki and 5 Namespace 5 - Ryzom Wiki talk<br />
<br />
Namespace 104 - Event<br />
<br />
==== DE ns ====<br />
[[:de:Technischer Wiki-Leitfaden/DE ns list]]<br />
Looks like the EN, but no Event namespace<br />
<br />
==== Atys Common ns ====<br />
<br />
<br />
=== Other links ===<br />
*[[Wiki Technical Guide/Special Pages]]<br />
* [[Wiki Technical Guide/API]]<br />
<br />
Other usefull links<br />
* https://regex101.com/<br />
* https://www.mediawiki.org/wiki/Manual%3APywikibot and [[User:Amosys/Pywiki]] (for tests)<br />
<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide/EN_ns_list&diff=30506Wiki Technical Guide/EN ns list2019-06-30T11:52:17Z<p>Amosys: </p>
<hr />
<div>{{Trad|DE=Technischer Wiki-Leitfaden/DE ns list|EN=Wiki Technical Guide/EN ns list|FR=Guide Technique du wiki/FR ns liste|ES=|RU=}}<br />
<br />
== Namespace 1 - ARK talk==<br />
same as FR<br />
{{Special:AllPages|namespace=1}}<br />
== Namespace 2 - User==<br />
{{Special:AllPages|namespace=2}}<br />
== Namespace 3 - User talk ==<br />
{{Special:AllPages|namespace=3}}<br />
== Namespace 4 - Ryzom Wiki ==<br />
{{Special:AllPages|namespace=4}}<br />
== Namespace 5 - Ryzom Wiki talk==<br />
{{Special:AllPages|namespace=5}}<br />
== Namespace 6 - File ==<br />
{{Special:AllPages|namespace=6}}<br />
== Namespace 7 - empty ==<br />
{{Special:AllPages|namespace=7}}<br />
== Namespace 8 - Media wiki ==<br />
{{Special:AllPages|namespace=8}}<br />
== Namespace 9 ==<br />
{{Special:AllPages|namespace=9}}<br />
== Namespace 10 - Template ==<br />
{{Special:AllPages|namespace=10}}<br />
== Namespace 11==<br />
{{Special:AllPages|namespace=11}}<br />
== Namespace 12 - Help ==<br />
{{Special:AllPages|namespace=12}}<br />
== Namespace 13==<br />
{{Special:AllPages|namespace=13}}<br />
== Namespace 14 - Category ==<br />
{{Special:AllPages|namespace=14}}<br />
== Namespace 15==<br />
{{Special:AllPages|namespace=15}}<br />
== Namespace 100 - Guild ==<br />
{{Special:AllPages|namespace=100}}<br />
== Namespace 101==<br />
{{Special:AllPages|namespace=101}}<br />
== Namespace 102==<br />
{{Special:AllPages|namespace=102}}<br />
== Namespace 103==<br />
{{Special:AllPages|namespace=103}}<br />
== Namespace 104 - Event ==<br />
{{Special:AllPages|namespace=104}}<br />
== Namespace 105==<br />
{{Special:AllPages|namespace=105}}<br />
== Namespace 106==<br />
{{Special:AllPages|namespace=106}}<br />
== Namespace 107==<br />
{{Special:AllPages|namespace=107}}<br />
<br />
<br />
<br />
[[category:Wikipatys]] [[category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=30505Wiki Technical Guide2019-06-30T11:45:13Z<p>Amosys: /* FR ns */</p>
<hr />
<div><noinclude>{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=4<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}</noinclude><br />
'''''A short technical guide for experienced contributors and documentation managers.''''' See [[Writing Guide]] for basic wiki knowledge.<br />
<br />
=='''<big>Working as a team</big>'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''<code><nowiki>[[Talk:{{FULLPAGENAME}}]]</nowiki></code>'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''<code><nowiki>===Title of the topic==</nowiki></code>'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''<code><nowiki>~~~~</nowiki></code>'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more <code>:</code> than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''<code><nowiki>==Title of the topic {{OK}}==</nowiki></code>'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''<code><nowiki>{{KO}}</nowiki></code>'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''<big>Translations</big>'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''<big>Edition</big>'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''<code><nowiki><!--</nowiki></code>''' and to follow it with '''<code><nowiki>--></nowiki></code>'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''<code><nowiki><noinclude><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></noinclude></nowiki></code>'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''<code><nowiki>{{WIP|~~~~}}</nowiki></code>''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''<code><nowiki>{{WIP}}</nowiki></code>'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''<code><nowiki>[[Utilisateur:Zorroargh/Brouillons/...]]</nowiki></code>'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''<big>Validation of content</big>'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
<big>A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.</big><br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''<code><nowiki>{{Official Lore}}</nowiki></code>''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''<code><nowiki>{{Lore Validation Request}}</nowiki></code>''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''<big>Categories</big>'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
<div style="text-align:center;"><br />
{{3DText|3D=outset|group=ranger|text=<span style="font-size:large;font-variant: small-caps;font-weight: bold;">'''''Portal …'''''</span>}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''<code><nowiki>There are for now {{Number of pages}} pages on …</nowiki></code>'''<br />
</div><br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use <code><nowiki>{{Number of pages}}</nowiki></code> that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article <big>'''''[[Categorization]]'''''</big>. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
<div style="text-align:center;">'''—• Six wikis, six category systems, all images in common •—'''</div><br />
<br />
=='''<big>Template</big>'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
<br />
===Naming your Template===<br />
Some rules for naming templates.<br />
<br />
===All templates===<br />
<big>'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.</big><br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''<big>Portal</big>'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''<code><nowiki>{{Portal bottom}}</nowiki></code>'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''<code><nowiki>{{Portal bottom}}</nowiki></code>''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''<code><nowiki>{{:DOCNAME}}</nowiki></code>''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class="wikitable centre"<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || <nowiki>{{:Featured article/...}}</nowiki> || <nowiki>{{:Lumière sur/...}}</nowiki><br />
|-<br />
| Every day of the week || <nowiki>{{:Featured article/GBA/Week/{{CURRENTDOW}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}</nowiki><br />
|-<br />
| Every day of the month || <nowiki>{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}</nowiki><br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''<pre><nowiki>{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|xxx}}<br />
[[Category:yyyy]]</noinclude></nowiki></pre>'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''<code><nowiki><noinclude></nowiki></code>''' and '''<code><nowiki></noinclude></noinclude></nowiki></code>''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''<code><nowiki><onlyinclude></nowiki></code>''' and '''<code><nowiki></onlyinclude></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''<code><nowiki><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''<code><nowiki>{{read more|<<the original article>}}</nowiki></code>''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''<big>Home page</big>'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
<br />
== Other advanced stuffs ==<br />
API, tips on Special commands...<br />
=== namespaces ===<br />
Code used: <nowiki>{{Special:AllPages|namespace=1}}</nowiki><br />
<br />
Usually, the talk has ns+1. To be bief, no talk here (see more detailled pages) BUt un-usual.<br />
==== FR ns ====<br />
see [[:fr:Guide Technique du wiki/FR ns liste]] (commands are KO in here)<br />
<br />
Namespace 1 - ARK talk <br />
<br />
Namespace 2 - Utilisateur et Utilisatrices - User<br />
<br />
Namespace 4 - '''EncyclopAtys'''<br />
<br />
Namespace 6 - File - Fichier <br />
<br />
Namespace 8 - MediaWiki <br />
<br />
<br />
Namespace 10 - Modèle - Template <br />
<br />
Namespace 12 - Aide - Help<br />
<br />
<br />
Namespace 14 - Catégorie - Category <br />
<br />
Namespace 100 - Guilde<br />
<br />
Namespace 106 - '''Portail - Portal'''<br />
<br />
==== EN ns ====<br />
see [[Wiki Technical Guide/EN ns list]]<br />
<br />
same as FR but:<br />
4 Namespace 4 - Ryzom Wiki and 5 Namespace 5 - Ryzom Wiki talk<br />
<br />
Namespace 104 - Event<br />
<br />
==== DE ns ====<br />
[[de:Technischer Wiki-Leitfaden/DE ns list]]<br />
<br />
<br />
==== Atys Common ns ====<br />
<br />
<br />
=== Other links ===<br />
*[[Wiki Technical Guide/Special Pages]]<br />
* [[Wiki Technical Guide/API]]<br />
<br />
Other usefull links<br />
* https://regex101.com/<br />
* https://www.mediawiki.org/wiki/Manual%3APywikibot and [[User:Amosys/Pywiki]] (for tests)<br />
<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide&diff=30504Wiki Technical Guide2019-06-30T11:43:35Z<p>Amosys: /* Other advanced commands */</p>
<hr />
<div><noinclude>{{Trad<br />
|DE=Technischer Wiki-Leitfaden<br />
|EN=Wiki Technical Guide<br />
|ES=Guía Técnica de la Wiki<br />
|FR=Guide Technique du wiki<br />
|RU=Техническое руководство по Вики<br />
}}<br />
{{TIP<br />
|DE=2<br />
|EN=4<br />
|ES=1<br />
|FR=0<br />
|RU=5<br />
}}</noinclude><br />
'''''A short technical guide for experienced contributors and documentation managers.''''' See [[Writing Guide]] for basic wiki knowledge.<br />
<br />
=='''<big>Working as a team</big>'''==<br />
Never forget that any document (except protected pages, accessible only to administrators) can be edited at any time by anyone. See below ([[{{FULLPAGENAME}}#Edition|Edition]] puis [[{{FULLPAGENAME}}#Content Validation|Content Validation]]) for good practices to be followed.<br />
<br />
===Talk pages===<br />
It is often useful, convenient or necessary to leave a message to someone else. For that purpose a “Talk” page is associated with each document when it is created, for example here: [[Talk:{{FULLPAGENAME}}]] '''<code><nowiki>[[Talk:{{FULLPAGENAME}}]]</nowiki></code>'''.<br />
<br />
In any case, you must try to maintain something readable, so each topic will start with a title '''<code><nowiki>===Title of the topic==</nowiki></code>'''. It is better to have fifty small separate subjects, each with a title, than a single package of fifty subjects. This facilitates discriminated responses in their consideration, implementation, etc.<br />
<br />
At the end of the subject, always sign with '''<code><nowiki>~~~~</nowiki></code>'''. This immediately lets anyone know who posted the message and when.<br />
<br />
Usually, responses are made by indenting as in emails. This is done by opening the line with one more <code>:</code> than the previous part. Obviously each answer, each rebound will be signed. This is very useful for someone who will ask the same questions later on and who will thus see this discussion as part of a “Knowledge Base”.<br />
<br />
Last, it may be useful to attach to the title a '''{{OK}}''' to indicate that the subject is closed '''<code><nowiki>==Title of the topic {{OK}}==</nowiki></code>'''. If the subject has to be reopened, the '''{{OK}}''' can be replaced by a '''{{KO}}''' '''<code><nowiki>{{KO}}</nowiki></code>'''.<br />
<br />
Unfortunately, those concerned by the question are not necessarily informed (the number of articles monitored - and therefore likely to have their changes notified - is capped so as not to blow up the database). Thus, also think about preventing the person or persons who may be concerned by the discussion by indicating the link to the discussion. Again, title and signature, even if very short, are welcome.<br />
<br />
=== Sponsorship ===<br />
At first glance we will notice that if the Wiki is easy at writing, it is heavy to manage with all its rules of conviviality and efficiency, its traditions built on the experience of its predecessors, etc. This because the wiki also has its “Lore” (oral tradition).<br />
<br />
Do you really want to get involved in the wiki? So don't hesitate to be sponsored, without embarrassment, shyness or shame... We have all made our debut, and perhaps, hopefully, it will be up to you to sponsor later on. You don't know anyone? Try to contact “alumni” on https://chat.ryzom.com/channel/pj-ryzom_wiki or contact them from [[Special:ActiveUsers]].<br />
<br />
=='''<big>Translations</big>'''==<br />
There are four rules that coexist:<br />
;• Forge (development part), Game behaviour chart, Graphic chart, Fundamental categories:<br />
*everything must be translated into English to be accessible to as many people as possible, whose majority more or less understand written English;<br />
;• In-Game Behavior Chart, Graphic Chart, Wiki Management Templates, Fundamental Categories:<br />
*everything must be translated into all languages;<br />
;• Lore, Chronicles, Public events:<br />
*everything must be translated into at least Ryzom's three “mother tongues”: DE, EN and FR;<br />
;• the rest and especially the roleplay parts:<br />
*there are no rules, only players' and translators' concerns prevail.<br />
<br />
=='''<big>Edition</big>'''==<br />
[[File:EN wiki history comparing.png|thumb]] [[File:EN wiki history see.png|thumb]] With the exception of archived documents and documents with the official status of “final document” (Lore, Chronicle), everything can be improved and this is one of the riches of wikis.<br />
<br />
Nevertheless, certain rules of constructive conviviality must be respected.<br />
<br />
First of all, it is necessary to assess whether or not the changes are significant. There are no rules and it's more of a feeling, but if the change is drastic, it's wise to start by looking at the page's history (button next to “Edit”). If the content (not the form, look, spelling…) has not changed for some time, we can assume that its author left it for this and that the document may have aged, that it may need updating. An example is shown opposite.<br />
<br />
An update can be considered drastic when it deletes paragraphs or even lines that are fundamental to the development of the topic. In this case it becomes appropriate to leave a message in the “User Discussion:xyz” page. While waiting for his answer (one week?), it is wise to keep in the modified page the original text passed as a comment. The easiest way to pass a text as a comment is to preface it with '''<code><nowiki><!--</nowiki></code>''' and to follow it with '''<code><nowiki>--></nowiki></code>'''. But there are sometimes issues, especially if there are already other comments. In this case, the hammer and chisel can be used by framing the text with '''<code><nowiki><noinclude><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></noinclude></nowiki></code>'''. Why such a complication? Because it is always necessary to respect the writings of an author and his intellectual authorship, even in free software world. Otherwise, we run the risk of an:<br />
<br />
===Edit war===<br />
Excerpt from Wikipedia '''[https://en.wikipedia.org/wiki/Wikipedia:Edit_warring Edit warring]''':<br />
<br />
“''An '''edit war''' occurs when editors who disagree about the content of a page repeatedly override each other's contributions. Editors engaged in a dispute should reach consensus or pursue dispute resolution rather than edit warring. Edit warring is unconstructive and creates animosity between editors, making consensus harder to reach. Users who engage in edit wars risk being blocked or even banned. An editor who repeatedly restores their preferred version is edit warring, regardless of whether those edits are justifiable: “But my edits were right, so it wasn't edit warring” is no defense.''”<br />
<br />
This should not be confused with the edit conflict . Excerpt translated from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''':<br />
<br />
“''In Wikipedia, a version conflict or '''edit conflict''' occurs when two contributors work on the same page at the same time: the second one who records, having worked with an obsolete version of the page, has his modification rejected. Since version 1.3 of MediaWiki, this only happens if the changes cannot be merged automatically.''“<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===Working in tranquillity===<br />
Of course, incidents on the course and clumsiness will never be avoided at 100%, so the wisest thing to do is to follow the following recommendations (from Wikipedia '''[https://fr.wikipedia.org/wiki/Aide:Conflit_de_versions Aide:Conflit de versions]''') :<br />
<br />
“''To avoid version conflicts, the easiest way is to avoid long modifications.''<br />
<br />
''However, this is not always possible. This is why it is recommended, when modifying a page in depth, to first add the banner'' '''<code><nowiki>{{WIP|~~~~}}</nowiki></code>''' ''which is displayed as follows'':<br />
<br />
<br />
{{WIP|-- [[User:Zorroargh|Zo'ro-Argh]]&nbsp;<sup><small>[[User talk:Zorroargh|Woren&nbsp;Siloy]]</small></sup> 28 mai 2019 à 14:19 (CEST)}}<br />
<br />
<br />
''Once the page is published with this banner, you can modify it at any time. Limit the number of changes by using the preview to make adjustments (this saves time and avoids cluttering the page with recent changes).''<br />
<br />
''When you are finished, don't forget to remove the template'' '''<code><nowiki>{{WIP}}</nowiki></code>'''.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Edit_conflict Help:Edit conflict]''' for further information)<br />
<br />
===The draft===<br />
Another way to work in peace is to work in your own user space. This space is '''<code><nowiki>[[Utilisateur:Zorroargh/Brouillons/...]]</nowiki></code>'''.<br />
<br />
The documents you prepare there are not available to search engines (except explicitly). Even Google shouldn't go there!<br />
<br />
=='''<big>Validation of content</big>'''==<br />
Usually, in Ryzom's wikis all pages are free to be processed as long as there is no vandalism. Nevertheless, players may need reliable documents. This essentially concerns:<br />
*The '''[https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187218=en#1 Ryzom code of conduct]''' throughout the game, including this wiki.<br />
*The '''Lore''' which sets the fundamental characteristics of the game (homins don't speak Klingon, Karavan doesn't fly on fire dragons and Kamis don't emerge from an oil lamp). These characteristics are detailed in the portal of the '''[[Portal:Lore|Lore]]'''. Here, they will be briefly described to indicate their existence.<br />
Other documents may be considered sensitive for maintenance, such as the widely used [[Categorization#Le_Wikipatys|templates]] that can change the appearance, or even readability, of the documents.<br />
<br />
Finally, contributors, whether developers, players (RP or not), animators or others, may find it useful to request validation of their work.<br />
<br />
<big>A document validated by the Lorists, the official communications officers or the administrators is protected against any modifications not expressly authorized.</big><br />
<br />
=== The Lore ===<br />
Summary of the specific treatment of documents related to the Lore<br />
==== Official copy ====<br />
Text written by the Lorists and transcribed or translated by ''encyclopatysts''.<br />
At the very top of the page, the Lore logo is affixed '''<code><nowiki>{{Official Lore}}</nowiki></code>''' wihich will display the picture [[File:Rubber-Stamp-Lore_choix_Vert.png|64px]].<br />
====Creation of a non-lorist user====<br />
Pour demander une validation de l'équipe Lore, apposer tout en haut de la page la bannière '''<code><nowiki>{{Lore Validation Request}}</nowiki></code>''' which is displayed as follows:<br />
<br />
{{Lore Validation Request}}<br />
<br />
==== Validation ====<br />
A Lorist affixes, if that has not already being done, the Lore logo, and erases any banners that may have been used to request validation. Then the Lorist (who can delegate this task to an administrator) protects the page. The Lore logo then becomes: [[image:Rubber-Stamp-Lore_choix_H.png|64px]].<br />
<br />
=='''<big>Categories</big>'''==<br />
All data, articles, images, templates, portals, etc., must be categorized.<br />
===On the use of categories===<br />
Categories are very useful for cataloging documents and easing their search. It must be understood that a category resembles a set in the mathematical sense of the term, in other words:<br />
*an article can belong to several sets;<br />
*a set of article can be fully included in another;<br />
*It is unnecessary to declare that an article belongs to two sets if one of them is completely included in the other.<br />
Example: a '''''red sock''''' can belong to the categories: '''''socks''''', '''''red objects''''', '''''red clothes''''', '''''clothes'''''.<br />
Normally, declaring that this sock belongs to the '''''red clothes''''' is sufficient. But one could also say that it belongs to the '''''socks''''' and to the '''''red objects''''' without referring to '''''red clothes'''''. In both cases, it is useless to declare that it belongs to the '''''clothes'''''.<br />
<br />
The choice of categories can sometimes be linked to the tools that allow you to search in a category and that are often displayed in portals. For example: <br />
<div style="text-align:center;"><br />
{{3DText|3D=outset|group=ranger|text=<span style="font-size:large;font-variant: small-caps;font-weight: bold;">'''''Portal …'''''</span>}}<br />
<br />
{{3DText|3D=outset|group=ranger|text='''There are for now 19 pages …'''}}<br />
<br />
Ce qui est obtenu par '''<code><nowiki>There are for now {{Number of pages}} pages on …</nowiki></code>'''<br />
</div><br />
<br />
Of course, it appears from the previous example that there may be exceptions mainly related to the ergonomics of the research. Indeed, the automatic search (random search for an item to include, for example - see [[#Spotlight on|Spotlight on]] below) in category trees requires a lot of time and energy. Therefore, it is preferable to use <code><nowiki>{{Number of pages}}</nowiki></code> that does not go down in sub-categories.<br />
<br />
==== The main categories of this wiki ====<br />
Wikis, linked to the Ryzom universe, are supposed to share data common to the basic languages of the game.<br />
These common data are grouped in four trees detailed in the article <big>'''''[[Categorization]]'''''</big>. Only the “big branches” are detailed to leave the freedom to organize the data to each linguistic group. But these trunks and their “big branches” are essential, especially for translators who want to easily navigate between groups of articles.<br />
<br />
<br />
[[File:Mindmap 6 wikis and image categories 2019-06-14.png|center|800px|alt=6 wikis, 6 category systems, all images in common|Six wikis, six category systems, all images in common]]<br />
<div style="text-align:center;">'''—• Six wikis, six category systems, all images in common •—'''</div><br />
<br />
=='''<big>Template</big>'''==<br />
Translated excerpt from Wikipédia '''[https://fr.wikipedia.org/wiki/Aide:Mod%C3%A8le Aide:Modèle]'''<br />
<br />
“''A template is used to reproduce the same message, or the same layout, on several pages, sometimes according to parameters.<br />
<br />
''It is a pre-written element, more or less complex, intended to be embedded in a page in order to instantly obtain the desired visual result (formatting, display of specific elements, etc.). The banners at the top of the articles, the infoboxes, the centuries display… are templates.”<br />
<br />
(see Wikipedia '''[https://en.wikipedia.org/wiki/Help:Template Help:Template]''' for further information)<br />
<br />
===Visual aspect and graphic charter===<br />
The visual aspect must recall the identity of the game. For example: “infoboxes” remind us of “memory ambers” (RP) or interfaces of the Karavan (OOC). Icons in general refer more or less clearly to the game world.<br />
<br />
A graphic charter has two functions (at least):<br />
*an identification function, recalling the spirit of the site (for example by using the emblematic colours of nations, factions);<br />
*an ergonomic function, by avoiding the “element of surprise”, i.e. avoiding differences of behaviour between pages or between translations.<br />
<br />
For these two reasons, it should be adhered to as much as possible.<br />
===Banners, seals and indicators in header===<br />
Header or paragraph templates are used to alert the reader on the way the page they are consulting should be interpreted (obsolescence, in the process of being written, etc.) and to highlight important announcements regarding the article.<br />
===Banners, navigation, time stamps===<br />
Footer templates are used to provide the reader with additional information that may be of interest after reading the page.<br />
===Page body===<br />
Page body templates are used to complete or highlight information related to the current page. Highlightings can be diverse, such as large inserts or various typographic layouts.<br />
<br />
===Naming your Template===<br />
Some rules for naming templates.<br />
<br />
===All templates===<br />
<big>'''Warning''' : not exactly the same for all languages, but let us try to harmonize them as much as possible.</big><br />
<br />
All templates are placed in the [[:Category:Templates]] whose tree view is explained in the document [[Categorization#The_Wikipatys]]<br />
=='''<big>Portal</big>'''==<br />
Portals in our wiki serve as home pages for the various major areas of interest in the game. They are listed in the panel '''<code><nowiki>{{Portal bottom}}</nowiki></code>'''<br />
{{Portal bottom}}<br />
<br />
All portals have a similar structure, but their appearance varies according to the complexity of the data they present. In general, a portal contains, from top to bottom:<br />
*several tabs of sub-themes, the general home page positioning the reading on the first of them; in some cases, there may be a second row of tabs;<br />
*the number of articles concerned and categorized (see [[#Associated categories|Associated categories]]) ;<br />
*a summary;<br />
*information (on the left the [[#Doc of the day|Doc of the day]], on the right a [[#Bulletin board|Bulletin board]]);<br />
*the panel summarizing the main portals of the Ryzom Wiki ('''<code><nowiki>{{Portal bottom}}</nowiki></code>''').<br />
<br />
Portals have not been built in a day and therefore their design has been refined over time. In general, we try to include documents in them using the template '''<code><nowiki>{{:DOCNAME}}</nowiki></code>''' where DOCNAME=Name of the document to include.<br />
===Doc of the day===<br />
It is sometimes pleasant to have documentation that gives an overview of the themes presented under the portal.<br />
This can be done as follows:<br />
{| class="wikitable centre"<br />
! A different document included || ENGLISH || FRENCH <br />
|-<br />
| When necessary || <nowiki>{{:Featured article/...}}</nowiki> || <nowiki>{{:Lumière sur/...}}</nowiki><br />
|-<br />
| Every day of the week || <nowiki>{{:Featured article/GBA/Week/{{CURRENTDOW}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Jour/{{CURRENTDOW}}}}</nowiki><br />
|-<br />
| Every day of the month || <nowiki>{{:Featured article/GBA/Month/{{CURRENTDAY2}}}}</nowiki> || <nowiki>{{:Lumière sur/.../Mois/{{CURRENTDAY2}}}}</nowiki><br />
|}<br />
<br />
===Bulletin board===<br />
Bulletin boards contain information about both readers and contributors. This can range from simple information to emergencies, “To do” lists and “Tips and Tricks”.<br />
<br />
===Associated categories===<br />
====All relevant pages====<br />
To associate an article to a portal, just add at the bottom of the text of the said article a block of instructions of the following type:<br />
'''<pre><nowiki>{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|xxx}}<br />
[[Category:yyyy]]</noinclude></nowiki></pre>'''<br />
where:<br />
*the “clear” ensures that the navigation bar to the portal is well above the last image;<br />
*the “last version link” allows you to time stamp the page and adds a discreet tab to find the origin of an inclusion;<br />
*the “noinclude” can be put in so as not to pollute the inclusion.<br />
====On the front page====<br />
Adding the navigation banner to the portal also places the article in “hidden” categories, categories that would not be shown to the reader because they are not relevant, but are indicated by a '''[+]''' located after the last displayed category. The random choice technique has been rejected by Mediawiki as too expensive. Currently, it is preferred a restricted choice (day of the week or month). This requires you to create one redirection at a time to the page you want to highlight. Thus, for example, the “Featured article/GBA/Day/3” page (3rd of the month or Wednesday) is redirected to “Primes Raider”.<br />
<br />
What if the article is too long to be included, or if only some of its sections are worthwhile?<br />
<br />
The wisest way is to signal the sections to be displayed or hidden in the future inclusion by marking them up in the source article.<br />
*'''<code><nowiki><noinclude></nowiki></code>''' and '''<code><nowiki></noinclude></noinclude></nowiki></code>''' tags allow to exclude the parts they frame from the future inclusion.<br />
*'''<code><nowiki><onlyinclude></nowiki></code>''' and '''<code><nowiki></onlyinclude></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion.<br />
*'''<code><nowiki><includeonly></nowiki></code>''' and '''<code><nowiki></includeonly></nowiki></code>''' tags allow to include only the parts they frame in the future inclusion, while masking them in the original article (to be handled carefully in a template).<br />
<br />
This latter markup is used, for example, to hide in the original article the “To be continued…” ('''<code><nowiki>{{read more|<<the original article>}}</nowiki></code>''' displayed below) but displays it in the inclusion. {{read more|{{FULLPAGENAME}}}}<br />
<br />
=='''<big>Home page</big>'''==<br />
Home pages are “specific” because they are those that appear by default when you log in to the wiki. These pages are not editable and can contain many HTML (and Java) tricks. This implies that only seasoned contributors can modify them on community consensus or communication imperatives.<br />
<br />
<br />
== Other advanced stuffs ==<br />
API, tips on Special commands...<br />
=== namespaces ===<br />
Code used: <nowiki>{{Special:AllPages|namespace=1}}</nowiki><br />
<br />
Usually, the talk has ns+1. To be bief, no talk here (see more detailled pages) BUt un-usual.<br />
==== FR ns ====<br />
see [[fr:Guide Technique du wiki/FR ns liste]] (commands are KO in here)<br />
<br />
Namespace 1 - ARK talk <br />
<br />
Namespace 2 - Utilisateur et Utilisatrices - User<br />
<br />
Namespace 4 - '''EncyclopAtys'''<br />
<br />
Namespace 6 - File - Fichier <br />
<br />
Namespace 8 - MediaWiki <br />
<br />
<br />
Namespace 10 - Modèle - Template <br />
<br />
Namespace 12 - Aide - Help<br />
<br />
<br />
Namespace 14 - Catégorie - Category <br />
<br />
Namespace 100 - Guilde<br />
<br />
Namespace 106 - '''Portail - Portal'''<br />
<br />
==== EN ns ====<br />
see [[Wiki Technical Guide/EN ns list]]<br />
<br />
same as FR but:<br />
4 Namespace 4 - Ryzom Wiki and 5 Namespace 5 - Ryzom Wiki talk<br />
<br />
Namespace 104 - Event<br />
<br />
==== DE ns ====<br />
[[de:Technischer Wiki-Leitfaden/DE ns list]]<br />
<br />
<br />
==== Atys Common ns ====<br />
<br />
<br />
=== Other links ===<br />
*[[Wiki Technical Guide/Special Pages]]<br />
* [[Wiki Technical Guide/API]]<br />
<br />
Other usefull links<br />
* https://regex101.com/<br />
* https://www.mediawiki.org/wiki/Manual%3APywikibot and [[User:Amosys/Pywiki]] (for tests)<br />
<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide/EN_ns_list&diff=30503Wiki Technical Guide/EN ns list2019-06-30T11:36:01Z<p>Amosys: Created page with "{{Trad|DE=|EN=Wiki Technical Guide/EN ns list|FR=Guide Technique du wiki/FR ns liste|ES=|RU=}} == Namespace 1 - ARK talk== same as FR {{Special:AllPages|namespace=1}} == Nam..."</p>
<hr />
<div>{{Trad|DE=|EN=Wiki Technical Guide/EN ns list|FR=Guide Technique du wiki/FR ns liste|ES=|RU=}}<br />
<br />
<br />
== Namespace 1 - ARK talk==<br />
same as FR<br />
{{Special:AllPages|namespace=1}}<br />
== Namespace 2 - User==<br />
{{Special:AllPages|namespace=2}}<br />
== Namespace 3 - User talk ==<br />
{{Special:AllPages|namespace=3}}<br />
== Namespace 4 - Ryzom Wiki ==<br />
{{Special:AllPages|namespace=4}}<br />
== Namespace 5 - Ryzom Wiki talk==<br />
{{Special:AllPages|namespace=5}}<br />
== Namespace 6 - File ==<br />
{{Special:AllPages|namespace=6}}<br />
== Namespace 7 - empty ==<br />
{{Special:AllPages|namespace=7}}<br />
== Namespace 8 - Media wiki ==<br />
{{Special:AllPages|namespace=8}}<br />
== Namespace 9 ==<br />
{{Special:AllPages|namespace=9}}<br />
== Namespace 10 - Template ==<br />
{{Special:AllPages|namespace=10}}<br />
== Namespace 11==<br />
{{Special:AllPages|namespace=11}}<br />
== Namespace 12 - Help ==<br />
{{Special:AllPages|namespace=12}}<br />
== Namespace 13==<br />
{{Special:AllPages|namespace=13}}<br />
== Namespace 14 - Category ==<br />
{{Special:AllPages|namespace=14}}<br />
== Namespace 15==<br />
{{Special:AllPages|namespace=15}}<br />
== Namespace 100 - Guild ==<br />
{{Special:AllPages|namespace=100}}<br />
== Namespace 101==<br />
{{Special:AllPages|namespace=101}}<br />
== Namespace 102==<br />
{{Special:AllPages|namespace=102}}<br />
== Namespace 103==<br />
{{Special:AllPages|namespace=103}}<br />
== Namespace 104 - Event ==<br />
{{Special:AllPages|namespace=104}}<br />
== Namespace 105==<br />
{{Special:AllPages|namespace=105}}<br />
== Namespace 106==<br />
{{Special:AllPages|namespace=106}}<br />
== Namespace 107==<br />
{{Special:AllPages|namespace=107}}<br />
<br />
<br />
<br />
[[category:Wikipatys]] [[category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide/FR_ns_liste&diff=30502Wiki Technical Guide/FR ns liste2019-06-30T11:18:41Z<p>Amosys: </p>
<hr />
<div>{{Trad|DE=Wiki Technical Guide/DE ns list|EN=Wiki Technical Guide/EN ns list|FR=Wiki Technical Guide/FR ns liste|ES=|RU=}}<br />
<br />
see https://fr.wiki.ryzom.com/wiki/Wiki_Technical_Guide/FR_ns_liste (commands are KO in here)<br />
Namespace 1 - ARK talk <br />
<br />
Namespace 2 - Utilisateur et Utilisatrices - User<br />
<br />
Namespace 3 - user talk <br />
<br />
Namespace 4 - EncyclopAtys<br />
<br />
Namespace 5 - EncyclopAtys talk<br />
<br />
Namespace 6 - File - Fichier <br />
<br />
Namespace 7 - File talk - Discussions fichier <br />
<br />
Namespace 8 - MediaWiki <br />
<br />
Namespace 9 - empty (MediaWiki talk ?) <br />
<br />
<br />
Namespace 10 - Modèle - Template <br />
<br />
Namespace 11 - Discussion Modèle - Template talk <br />
<br />
Namespace 12 - Aide - Help<br />
<br />
Namespace 13 - Help talk<br />
<br />
<br />
Namespace 14 - Catégorie - Category <br />
<br />
Namespace 15 - Category talk<br />
<br />
Namespace 100 - Guilde<br />
<br />
Namespace 101<br />
<br />
Namespace 102 - empty<br />
<br />
Namespace 103<br />
<br />
Namespace 104<br />
<br />
Namespace 105 - empty<br />
<br />
Namespace 106 - Portail - Portal<br />
<br />
Namespace 107 - Portal talk<br />
<br />
<br />
[[Category:Wikipatys]] [[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide/FR_ns_liste&diff=30501Wiki Technical Guide/FR ns liste2019-06-30T11:11:18Z<p>Amosys: Created page with "{{Trad|DE=Wiki Technical Guide/DE ns list|EN=Wiki Technical Guide/EN ns list|FR=Wiki Technical Guide/FR ns liste|ES=|RU=}} == Namespace 1 - ARK talk == {{Special:AllPages|name..."</p>
<hr />
<div>{{Trad|DE=Wiki Technical Guide/DE ns list|EN=Wiki Technical Guide/EN ns list|FR=Wiki Technical Guide/FR ns liste|ES=|RU=}}<br />
== Namespace 1 - ARK talk ==<br />
{{Special:AllPages|namespace=1}}<br />
== Namespace 2 - Utilisateur et Utilisatrices - User==<br />
{{Special:AllPages|namespace=2}}<br />
== Namespace 3 - user talk ==<br />
{{Special:AllPages|namespace=3}}<br />
== Namespace 4 - EncyclopAtys==<br />
{{Special:AllPages|namespace=4}}<br />
== Namespace 5 - EncyclopAtys talk==<br />
{{Special:AllPages|namespace=5}}<br />
== Namespace 6 - File - Fichier ==<br />
{{Special:AllPages|namespace=6}}<br />
== Namespace 7 - File talk - Discussions fichier ==<br />
{{Special:AllPages|namespace=7}}<br />
== Namespace 8 - MediaWiki ==<br />
{{Special:AllPages|namespace=8}}<br />
== Namespace 9 - empty (MediaWiki talk ?) ==<br />
{{Special:AllPages|namespace=9}}<br />
<br />
== Namespace 10 - Modèle - Template ==<br />
{{Special:AllPages|namespace=10}}<br />
== Namespace 11 - Discussion Modèle - Template talk ==<br />
{{Special:AllPages|namespace=11}}<br />
== Namespace 12 - Aide - Help==<br />
{{Special:AllPages|namespace=12}}<br />
== Namespace 13 - Help talk==<br />
{{Special:AllPages|namespace=13}}<br />
<br />
== Namespace 14 - Catégorie - Category ==<br />
{{Special:AllPages|namespace=14}}<br />
== Namespace 15 - Category talk==<br />
{{Special:AllPages|namespace=15}}<br />
== Namespace 100 - Guilde==<br />
{{Special:AllPages|namespace=100}}<br />
== Namespace 101==<br />
{{Special:AllPages|namespace=101}}<br />
== Namespace 102 - empty==<br />
{{Special:AllPages|namespace=102}}<br />
== Namespace 103==<br />
{{Special:AllPages|namespace=103}}<br />
== Namespace 104==<br />
{{Special:AllPages|namespace=104}}<br />
== Namespace 105 - empty==<br />
{{Special:AllPages|namespace=105}}<br />
== Namespace 106 - Portail - Portal==<br />
{{Special:AllPages|namespace=106}}<br />
== Namespace 107 - Portal talk==<br />
{{Special:AllPages|namespace=107}}<br />
<br />
[[Category:Wikipatys]] [[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide/Special_Pages&diff=30499Wiki Technical Guide/Special Pages2019-06-30T10:40:08Z<p>Amosys: </p>
<hr />
<div><big>About Special Pages - Au sujet des Pages Spéciales</big><br />
<!-- Add here some special pages you think are usefull --><br />
{|cellspacing="0" cellpadding="5" border="1" style="text-align:left;" class="sortable" <br />
|-bgcolor="#eee" style="color:black;" <br />
!EN wiki <br />
!FR wiki <br />
!DE wiki <br />
!Common <br />
!Notes <br />
|-<br />
|https://en.wiki.ryzom.com/wiki/Special:Statistics<br />
|https://fr.wiki.ryzom.com/wiki/Sp%C3%A9cial:Statistiques<br />
|https://de.wiki.ryzom.com/wiki/Spezial:Statistik<br />
|https://atys.wiki.ryzom.com/wiki/Special:Statistics<br />
| Stats: '''Page''': content, all p (talk p, redirects...),upload files ; '''Edit''' ; '''User''' (registered, active, bots, admins, Bureaucrats)<br />
|- <br />
|[[Special:MassEditRegex]]<br />
|[https://fr.wiki.ryzom.com/wiki/Sp%C3%A9cial%3AMassEditRegex Modification en masse avec expr. rationnelles] <br />
|https://de.wiki.ryzom.com/wiki/Spezial:Regex-Massenbearbeitung<br />
|https://atys.wiki.ryzom.com/wiki/Special:MassEditRegex<br />
|'''Caution here !!!''' see https://regex101.com/<br />
|-<br />
|[[Special:LongPages]]<br />
|[https://fr.wiki.ryzom.com/wiki/Sp%C3%A9cial%3APages_longues FR P longues]<br />
|https://de.wiki.ryzom.com/wiki/Spezial:L%C3%A4ngste_Seiten<br />
|https://atys.wiki.ryzom.com/wiki/Special:LongPages<br />
|Wiki IG need small pages (text + image size). I think long page is text only (image code only, not adding image size ? '''to check''')<br />
|-<br />
|https://en.wiki.ryzom.com/w/index.php?title=Special%3APrefixIndex&prefix=Amosys%2FDraft%2F&namespace=2&stripprefix=1<br />
|https://fr.wiki.ryzom.com/wiki/Sp%C3%A9cial:Index<br />
|<br />
|https://atys.wiki.ryzom.com/w/index.php?title=Special%3APrefixIndex&prefix=&namespace=0&stripprefix=1<br />
|see [[File:Special Pages p with prefix 2019-06-26.png|thumb]]<br />
|-<br />
<!-- Thanks to copy paste theses lines, for easy use --><br />
|<!-- For EN wiki col --><br />
|<!-- For FR wiki col --><br />
|<!-- For DE wiki col --><br />
|<!-- For ATYS common wiki col --><br />
|<!-- For Notes col --><br />
|} <br />
<br />
To [[Wiki Technical Guide/Comparaison of lists ns and other]] it's a backup/translations and reorganisation of Heernis work, on the 2019 06 30<br />
<br />
To [[Wiki Technical Guide/API]].<br />
<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide/Special_Pages&diff=30498Wiki Technical Guide/Special Pages2019-06-30T10:22:41Z<p>Amosys: </p>
<hr />
<div><big>About Special Pages - Au sujet des Pages Spéciales</big><br />
<!-- Add here some special pages you think are usefull --><br />
{|cellspacing="0" cellpadding="5" border="1" style="text-align:left;" class="sortable" <br />
|-bgcolor="#eee" style="color:black;" <br />
!EN wiki <br />
!FR wiki <br />
!DE wiki <br />
!Common <br />
!Notes <br />
|-<br />
|https://en.wiki.ryzom.com/wiki/Special:Statistics<br />
|https://fr.wiki.ryzom.com/wiki/Sp%C3%A9cial:Statistiques<br />
|https://de.wiki.ryzom.com/wiki/Spezial:Statistik<br />
|https://atys.wiki.ryzom.com/wiki/Special:Statistics<br />
| Stats: '''Page''': content, all p (talk p, redirects...),upload files ; '''Edit''' ; '''User''' (registered, active, bots, admins, Bureaucrats)<br />
|- <br />
|[[Special:MassEditRegex]]<br />
|[https://fr.wiki.ryzom.com/wiki/Sp%C3%A9cial%3AMassEditRegex Modification en masse avec expr. rationnelles] <br />
|https://de.wiki.ryzom.com/wiki/Spezial:Regex-Massenbearbeitung<br />
|https://atys.wiki.ryzom.com/wiki/Special:MassEditRegex<br />
|'''Caution here !!!''' see https://regex101.com/<br />
|-<br />
|[[Special:LongPages]]<br />
|[https://fr.wiki.ryzom.com/wiki/Sp%C3%A9cial%3APages_longues FR P longues]<br />
|https://de.wiki.ryzom.com/wiki/Spezial:L%C3%A4ngste_Seiten<br />
|https://atys.wiki.ryzom.com/wiki/Special:LongPages<br />
|Wiki IG need small pages (text + image size). I think long page is text only (image code only, not adding image size ? '''to check''')<br />
|-<br />
|https://en.wiki.ryzom.com/w/index.php?title=Special%3APrefixIndex&prefix=Amosys%2FDraft%2F&namespace=2&stripprefix=1<br />
|https://fr.wiki.ryzom.com/wiki/Sp%C3%A9cial:Index<br />
|<br />
|https://atys.wiki.ryzom.com/w/index.php?title=Special%3APrefixIndex&prefix=&namespace=0&stripprefix=1<br />
|see [[File:Special Pages p with prefix 2019-06-26.png|thumb]]<br />
|-<br />
<!-- Thanks to copy paste theses lines, for easy use --><br />
|<!-- For EN wiki col --><br />
|<!-- For FR wiki col --><br />
|<!-- For DE wiki col --><br />
|<!-- For ATYS common wiki col --><br />
|<!-- For Notes col --><br />
|} <br />
<br />
<br />
<br />
https://atys.wiki.ryzom.com/wiki/Special:Statistics<br />
To [[Wiki Technical Guide/API]].<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide/Special_Pages&diff=30496Wiki Technical Guide/Special Pages2019-06-30T10:16:32Z<p>Amosys: </p>
<hr />
<div><big>About Special Pages - Au sujet des Pages Spéciales</big><br />
<!-- Add here some special pages you think are usefull --><br />
{|cellspacing="0" cellpadding="5" border="1" style="text-align:left;" class="sortable" <br />
|-bgcolor="#eee" style="color:black;" <br />
!EN wiki <br />
!FR wiki <br />
!DE wiki <br />
!Common <br />
!Notes <br />
|-<br />
|https://en.wiki.ryzom.com/wiki/Special:Statistics<br />
|https://fr.wiki.ryzom.com/wiki/Sp%C3%A9cial:Statistiques<br />
|https://de.wiki.ryzom.com/wiki/Spezial:Statistik<br />
|https://atys.wiki.ryzom.com/wiki/Special:Statistics<br />
| Stats: '''Page''': content, all p (talk p, redirects...),upload files ; '''Edit''' ; '''User''' (registered, active, bots, admins, Bureaucrats)<br />
|- <br />
|[[Special:MassEditRegex]]<br />
|[https://fr.wiki.ryzom.com/wiki/Sp%C3%A9cial%3AMassEditRegex Modification en masse avec expr. rationnelles] <br />
|https://de.wiki.ryzom.com/wiki/Spezial:Regex-Massenbearbeitung<br />
|https://atys.wiki.ryzom.com/wiki/Special:MassEditRegex<br />
|'''Caution here !!!''' see https://regex101.com/<br />
|-<br />
|[[Special:LongPages]]<br />
|[https://fr.wiki.ryzom.com/wiki/Sp%C3%A9cial%3APages_longues FR P longues]<br />
|https://de.wiki.ryzom.com/wiki/Spezial:L%C3%A4ngste_Seiten<br />
|https://atys.wiki.ryzom.com/wiki/Special:LongPages<br />
|Wiki IG need small pages (text + image size). I think long page is text only (image code only, not adding image size ? '''to check''')<br />
|-<br />
|https://en.wiki.ryzom.com/w/index.php?title=Special%3APrefixIndex&prefix=Amosys%2FDraft%2F&namespace=2&stripprefix=1<br />
|https://fr.wiki.ryzom.com/wiki/Sp%C3%A9cial:Index<br />
|<br />
|<br />
|see <br />
[[File:Special Pages p with prefix 2019-06-26.png|thumb]]<br />
|-<br />
<!-- Thanks to copy paste theses lines, for easy use --><br />
|<!-- For EN wiki col --><br />
|<!-- For FR wiki col --><br />
|<!-- For DE wiki col --><br />
|<!-- For ATYS common wiki col --><br />
|<!-- For Notes col --><br />
|} <br />
<br />
<br />
<br />
https://atys.wiki.ryzom.com/wiki/Special:Statistics<br />
To [[Wiki Technical Guide/API]].<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Wiki_Technical_Guide/Special_Pages&diff=30494Wiki Technical Guide/Special Pages2019-06-30T10:10:19Z<p>Amosys: </p>
<hr />
<div><big>About Special Pages - Au sujet des Pages Spéciales</big><br />
<!-- Add here some special pages you think are usefull --><br />
{|cellspacing="0" cellpadding="5" border="1" style="text-align:left;" class="sortable" <br />
|-bgcolor="#eee" style="color:black;" <br />
!EN wiki <br />
!FR wiki <br />
!DE wiki <br />
!Common <br />
!Notes <br />
|-<br />
|https://en.wiki.ryzom.com/wiki/Special:Statistics<br />
|https://fr.wiki.ryzom.com/wiki/Sp%C3%A9cial:Statistiques<br />
|https://de.wiki.ryzom.com/wiki/Spezial:Statistik<br />
|https://atys.wiki.ryzom.com/wiki/Special:Statistics<br />
| Stats: '''Page''': content, all p (talk p, redirects...),upload files ; '''Edit''' ; '''User''' (registered, active, bots, admins, Bureaucrats)<br />
|- <br />
|[[Special:MassEditRegex]]<br />
|[https://fr.wiki.ryzom.com/wiki/Sp%C3%A9cial%3AMassEditRegex Modification en masse avec expr. rationnelles] <br />
|de ?<br />
|https://atys.wiki.ryzom.com/wiki/Special:MassEditRegex<br />
|'''Caution here !!!''' see https://regex101.com/<br />
|-<br />
|[[Special:LongPages]]<br />
|[https://fr.wiki.ryzom.com/wiki/Sp%C3%A9cial%3APages_longues FR P longues]<br />
|de ?<br />
|<br />
|Wiki IG need small pages (text + image size). I think long page is text only (image code only, not adding image size ? '''to check''')<br />
|-<br />
|https://en.wiki.ryzom.com/w/index.php?title=Special%3APrefixIndex&prefix=Amosys%2FDraft%2F&namespace=2&stripprefix=1<br />
|https://fr.wiki.ryzom.com/wiki/Sp%C3%A9cial:Index<br />
|<br />
|<br />
|see <br />
[[File:Special Pages p with prefix 2019-06-26.png|thumb]]<br />
|-<br />
<!-- Thanks to copy paste theses lines, for easy use --><br />
|<!-- For EN wiki col --><br />
|<!-- For FR wiki col --><br />
|<!-- For DE wiki col --><br />
|<!-- For ATYS common wiki col --><br />
|<!-- For Notes col --><br />
|} <br />
<br />
<br />
<br />
https://atys.wiki.ryzom.com/wiki/Special:Statistics<br />
To [[Wiki Technical Guide/API]].<br />
-----------------------------------------------------------------------------------------------<br />
<references/><br />
{{clear}}{{Last version link}}<br />
<noinclude>{{Portal|Wikipatys|}}</noinclude><br />
[[Category:Wikipatys]][[Category:Encyclopatys]][[Category:Help]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Armour_and_Shields&diff=30493Armour and Shields2019-06-30T09:31:34Z<p>Amosys: </p>
<hr />
<div>'''Type:''' Crafting<br />
<br />
'''Race:''' Zoraï<br />
<br />
=Prerequisites=<br />
==Special order for armour (Nai-Da Fuangi, Zora trainers)==<br />
* Zoraï fame 0+<br />
<br />
* 2 x Tan-ko pants x40 (Zoraï BQ heavy pants)<br />
* 2 x Shaï-don sleeves q30 (Zoraï BQ medium sleeves)<br />
==Nai-Da Fuangi needs armour==<br />
* Zoraï fame 0+<br />
<br />
* 8 x Pakmon Shield q11<br />
* 2 x Kastu Buckler q35<br />
==Wu Zhong (Zora, South Gate) wants made-to-order armour==<br />
* Zoraï fame +0<br />
<br />
* 5 x Tan-ko Boots q12 (Zoraï BQ heavy boots)<br />
* 5 x Shaï-don Vest q18 (Zoraï BQ medium vest)<br />
* 18 minute timer<br />
<br />
==Rite Mission==<br />
La-Po Len (Zora, Highmart District), The old Zoraï Smith<br />
* Craft lvl 25+<br />
* Zoraï fame 34<br />
[[Category:Rites]] [[Category:Craft]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=User:Craftjenn/OCC_Notes&diff=30492User:Craftjenn/OCC Notes2019-06-30T09:29:11Z<p>Amosys: /* OCC Notes */</p>
<hr />
<div>{{Tabs<br />
|Tab-1=Craftjenn<br />
|URL-1=User:Craftjenn<br />
|Image-1=Dummy.png<br />
<br />
<!--|background Tab-1=#fef--><br />
|Tab-2=OCC Notes<br />
|URL-2={{PAGENAME}}<br />
|background Tab-2=#fef<br />
|border=2px solid #636<br />
<!--|background div=#fff--><br />
|round=5em<br />
|align_tab=center<br />
}}</noinclude><br />
<br />
<!-- Paste the code above at the top of your new OCC page. No need to change it --><br />
<br />
<!-- Add the languages flags, to create a translation on the correct wiki --><br />
{{Trad<br />
|DE=<br />
|EN={{PAGENAME}}<br />
|ES=<br />
|FR=Utilisatrice:Craftjenn/NotesCJ<br />
|RU=<br />
}}<br />
<br />
{{Obsolete}}<br />
<br />
<br />
<big>Drafts, notes, OCC...</big><br />
* https://chat.ryzom.com/channel/ryzom-wiki<br />
* help for translators on wiki [[WikiTrad-EN]],<br />
* [[APageRPandOOC]] (show how to create OCC tab, as on my profile, with many comments)<br />
<br />
== OCC Notes ==<br />
<br />
*I have done several tests, mainly translations. The french and english wikis are sooo different ! Trying to delete and move obsolete/wrong information in wiki (such ceB informations).<br />
<br />
*Now, I am more familiar with the EnclyclopAtys and wrote several tutorials on the French wiki, and some howto pages regarding EnclyclopAtys and how to translate on it. <br /><br />
See for ex <br />
* [[New2019]] about the big 2019's changes, and the ones for 2018, 2017.<br />
* [[Easy Dapper guide]] pasted from the forum... <br />
* At the last Forge meeting, we talked about a [[Memorial Project]]. I didn't found on the forum such project yet, but I created a structure for it.<br />
<br />
It will convenient [https://en.wiki.ryzom.com/w/index.php?title=Talk:Craftjenn/OCC_Notes&action=edit&section=new for Discussions] (the link goes to create an discussion on my English profile), regarding some issues about translations (Spanish, German...) - I will check it for remarks and questions :p<br />
<br />
But I think that the new [https://chat.ryzom.com/channel/pub-ryzom-wiki channel we have now on RC] will be even faster and easier [[File:RClogo211905.png|center|#pub-ryzom-wiki is the RC channel to talk about wikis |link=https://chat.ryzom.com/channel/pub-ryzom-wiki]] :)<br />
<br />
[[Development or novlang ?]]<br />
<br />
=== Help with the wikis ===<br />
*[[Writing Guide]] and the [[:Category:Help]] category<br />
*Here are some [[User:Craftjenn/tips]] (for the English EncyclopAtys).<br />
* Images about help on Wikis should be in Category:Wiki (Wiki is under Wiki images)<br />
<br />
== Index==<br />
Work in Progress: [[Chat]] [[Chat/RC channel list]], [[Memorial Project]] <br />
<br />
Page I created here (as I am French, thanks to correct my bad english, when done add a comment in my discussion on here)<br />
[[Market]]<br />
[[Webapps/API key]] [[Search and find]] [[Mektoub FAQ]] [[Merchant]] , [[Writing Guide]] Neutral [[Easy Dapper guide]],<br />
[[User:Craftjenn/How I became a Ranger]] User:Craftjenn/bio User:Craftjenn/main <br />
Guild Island/Gallery [[Guild Island]]<br />
[[New2019]] <br />
Development or novlang ?<br />
[[Webapps main]] <br />
[[User:Craftjenn/tips]] [[APageRPandOOC]] [[SOS/catImage]]<br />
[[Atys Mag]]<br />
[[Wheel of fortune/prizes]]<br />
[[New 2018]]<br />
[[WikiTrad-EN]] <br />
[[Help talk:How to help]]<br />
[[WikiTrad/WikiTrad-EN]]<br />
... [[Occupation ighelp]]<br />
[[Guilde:Almatiwood]] [[Rangerlang EN]] [[Rangers]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=User:Craftjenn/Development_or_novlang_%3F&diff=30490User:Craftjenn/Development or novlang ?2019-06-30T09:28:45Z<p>Amosys: Amosys moved page Development or novlang ? to User:Craftjenn/Development or novlang ?</p>
<hr />
<div>{{Trad|EN=Development or novlang ?|FR=Craftjenn/Progrès ou novlangue ?}} <br />
<br />
== For your information ==<br />
This rant page is not only about Atys.<br />
<br />
== On the Karavan interface modules ==<br />
The Karavan interface modules <ref>or PC and by extention: all smartphones using Android or iOs or other + all PC post 2003 years using or Windows or GNU/linux or other + all stuffs who works above : <br /><br />
internet, Ryzom's clients, all the Ryzom related applications and tools, Steam clients, apps but also the printer, usb key, from how access to emails to the government administrations (taxes, health and social assistance access...) </ref> are changing every day. <br />
<br />
Some will say that it is progress. Other <ref>Those who welcome young people, or who supervise the transmission of knowledge, or who try to improve survival and mutual assistance and / or who try to document the subject, etc ...</ref> have a hard time reading and updating the miles of written documentation on the subject, not to mention the many creations and projects that could be organized and co-managed by motivated teams - see the games, various events, gazette and news magazines ... - since the last few hundred years of Jena, written in various dialects, and whose [[Special:ListUsers|traces are found on the EncyclopAtys]].<br />
<br />
If I am asked the question: how many write here? [[User:Zorroargh|The answer is simple: one]]. LOL<br />
This special page shows [[Special:ActiveUsers|Active Users]]. These data are only available on the current month <ref>I think, not shure - if anyone has a way to see over 6 months I'm taking it, but I think no one will read this and take 1mn trouble to answer it</ref>, today I see '''5 homins'''.<br />
<br />
== Atys, a dangerous world ==<br />
I was talking with Wo-Lo Ciai when a young Ranger contacted me about our rite (the Ranger rite). Was I tired ? A jugula killed me, coming on my ass while I was answering her...<br />
<br />
My sister, [[User: Jenn | Jenn]], wanted to join me to rez me - she was nearby a nutela and could be there in 30 seconds, easy... As nutela gives Ranger the ability to jump from a place to an other, very quickly (we have about 18 places like that on Atys). But she was stun by gaz (she was digging in Loria) ? Anyway, she did not notice, on her Ranger map, the 0 :/<br />
<br />
As a result, she was killed, and rez at some far away vortex - far away from any Ranger pathway. This is one of the biggest disadvantage of our travelling system.<br />
<br />
She was very likely to be killed by the same Jugula, given her off level. <br /><br />
<br />
So I made this choice: no jealous, one dp each.<br />
<br />
In a world in a global war, all homin.e.s are in survival mode. <br /><br />
If competition and destruction are valued and encouraged, without mutual help and friendliness, Jugulas kill just for fun Bolobis in total silence, Stinga forests disappear for the benefit of some etc ... so I don't care anymore about DP :p<br />
<br />
== KWPD ==<br />
Novlang or [https://en.wikipedia.org/wiki/Newspeak Newspeak on en.wikipedia.org] begins and is very often [[User_Manual#Common_Acronyms_and_Abbreviations.|acronyms]]. That's why I have chosen this acronym as title, with mockery D <br /><br />
KWPD is for '''Knowledge Wish Power Dare'''<br />
<br />
: The use of acronyms<br />
* it is very useful because fast on the chat,<br />
* it's incomprehensible (specially for a young homin, who for the first time puts his feets on Silan),<br />
* it's omnipresent: on the chat, the forum, the wiki ...<br />
* impossible to search, too short (for ex: SN)<br />
<br />
Knowledge is power. Restricting access to information is the nerve of any war: spying to gain wealth and power, giving false/bad information or worse in an interested way, technical issues can happens too (or go through [https://app.ryzom.com/app_forum/index.php?page=forum/view/1841 fighting with a recalcitrant Karavan interface])...<br />
<br />
In 2600, there are those who are trilingual and have lots of friends, lots of young people who think they understand their interface modules Karavan (which one day will fool them: p), others who drill and craft alone, others who spy digers in PvP zone in order to kill them ... some spend more time chatting than killing kings or forage. In short, some do politics and some do not, everyone on Atys is free to be citizen or stateless, religious or not, and even to change the nation / religion / faction ... the list is long.<br />
<br />
On Atys, we meet many homins, of all races, religions, horizons ...<br /><br />
Some are very active on chat, others leave and come back. Some are very often there but never speak on a wiki or uni, others are talkative (we also have trolls, as everywhere). A certain number tell me "I never read uni fr", or "uni but not uni fr" and vice versa. Everyone has the opportunity to do what they want with what they have.<br />
<br />
<br />
Atys is a mysterious world. Fighting with a "recalcitrant" Karavan interface is also part of life, in a way. But some days, it's still annoying ... When for example, we can not put any more image on the wiki. Or we discover that we no longer have access to the scene editor.<br />
<br />
== Ref ==<br />
<br />
More on <br />
[[User_Manual#Common_Acronyms_and_Abbreviations.]] to compare with https://fr.wiki.ryzom.com/wiki/Manuel_de_l%27utilisateur#Acronymes_usuels_et_abr.C3.A9viations<br />
<br />
<br />
<br />
[[User:Craftjenn|CraftJenn, Ranger du Cercle du Bois d&#39;Almati]] ([[User talk:Craftjenn|talk]]) 13:04, 1 December 2018 (UTC)<br />
[[category:Homins]] [[category:Player]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Development_or_novlang_%3F&diff=30491Development or novlang ?2019-06-30T09:28:45Z<p>Amosys: Amosys moved page Development or novlang ? to User:Craftjenn/Development or novlang ?</p>
<hr />
<div>#REDIRECT [[User:Craftjenn/Development or novlang ?]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Merchant&diff=30481Merchant2019-06-29T02:36:53Z<p>Amosys: /* Links */</p>
<hr />
<div>{{Template:User Manual v4}}{{Trad|EN=Merchant|FR=Marchand}} {{WIP}}<br />
[[File:Fame.jpg|200px|thumb|right|Fame]]<br />
There are Armour, Raw Materials, Weapons, Jewellery, Hawkers, Consumables, Stable boys and several other types of merchants throughout Atys. <br />
All of them will buy your goods. <br />
However, what is sold in one country is not available to purchase in another. <br />
For example, a sword put up for sale in Pyr ([[Desert]]) is not available for players to purchase in Yrkranis ([[Forest]]).<br />
While traveling, you may wish to purchase new armour or replace a pick. If your fame is not good with a particular merchant's race, then expect to pay more and get less.<br />
<br />
Check fame at Task-bar>Communications>FAME>YOU&nbsp;('''Shift+F''').<br />
<br />
<br />
== More on merchants or traders ==<br />
(OCC: all of those are [[:Category:Non Playable Characters|NPC]])<br />
* Most of them are in towns (as trainers, you buy with xp won, see P, on left colon, middle).<br />
Not on [[Silan]] (only on Main Land, [[Atys]]):<br />
* [[Hawker]]s are less specialized, they are moving out of the cities (several places, regarding the [[Time|seasons]], they can be in [[:Category:Tribes|tribe]] camps too...).<br />
* In each capital, there's a special merchant, to use your '''factions points''' (P then Advanced) to get a nice pike, cats, generic mats... The name change (Imperial, Federal, Dynastic...) regarding countries.<br />
<gallery><br />
V3 Cristal Ammo.png|To recharge sap on weapon<br />
ICO Cataliseur XP.png|cats: Free accounts need them to double xp (sub have double xp and don't need them anymore)<br />
V3 c5.png|generic mats<br />
</gallery> <br />
* Stable boys sell Mektoubs and hay, they are in towns. More on [[Mektoub FAQ]].<br />
<br />
=== Links ===<br />
Merchants and buy related:<br />
* see [[Market]] - (about Black Market and other markets organized by [[:Category:Homins|players]], and not by NPC). <br />
* More about [[Dapper]] (OOC: the money on Atys).<br />
<br />
Other<br />
* To the [[User_Manual#Transporters]] (or NH, for New Horizons) and [[Occupations]].<br />
*Note: When you are in a coma, you pay for the care provided by either the [[Portal:Kami|Kami]] or the [[Portal:Karavan|Karavan]] with xp, often by passing by buys TPs in Dappers. They are NPCs but not merchants (have a look on [[Portal:Lore|Lore]] portal).<br />
* '''Brotherhood of the Fortunate Gubani''': If interested in gambling, an avatar may purchase '''[[token]]s''' from the Gubani representative for use in the nearby [[Wheel of fortune]]. If played long enough, the avatar will gain interesting [[Titles|titles]] and more.<br />
<br />
<br />
{{Portal|Society}}<br />
[[Category:Non Playable Characters]] [[Category:Society]]<br />
<br />
<br />
{{Portal bottom}}</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Merchant&diff=30480Merchant2019-06-29T02:33:58Z<p>Amosys: /* More on merchants or traders */</p>
<hr />
<div>{{Template:User Manual v4}}{{Trad|EN=Merchant|FR=Marchand}} {{WIP}}<br />
[[File:Fame.jpg|200px|thumb|right|Fame]]<br />
There are Armour, Raw Materials, Weapons, Jewellery, Hawkers, Consumables, Stable boys and several other types of merchants throughout Atys. <br />
All of them will buy your goods. <br />
However, what is sold in one country is not available to purchase in another. <br />
For example, a sword put up for sale in Pyr ([[Desert]]) is not available for players to purchase in Yrkranis ([[Forest]]).<br />
While traveling, you may wish to purchase new armour or replace a pick. If your fame is not good with a particular merchant's race, then expect to pay more and get less.<br />
<br />
Check fame at Task-bar>Communications>FAME>YOU&nbsp;('''Shift+F''').<br />
<br />
<br />
== More on merchants or traders ==<br />
(OCC: all of those are [[:Category:Non Playable Characters|NPC]])<br />
* Most of them are in towns (as trainers, you buy with xp won, see P, on left colon, middle).<br />
Not on [[Silan]] (only on Main Land, [[Atys]]):<br />
* [[Hawker]]s are less specialized, they are moving out of the cities (several places, regarding the [[Time|seasons]], they can be in [[:Category:Tribes|tribe]] camps too...).<br />
* In each capital, there's a special merchant, to use your '''factions points''' (P then Advanced) to get a nice pike, cats, generic mats... The name change (Imperial, Federal, Dynastic...) regarding countries.<br />
<gallery><br />
V3 Cristal Ammo.png|To recharge sap on weapon<br />
ICO Cataliseur XP.png|cats: Free accounts need them to double xp (sub have double xp and don't need them anymore)<br />
V3 c5.png|generic mats<br />
</gallery> <br />
* Stable boys sell Mektoubs and hay, they are in towns. More on [[Mektoub FAQ]].<br />
<br />
=== Links ===<br />
Merchants and buy related:<br />
* see [[Market]] - (about Black Market and other markets organized by [[:Category:Homins|players]], and not by NPC). <br />
* More about [[Dapper]] (OOC: the money on Atys).<br />
<br />
Other<br />
* To the [[User_Manual#Transporters]] (or NH, for New Horizons) and [[Occupations]].<br />
*Note: When you are in a coma, you pay for the care provided by either the [[Portal:Kami|Kami]] or the [[Portal:Karavan|Karavan]] with xp, often by passing by buys TPs in Dappers. They are NPCs but not merchants (have a look on [[Portal:Lore|Lore]] portal).<br />
* '''Brotherhood of the Fortunate Gubani''': If interested in gambling, an avatar may purchase '''tokens''' from the Gubani representative for use in the nearby wheel-of-fortune. If played long enough, the avatar will gain interesting titles.<br />
<br />
<br />
{{Portal|Society}}<br />
[[Category:Non Playable Characters]] [[Category:Society]]<br />
<br />
<br />
{{Portal bottom}}</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=User:Amosys/Draft/User_Manual/Part_1_-_Create_an_Account_and_Avatar&diff=30479User:Amosys/Draft/User Manual/Part 1 - Create an Account and Avatar2019-06-29T01:50:58Z<p>Amosys: /* Name Your Avatar */</p>
<hr />
<div>{{WIP}}<br />
{{Trad|DE=ToDO|EN={{NAMESPACE}}:{{BASEPAGENAME}}/User Manual/Part 1 - Create an Account and Avatar|FR=Utilisateur:Amosys/Brouillons/Manuel de l'utilisateur/Ch 1 Créer un compte et un personnage}}<br />
{{Template:User Manual v4}}<br />
<br />
==Create an account==<br />
To play Ryzom you need an active player account. <br />
<br />
On the main login screen, click on ''CREATE AN ACCOUNT'' and follow the instructions to open an account on the main server. The account name and password must contain between 5 and 12 lowercase letters or numbers (no symbols can be used). The "username" thus created will be your official account name, but will never be displayed in the game. Press the ''Submit'' button when you are finished.<br />
<br />
This official account <ref>You can access your account via[https://account.ryzom.com/payment_profile/?language=en https://account.ryzom.com] (billing account in the ryzom.com menu). While accessing your character (character name with the same password) at https://app.ryzom.com/ (Web applications in the ryzom.com menu)</ref> is to be used <br />
<gallery><br />
Logon screen.png|main login screen: players do not know the name of the account<br />
FR Ryzom sub form.png|The user account (and billing account) <br />
</gallery><br />
<br />
Each account has 5 locations, for 5 characters. The ''character'' (or avatar, toon) is [[Races of Atys|a homin]] who represents you in the game. <br />
<br />
* If you are coming back to Ryzom, you can ask Support for a restoration (reserved for subscriber accounts).<br />
* Steam players can ask to Ryzom Support to unlink their account from Steam <ref>Specially the one who installed Steam just for playing Ryzom, with a free account (Steam is not free).</ref><br />
<br />
<br />
<br />
<br />
<br />
<br />
===Creating characters===<br />
After logging in (under your username, or account name) on the main Atys server, you will see five free '''slots''' that you can use to create new characters (in columns on the left side of the screen, they contain large question marks <ref>If the window is misplaced, use the Ryzom Installer tool to change its configuration (more on [[User Manual/Part 1 - An issue to log in?|An issue to log in?]]). </ref>). <br />
<br />
To create a new character, select one of these locations and click on the ''CREATE NEW'' button in the bottom right corner of the screen (or double click on the chosen free location).<br />
<br />
<br />
Many of these features will have no impact on the [[:Category:Gameplay|GamePlay]] (the way of playing), such as the appearance of the face or sex. What at the beginning (new player) will have the most impact is the choice of race <ref>For a player who discovers Atys (they are called "the young"), race is the choice that will have a significant impact on the game, because of the links between countries and their regions (impacts the type of raw materials recovered (hunting, fighting or drilling), the position facing the religions and nations of Atys, crafts... More on the [[Portal:Lore]] and its [[:Category:Inhabitants|Inhabitants]]</ref>. After that (when the character is finished), you will not be able to change race, gender or physical appearance - but, later, on the mainland (after leaving the tutorial island called Silan), you will find tattoo and hairdressers who will ask for [[dappers]] (the currency of Atys)...<br />
<br />
<br />
'''Race'''<br />
<br />
Your race ('''CIVILIZATION''' in the left column) will determine the basic appearance, the initial crafting skill of your character (on Silan, the island that serves as a tutorial, we only learn the nation's craft by default of one of the 4 races) and especially the initial "fame" among the various factions and civilizations (or "nations"''') of the game. <br /><br />
Your choice of race will not limit you in exploring the world of Ryzom (the planet '''Atys'''), nor in learning skills. It's more [[:Category:Roleplay|about the roleplay]].<br />
<br />
<br />
'''Gender'''<br />
<br />
Your gender will change your physical appearance, but will otherwise have no affect on the gameplay. Once you've selected your avatar's gender, proceed to the next step in the column on the left. <br />
<br />
OOC: While many female characters are animated by males players, few male characters are animated by female players. Most of RP players will say "She" even knowing IRL it's "he".<br />
<br />
'''Physical appearance'''<br />
<br />
Using the sliders, customize your character's body shape. You can rotate your character by dragging from left to right your mouse left button held and zoom in on it by dragging from front to back your mouse right button held. His physical appearance has no influence on the characteristics (strength, endurance, etc.) of your character. Once you have decided on this appearance, proceed to the next step in the left column.<br />
<br />
'''Facial Customization'''<br />
<br />
Use the sliders to customize your character's face. Depending on your race and gender, you have different possibilities. You can rotate your character's head by dragging your left button mouse from left to right and zooming in on it by dragging your right button mouse back and forth. When you have finished shaping your character's head, proceed to the final step.<br />
<br />
'''Initial skills package'''<br />
<br />
This choice determines the skills and equipment with which your character will begin his life on Atys but has no impact on the gameplay. Your character will start at level 1 in all skills and can increase these levels in any branch without any other being penalized. Use the cursor to choose your initial skill pack (called '''action pack''').<br />
This is not very important.<br />
<br />
====Fame and Alignment====<br />
The race of your avatar influences your reputation with the other races and the two great religious powers (called '''factions'''), the '''Kamis''' and '''Karavan'''. <br />
<br />
Each of the four races has particular affinities with another and has a particular enmity towards a third. <br /><br />
Each race is by nature more favored by one or the other of the two great religious powers: the '''Trykers''' and '''Matis''' have the favors of the Karavan while the '''Zoraïs''' and '''Fyros''' have the favors of the Kamis. <br /><br />
These reputations (known as'''fame'') are initially between -20 and +20 but may subsequently reach, depending on your actions, any level between -100 and +100. These initial reputations do not oblige you to align yourself with a particular nation or religion: you can choose the nation and church you want (within the limits of playability), or even not choose any at all. In any case, you will only be able to choose these allegiances after you have joined the continent, worked on your different reputations and performed certain [[rites]]. It is recommended to think carefully about your "alignment" (at the choice of your faction) because, although it is not irreversible, it is difficult to reverse a maximum reputation (with an initially chosen [[faction]]).<br />
<br />
The line-up will determine which [[guilds]] you can join, which teleport pacts you can get and which players can earn [[PvP]] points by fighting you. It will also determine the side that other players will expect you to join in outpost wars.<br />
<br />
<gallery><br />
Identity Advanced Stats 2019-06-07.png|Identity (press P) Advanced Stats: Faction and Nation points, PvP points, RRP<br />
FR Fame 2019-06-08.png|Your renamed faction and nation<br />
FR fame tribu 2019-06-08.png|and with the tribes<br />
</gallery><br />
<br />
<br />
==== Review ====<br />
Animate your finished avatar with the arrow button in the lower mid-left of the screen. <br /><br />
Review your race, gender, civilization, and initial actions; then select the Finish button at the bottom right of the screen. If displayed, select OK to choose the Atys world community. <br /><br />
Next, choose your key configuration; most modern computer users will prefer the arrow keys to move (together with mouse or trackball). <br />
<br />
<br />
==== Name Your Avatar ====<br />
The final step for your avatar is to select a name. <br />
* Each name on Atys must be unique, permanent, so it may take several attempts to choose a name. Names must adhere to the [https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187223=en#6 Naming Policy] (part of [[Ryzom code of conduct]], under penalty of forced renaming: no known name, no brand, no coarse....). <br />
* Once your name is chosen, you will see your new avatar in a slot on the left. <br />
* Select PLAY to start gameplay on the island of Silan. Silan is a tutorial (how to fight and create stanza, how craft, dig, sell to merchants...), it's not really the game. Wait a little bit then<br />
* click on Chiang the Strong for your first orientation mission. <br />
[[File:UIpreview first screen.png|150px|center|Chiang the Strong - basic presentation|link=User:Amosys/Draft/User_Manual/Part_2_-_Basic_presentation]]<br />
<br />
<br />
<br />
To the [[Ryzom code of conduct]], on the forum the [https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187223=en#6 Naming Policy]<br />
<br />
<br />
<br />
{{Portal bottom}}</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=User:Amosys/Draft/User_Manual/Part_1_-_Create_an_Account_and_Avatar&diff=30478User:Amosys/Draft/User Manual/Part 1 - Create an Account and Avatar2019-06-29T01:42:48Z<p>Amosys: /* Create an account */</p>
<hr />
<div>{{WIP}}<br />
{{Trad|DE=ToDO|EN={{NAMESPACE}}:{{BASEPAGENAME}}/User Manual/Part 1 - Create an Account and Avatar|FR=Utilisateur:Amosys/Brouillons/Manuel de l'utilisateur/Ch 1 Créer un compte et un personnage}}<br />
{{Template:User Manual v4}}<br />
<br />
==Create an account==<br />
To play Ryzom you need an active player account. <br />
<br />
On the main login screen, click on ''CREATE AN ACCOUNT'' and follow the instructions to open an account on the main server. The account name and password must contain between 5 and 12 lowercase letters or numbers (no symbols can be used). The "username" thus created will be your official account name, but will never be displayed in the game. Press the ''Submit'' button when you are finished.<br />
<br />
This official account <ref>You can access your account via[https://account.ryzom.com/payment_profile/?language=en https://account.ryzom.com] (billing account in the ryzom.com menu). While accessing your character (character name with the same password) at https://app.ryzom.com/ (Web applications in the ryzom.com menu)</ref> is to be used <br />
<gallery><br />
Logon screen.png|main login screen: players do not know the name of the account<br />
FR Ryzom sub form.png|The user account (and billing account) <br />
</gallery><br />
<br />
Each account has 5 locations, for 5 characters. The ''character'' (or avatar, toon) is [[Races of Atys|a homin]] who represents you in the game. <br />
<br />
* If you are coming back to Ryzom, you can ask Support for a restoration (reserved for subscriber accounts).<br />
* Steam players can ask to Ryzom Support to unlink their account from Steam <ref>Specially the one who installed Steam just for playing Ryzom, with a free account (Steam is not free).</ref><br />
<br />
<br />
<br />
<br />
<br />
<br />
===Creating characters===<br />
After logging in (under your username, or account name) on the main Atys server, you will see five free '''slots''' that you can use to create new characters (in columns on the left side of the screen, they contain large question marks <ref>If the window is misplaced, use the Ryzom Installer tool to change its configuration (more on [[User Manual/Part 1 - An issue to log in?|An issue to log in?]]). </ref>). <br />
<br />
To create a new character, select one of these locations and click on the ''CREATE NEW'' button in the bottom right corner of the screen (or double click on the chosen free location).<br />
<br />
<br />
Many of these features will have no impact on the [[:Category:Gameplay|GamePlay]] (the way of playing), such as the appearance of the face or sex. What at the beginning (new player) will have the most impact is the choice of race <ref>For a player who discovers Atys (they are called "the young"), race is the choice that will have a significant impact on the game, because of the links between countries and their regions (impacts the type of raw materials recovered (hunting, fighting or drilling), the position facing the religions and nations of Atys, crafts... More on the [[Portal:Lore]] and its [[:Category:Inhabitants|Inhabitants]]</ref>. After that (when the character is finished), you will not be able to change race, gender or physical appearance - but, later, on the mainland (after leaving the tutorial island called Silan), you will find tattoo and hairdressers who will ask for [[dappers]] (the currency of Atys)...<br />
<br />
<br />
'''Race'''<br />
<br />
Your race ('''CIVILIZATION''' in the left column) will determine the basic appearance, the initial crafting skill of your character (on Silan, the island that serves as a tutorial, we only learn the nation's craft by default of one of the 4 races) and especially the initial "fame" among the various factions and civilizations (or "nations"''') of the game. <br /><br />
Your choice of race will not limit you in exploring the world of Ryzom (the planet '''Atys'''), nor in learning skills. It's more [[:Category:Roleplay|about the roleplay]].<br />
<br />
<br />
'''Gender'''<br />
<br />
Your gender will change your physical appearance, but will otherwise have no affect on the gameplay. Once you've selected your avatar's gender, proceed to the next step in the column on the left. <br />
<br />
OOC: While many female characters are animated by males players, few male characters are animated by female players. Most of RP players will say "She" even knowing IRL it's "he".<br />
<br />
'''Physical appearance'''<br />
<br />
Using the sliders, customize your character's body shape. You can rotate your character by dragging from left to right your mouse left button held and zoom in on it by dragging from front to back your mouse right button held. His physical appearance has no influence on the characteristics (strength, endurance, etc.) of your character. Once you have decided on this appearance, proceed to the next step in the left column.<br />
<br />
'''Facial Customization'''<br />
<br />
Use the sliders to customize your character's face. Depending on your race and gender, you have different possibilities. You can rotate your character's head by dragging your left button mouse from left to right and zooming in on it by dragging your right button mouse back and forth. When you have finished shaping your character's head, proceed to the final step.<br />
<br />
'''Initial skills package'''<br />
<br />
This choice determines the skills and equipment with which your character will begin his life on Atys but has no impact on the gameplay. Your character will start at level 1 in all skills and can increase these levels in any branch without any other being penalized. Use the cursor to choose your initial skill pack (called '''action pack''').<br />
This is not very important.<br />
<br />
====Fame and Alignment====<br />
The race of your avatar influences your reputation with the other races and the two great religious powers (called '''factions'''), the '''Kamis''' and '''Karavan'''. <br />
<br />
Each of the four races has particular affinities with another and has a particular enmity towards a third. <br /><br />
Each race is by nature more favored by one or the other of the two great religious powers: the '''Trykers''' and '''Matis''' have the favors of the Karavan while the '''Zoraïs''' and '''Fyros''' have the favors of the Kamis. <br /><br />
These reputations (known as'''fame'') are initially between -20 and +20 but may subsequently reach, depending on your actions, any level between -100 and +100. These initial reputations do not oblige you to align yourself with a particular nation or religion: you can choose the nation and church you want (within the limits of playability), or even not choose any at all. In any case, you will only be able to choose these allegiances after you have joined the continent, worked on your different reputations and performed certain [[rites]]. It is recommended to think carefully about your "alignment" (at the choice of your faction) because, although it is not irreversible, it is difficult to reverse a maximum reputation (with an initially chosen [[faction]]).<br />
<br />
The line-up will determine which [[guilds]] you can join, which teleport pacts you can get and which players can earn [[PvP]] points by fighting you. It will also determine the side that other players will expect you to join in outpost wars.<br />
<br />
<gallery><br />
Identity Advanced Stats 2019-06-07.png|Identity (press P) Advanced Stats: Faction and Nation points, PvP points, RRP<br />
FR Fame 2019-06-08.png|Your renamed faction and nation<br />
FR fame tribu 2019-06-08.png|and with the tribes<br />
</gallery><br />
<br />
<br />
==== Review ====<br />
Animate your finished avatar with the arrow button in the lower mid-left of the screen. <br /><br />
Review your race, gender, civilization, and initial actions; then select the Finish button at the bottom right of the screen. If displayed, select OK to choose the Atys world community. <br /><br />
Next, choose your key configuration; most modern computer users will prefer the arrow keys to move (together with mouse or trackball). <br />
<br />
<br />
==== Name Your Avatar ====<br />
The final step for your avatar is to select a name. <br />
* Each name on Atys must be unique, permanent, so it may take several attempts to choose a name. Names must adhere to the [https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187223=en#6 Naming Policy] (part of [[Ryzom code of conduct]], under penalty of forced renaming: no known name, no brand, no coarse....). <br />
* Once your name is chosen, you will see your new avatar in a slot on the left. <br />
* Select PLAY to start gameplay on the island of Silan. Silan is a tutorial (how to fight and create stanza, how craft, dig, sell to merchants...), it's not really the game. Wait a little bit then<br />
* click on Chiang the Strong for your first orientation mission. <br />
[[File:UIpreview first screen.png|150px|center|Chiang the Strong - basic presentation|link=User:Amosys/Draft/User_Manual/Part_2_-_Basic_presentation]]<br />
<br />
<br />
<br />
To the [[Ryzom code of conduct]], on the forum the [https://app.ryzom.com/app_forum/index.php?page=topic/view/28406/1&post187223=en#6 Naming Policy]<br />
--------------------------------------------------------------</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=User:Amosys/Draft/User_Manual/Part_1_-_Install_the_game&diff=30477User:Amosys/Draft/User Manual/Part 1 - Install the game2019-06-29T01:05:55Z<p>Amosys: </p>
<hr />
<div>{{WIP}}<br />
{{Trad|DE=ToDO|EN=User:Amosys/Draft/User Manual/Part 1 - Install the game|FR=Utilisateur:Amosys/Brouillons/Manuel de l'utilisateur/Ch 1}} See FR version <br />
{{Template:User Manual v4}}<br />
How you do this will depend on your operating system; follow the instructions at http://ryzom.com<br />
<br />
=== New content and roadmap===<br />
<br />
* We now have access to the current '''[https://board.ryzom.com/?controller=BoardViewController&action=readonly&token=c46b5ea0f37c83d155f3eacc3acf6956ee75cbfca4afa3f2c107fcb4e74d&lang=en&from_index=1 Roadmap]''' ans you'll find [https://app.ryzom.com/app_forum/index.php?page=post%2Fview%2F186177&lang=en explanations about it].<br />
* Read on the forum the [https://app.ryzom.com/app_forum/index.php?page=forum%2Fview%2F1839%2F1&lang=en OFFICIAL NEWS], it announce all the new features <br />
* https://bitbucket.org/ryzom/<br />
<br />
In short :<br />
* [[Patch 2019]]: Clients Improvements (as UI-Scale for ex), new bosses, Guild Islands, New rewards at [[Wheel of fortune|Wheel of Fortune]] :p<br />
* [[New 2018|Patch 2018]]: we can go back to Silan ([https://app.ryzom.com/app_forum/index.php?page=topic/view/28179/6#6 Patch 3.2.1]), [https://app.ryzom.com/app_forum/index.php?page=topic/view/28384/1#1 ranger rite on the forum]...<br />
* [[New2017|Patch 2017]] [[File:Newlooticon.png|thumb|right|Loot lock]] added many new stuffs: new chat, better inventory, new '''Loot Locking System'''...<br />
* From October 2016, all clients migrates from 2.x (and oldiers) to 3.0, with a new installer/patch system.</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=User:Amosys/Draft/User_Manual/Part_1_-_Install_the_game&diff=30476User:Amosys/Draft/User Manual/Part 1 - Install the game2019-06-29T01:05:34Z<p>Amosys: </p>
<hr />
<div>{{WIP}}<br />
{{Trad|DE=ToDO|EN=User:Amosys/Draft/User Manual/Part 1 - Install the game|FR=Utilisateur:Amosys/Brouillons/Manuel de l'utilisateur/Ch 1}} See FR version<br />
{{Template:User Manual v4}}<br />
How you do this will depend on your operating system; follow the instructions at http://ryzom.com<br />
<br />
=== New content and roadmap===<br />
<br />
* We now have access to the current '''[https://board.ryzom.com/?controller=BoardViewController&action=readonly&token=c46b5ea0f37c83d155f3eacc3acf6956ee75cbfca4afa3f2c107fcb4e74d&lang=en&from_index=1 Roadmap]''' ans you'll find [https://app.ryzom.com/app_forum/index.php?page=post%2Fview%2F186177&lang=en explanations about it].<br />
* Read on the forum the [https://app.ryzom.com/app_forum/index.php?page=forum%2Fview%2F1839%2F1&lang=en OFFICIAL NEWS], it announce all the new features <br />
* https://bitbucket.org/ryzom/<br />
<br />
In short :<br />
* [[Patch 2019]]: Clients Improvements (as UI-Scale for ex), new bosses, Guild Islands, New rewards at [[Wheel of fortune|Wheel of Fortune]] :p<br />
* [[New 2018|Patch 2018]]: we can go back to Silan ([https://app.ryzom.com/app_forum/index.php?page=topic/view/28179/6#6 Patch 3.2.1]), [https://app.ryzom.com/app_forum/index.php?page=topic/view/28384/1#1 ranger rite on the forum]...<br />
* [[New2017|Patch 2017]] [[File:Newlooticon.png|thumb|right|Loot lock]] added many new stuffs: new chat, better inventory, new '''Loot Locking System'''...<br />
* From October 2016, all clients migrates from 2.x (and oldiers) to 3.0, with a new installer/patch system.</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Merchant&diff=30475Merchant2019-06-29T00:53:06Z<p>Amosys: /* More on merchants or traders */</p>
<hr />
<div>{{Template:User Manual v4}}{{Trad|EN=Merchant|FR=Marchand}} {{WIP}}<br />
[[File:Fame.jpg|200px|thumb|right|Fame]]<br />
There are Armour, Raw Materials, Weapons, Jewellery, Hawkers, Consumables, Stable boys and several other types of merchants throughout Atys. <br />
All of them will buy your goods. <br />
However, what is sold in one country is not available to purchase in another. <br />
For example, a sword put up for sale in Pyr ([[Desert]]) is not available for players to purchase in Yrkranis ([[Forest]]).<br />
While traveling, you may wish to purchase new armour or replace a pick. If your fame is not good with a particular merchant's race, then expect to pay more and get less.<br />
<br />
Check fame at Task-bar>Communications>FAME>YOU&nbsp;('''Shift+F''').<br />
<br />
<br />
== More on merchants or traders ==<br />
(OCC: all of those are [[:Category:Non Playable Characters|NPC]])<br />
* Most of them are in towns (as trainers, you buy with xp won, see P, on left colon, middle).<br />
Not on [[Silan]] (only on Main Land, [[Atys]]):<br />
* [[Hawker]]s are less specialized, they are moving out of the cities (several places, regarding the [[Time|seasons]], they can be in [[:Category:Tribes|tribe]] camps too...).<br />
* In each capital, there's a special merchant, to use your '''factions points''' (P then Advanced) to get a nice pike, cats, generic mats... The name change (Imperial, Federal, Dynastic...) regarding countries.<br />
<gallery><br />
V3 Cristal Ammo.png|To recharge sap on weapon<br />
ICO Cataliseur XP.png|cats: Free accounts need them to double xp (sub have double xp and don't need them anymore)<br />
V3 c5.png|generic mats<br />
</gallery> <br />
* Stable boys sell Mektoubs and hay, they are in towns. More on [[Mektoub FAQ]].<br />
<br />
<br />
<br />
Note: When you are in a coma, you pay for the care provided by either the [[Portal:Kami|Kami]] or the [[Portal:Karavan|Karavan]] with xp, often by passing by buys TPs in Dappers. They are NPCs but not merchants (have a look on [[Portal:Lore|Lore]] portal).<br />
<br />
=== Links ===<br />
Merchants and buy related:<br />
* see [[Market]] - (about Black Market and other markets organized by [[:Category:Homins|players]], and not by NPC). <br />
* More about [[Dapper]] (OOC: the money on Atys).<br />
<br />
Other<br />
* To the [[User_Manual#Transporters]] (or NH, for New Horizons) and [[Occupations]].<br />
<br />
<br />
{{Portal|Society}}<br />
[[Category:Non Playable Characters]] [[Category:Society]]<br />
<br />
<br />
{{Portal bottom}}</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=Merchant&diff=30474Merchant2019-06-29T00:42:18Z<p>Amosys: /* More on merchants or traders */</p>
<hr />
<div>{{Template:User Manual v4}}{{Trad|EN=Merchant|FR=Marchand}} {{WIP}}<br />
[[File:Fame.jpg|200px|thumb|right|Fame]]<br />
There are Armour, Raw Materials, Weapons, Jewellery, Hawkers, Consumables, Stable boys and several other types of merchants throughout Atys. <br />
All of them will buy your goods. <br />
However, what is sold in one country is not available to purchase in another. <br />
For example, a sword put up for sale in Pyr ([[Desert]]) is not available for players to purchase in Yrkranis ([[Forest]]).<br />
While traveling, you may wish to purchase new armour or replace a pick. If your fame is not good with a particular merchant's race, then expect to pay more and get less.<br />
<br />
Check fame at Task-bar>Communications>FAME>YOU&nbsp;('''Shift+F''').<br />
<br />
<br />
== More on merchants or traders ==<br />
(OCC: all of those are [[:Category:Non Playable Characters|NPC]])<br />
* Most of them are in towns (as trainers, you buy with xp won, see P, on left colon, middle).<br />
Not on [[Silan]] (only on Main Land, [[Atys]]):<br />
* [[Hawker]]s are less specialized, they are moving out of the cities (several places, regarding the [[Time|seasons]], they can be in [[:Category:Tribes|tribe]] camps too...).<br />
* In each capital, there's a special merchant, to use your '''factions points''' (P then Advanced) to get a nice pike, cats, generic mats... The name change (Imperial, Federal, Dynastic...) regarding countries.<br />
<gallery><br />
V3 Cristal Ammo.png|To recharge sap on weapon<br />
ICO Cataliseur XP.png|cats: Free accounts need them to double xp (sub have double xp and don't need them anymore)<br />
V3 c5.png|generic mats<br />
</gallery> <br />
* Stable boys sell Mektoubs and hay, they are in towns. More on [[Mektoub FAQ]].<br />
<br />
<br />
<br />
Note: When you are in a coma, you pay for the care provided by either the [[Portal:Kami|Kami]] or the [[Portal:Karavan|Karavan]] in Dappers. They are NPCs but not merchants.<br />
<br />
=== Links ===<br />
Merchants and buy related:<br />
* see [[Market]] - (about Black Market and other markets organized by [[:Category:Homins|players]], and not by NPC). <br />
* More about [[Dapper]] (OOC: the money on Atys).<br />
<br />
Other<br />
* To the [[User_Manual#Transporters]] (or NH, for New Horizons) and [[Occupations]].<br />
<br />
<br />
{{Portal|Society}}<br />
[[Category:Non Playable Characters]] [[Category:Society]]</div>Amosyshttps://en.wiki.ryzom.com/w/index.php?title=User_Manual/Part_2_-_The_4_desktops&diff=30473User Manual/Part 2 - The 4 desktops2019-06-28T23:57:37Z<p>Amosys: </p>
<hr />
<div>{{Trad|EN=User Manual/Part 2 - The 4 desktops|FR=Manuel de l'utilisateur/Ch 2 - Les 4 bureaux}}{{WIP}} <br />
todo: '''reduce differences between EN and FR''' and check images see discussion too<br />
<br />
<br />
Depending on what you do, you're going to want '''to organize your windows''' differently (specially nice using a small screen, such 13"). <br />
<br />
You have 4 different game desktops, by default the shortcuts are F1 to F4 (K to change the shortcuts) - keyboard shortcuts are the same in the Game <ref>Better not change them (specially I or P), as they show/hide basic windows of the game... it could be difficult to talk with friends, or the support :) <br />
</ref>. <br />
<br />
As the default is number '''1''', you can add/hide toolbars and a lot of windows by pressing '''F1''' (hold down the key F1 to open this window):<br />
[[File:EN F1 key held down 2019-06-14.png|thumb|left|Tools and windows of the screen]]Here are some '''basic keyboard shortcuts''' <br />
<br />
* F1, F2, F3 and F4: switch on one of your 4 screens (desktops), while<br />
* holding down the Fx key displays the configuration screen of the screen x (x=1 to 4). It can be used as a reminder of several basic keyboard shortcuts. <br />
On each Fx screen, you can change opacity and hide/show and move several toolbars and windows using<br />
* Status: Identity ('''P'''), Journal of Mission ('''J'''), Encyclopedia ('''Shift+E''')<br />
* Actions & inventory: Inventory ('''I'''), action progression ('''B''') <br />
* Guild and Team: Team ('''T''') and later Guild ('''G''')<br />
* Communication: fame ('''Shift+f'''), web ('''Shift+W'''), '''F'''riends<br />
* Orientation: '''M'''ap <br />
* Animals: '''Shift+P''' (as Pets). <br />
* Options: Configuration ('''U'''), Keybindings (K), Connection ('''Shift+N''' as Network) - in here, '''global to the game'''.<br />
<br />
Some examples:<br />
<gallery><br />
EN f1 2019-06-14 800px.png|Desktop 1 (press F1 to add a 2nd Hands toolbar)<br />
EN F2 2019-06-14 800px.png|Desktop 2 (press F2, add controls, change position and opacity windows)<br />
</gallery><br />
<br />
<br />
<br />
=== Status ===<br />
[[File:V3 spe status.png]]Identity (P), Mission (J), Target HP, My bars, Bonus/Malus, Encyclopedia (Shift+E)<br />
<gallery><br />
Identity Advanced Stats 2019-06-07.png|Identity: adv stats (nation & faction points, RRP)<br />
Encyclopedie.png|FR Encyclopedia (Shift+E) collect several missions for rites.<br />
</gallery><br />
<br />
=== Actions & inventory ===<br />
[[File:V3 ICO mission casket.png|left]]Action bar Hands 1 and 2, Inventory (I), action progression (B), active links<br />
<br />
=== Guild and Team ===<br />
[[File:V3 spe memory.png|Guild and Team]]<br />
Guild info (G)<br />
Guild forum, Team (T)<br />
<br />
=== Communication ===<br />
[[File:V3 spe com.png|Communication]]Main chat (X), Contact list (F as Friend), mailbox (izam, Shift+M), fame (Shift+f), web (Shift+W), AppZone<br />
<gallery><br />
Contact list ex 2019-06-07.png|A contact list<br />
Accueil IG 2019-05-13.png|FR<br />
</gallery><br />
<br />
=== Orientation ===<br />
[[File:R2 icon map small.png]] Compass, map (M)<br />
<br />
=== Animals ===<br />
[[File:V3 spe beast.png]]Shift+P (as Pet)<br />
<br />
=== Options ===<br />
[[File:R2 icon preferences.png]] Configuration (U), Keybindings (K), [[Macros]], Connection (Shift+N as Network), mp3 player, Taskbar<br />
<br />
<br />
<br />
<br />
<br />
<gallery><br />
KeysConf.jpg|K key held down: change the shortcuts<br />
EN f1 2019-06-14 800px.png|An example of Desktop 1 (press F1 to add a 2nd Hands toolbar)<br />
EN F2 2019-06-14 800px.png|An example of Desktop 2 (press F2, add controls, change position and opacity windows)<br />
ChiangTheStrong.jpg|UI config 1 (for ex on Desktop 1)<br />
CustomisedUI.jpg|UI config 2 (for ex on Desktop 2)<br />
</gallery><br />
<br />
<br />
<br />
[[Category:Game mechanics]] [[Category:Gameplay]] [[Category:Starting Out]]</div>Amosys