Differences

This shows you the differences between two versions of the page.

--- en:creer_un_univers [2016/12/26 08:06] – [The Georges Sheets] Domperss
+++ en:creer_un_univers [2021/12/03 18:19] (current) – external edit 127.0.0.1
@@ Line 5: / Line 5: @@
 ==== Base MySQL ====
-This database system is used for services and the administration of the server, this does not therefore directly concern the world __EXCEPT__ the determination of player accounts and their [[Commands_shard#the_rights|privileges]].
+This database system is used for services and the administration of the server, this does not therefore directly concern the world __EXCEPT__ the determination of player accounts and their [[commandes_shard#the_rights|privileges]].
 ==== The Georges Sheets ====
@@ Line 14: / Line 14: @@
 \\ Once defined, these files are compressed into //packed sheets// files, this is a compact binary version for use by the game server. If you delete the files, the server will recreate them at startup!
 ==== The Primitives ====
-Once all your items, spells, actions, skills etc. Defined in the Georges Sheets, you have to assemble all the bricks to make a world, this is the work of the World Editor, which is much more than a software of creation of map, It is he who makes it possible to compose the world, by sections.
+Once all your //items, spells, actions, and skills// are defined in the Georges Sheets, you have to assemble all the "bricks" for world making. This is a job for the World Editor!! This one is much more than a software for map creation, because it also makes it possible to compose the world in sections.
-\\ Once again, the data is stored as xml files, with different extensions depending on their destination. The server stores them in //code/ ryzom/common/data_leveldesign/primitives//
+\\ Once again, the data is stored as xml files, with different extensions depending on their destination. The server stores them in //code/ryzom/common/data_leveldesign/primitives//.
-\\ This is where it becomes possible to create a specific character, assigned to a task, in a given place. The different bricks composed in the Georges Sheets are used for this purpose. Again, there is a hierarchy system that allows you to define groups of NPCs, creatures, and so on. To then place elements of these groups without having to redefine individually each object/creature/character.
+\\ Now, This is where it becomes possible to create a specific character that's assigned to a task in a given place. This is because the different bricks(composed in the Georges Sheets) are used for this purpose. The hierarchy system allows you to define groups of NPCs, creatures, and so on in a nice and tidy manner... so you then can place elements of these groups without having to redefine(individually) each object/creature/character.
-\\ Again, the server generates its packed sheets at startup in case it is missing.
+\\ Again, the server generates the packed sheets at startup in case it is missing.
 ==== The Persistent Data Record ====
-With the Georges Sheets and Primitives, we get the state of the world when the server starts, at the moment 0. But it will immediately begin to live, the players, through their characters, will make modifications, interact ... To save the world's evolution, keep the memory of the last state of each thing, the Ryzom Core server writes files to the disk without going through a database system.
+With the Georges Sheets and Primitives, we get a "world state" when the server starts(for the moment 0). But it will immediately change(begin to live) because of the players through their characters, modifications made, interaction etc... To save the world's evolution, and keeping the memory of the last state of each and every thing, the Ryzom Core server write files to the disk(without going through a database system).
-\\ This is where all characters, guilds, inventories, creatures position, quest status are stored ...
+\\ This is where all the: characters, guilds, inventories, creatures position, quest statuses are stored...
-\\ The data is stored in //code/ryzom/server/save_shard//, in binary files.
+\\ This kind of data is stored in //code/ryzom/server/save_shard//, in the form of binary files.
-\\ Although it is not normally necessary to do this, it is possible to edit the data using the //pdr_util// utility, which transforms the binary pdr into an editable xml. It can then be reassembled with the same tool. This can be used to massively update data on a large number of characters or creatures.
+\\ Although,  this is not normally necessary, because it is possible to edit the data using the //pdr_util// utility, which transforms the binary "pdr" into an "editable xml". It can then be reassembled with the same tool. This can be used to massively update data on a large number of characters or creatures.
-<WRAP tip> Let's take a sample file: //code/ryzom/server/save_shard/characters/001/account_1_0_pdr.bin//. \\ We see that we are in the part devoted to the characters("characters" in English). The subfolder, 001, is used only to prevent too much data from being stored in the same directory, so the system automatically organizes them into subdirectories. Then we see "account", that means a player account, then "1", so it is the account with ID 1. Then we read 0, it is the first character slot(out of 4 possible ). In this binary file, there is therefore all the data of the first character of the server's first player: inventory, position, skills etc. </WRAP>
+<WRAP tip> Let's take a sample file: //code/ryzom/server/save_shard/characters/001/account_1_0_pdr.bin//. \\ We see that we are in the part devoted to the characters("characters" in English). The subfolder, 001, is used only to prevent too much data from being stored in the same directory, so the system automatically organizes them into sub directories. Then we see "account", this means a player account, then "1", means account with ID 1. Then we read 0, this is the first character slot(out of 4 possible ). Ie: This binary file contains all the data of the first character of the server's first player: inventory, position, skills etc. </WRAP>
 {{tag>Informational Server tutorial}}