Server Config/fr: Difference between revisions

<languages/>__TOC__

Vous pouvez en savoir plus sur certaines valeurs sur les pages [[List of server commands|Liste des commandes serveur]] et [[Setting up a Multiplayer Server|Configuration d'un serveur multijoueur]].

    // Code de localisation à 2 lettres à utiliser sur ce serveur. Détermine la langue des messages du serveur.

    // Si non nul, nécessite un mot de passe pour que les joueurs se connectent.

    // Ajouter ou non ce serveur au serveur maître (pour être dans la liste des serveurs publics).

   // Si c'est vrai, les heures et les jours passeront même s'il n'y a aucun joueur en ligne.

   // Cela indique au générateur de monde de sauter des bandes de tronçons. Utile pour tester la génération de gisement de minerai.

   // Le nombre maximum de canaux discussion de groupe qu'un joueur peut créer

     // Seed. Does not guarantee exactly the same world each time!

     // Point to world file which should be loaded on server start (or created if not exists).

     // Defines a world name for new world.

     // There used to be a "Allow cheats" toggle in the create world screen that forbids the use of /gamemode creative even if you are an admin. The config for it is still there.

     // Defines preset of parameters for new world. Possible values: "creativebuilding","surviveandbuild", "exploration" and "wildernesssurvival" (theoretically - any string value).

     // A reference to an entry in the en.json. Basically, id for human-readable names for PlayStyle.  

     // Possible values: "preset-surviveandbuild", "preset-exploration", "preset-wildernesssurvival" and "creativebuilding".

     // World generation type. Possible values: "standard", "superflat".

     // Settings of new world. Basically can use the same properties as with /worldconfig

     // Height of the world.

     // Anything you want to see in Author field, usually it's nickname.

     // List of mods (IDs) that should be ignored.

   #The range an entity has to be in order for clients to receive regular updates for it. May be overriden by entities. The value is the max chunk distance. (e.g. 2 => update all entities not further away than 2 chunks in x/y any dir from a player)

   #This value is capped by each players max chunk range.

   #Cubic size of the chunks on the server (width, length and height)

   #This is ServerChunkSize - 1 if ServerChunkSize is a multiple of 2 (which it really should be)

   #Size of the chunk column request buffer. Every chunk column of WorldGenPass Done needs to be surrounded by chunks of pass PreDone (3x3).  

   #Every PreDone chunk needs to be surrounded by Vegetation (5x5), every Vegetation chunk needs to be surrounded by terrainfeatures (7x7)

   #So in order to complete at least chunk column we have to keep 7x7=49 chunk columns in the queue

  "RequestChunkColumnsQueueSize": 2000,

   #Size of the chunk ready buffer. If buffer is full, the chunk gen thread no longer generates new chunks.  

   #This value can probably stay fairly small because if the main thread is not the bottleneck it will never fill up, but when it is the bottleneck we don't want to overburden it with sending gazillions of chunks to clients.

   #Amount of chunks the SendChunks System may request per tick. Setting this value too high might fill the buffer too quickly and give a disadvantage to other players chunk loading speed.

   #Amount of chunks the SendChunks System may send per tick. Setting this value too high might overburden the client or the network.

   #How often (at most) the SendChunks system should be called in ms (thread sleep time)

   #Amount of chunks the LoadChunks System may generate per tick. Setting this value too might overburden the server.

   #How many seconds between each autosave of the game world.

   #Width and Length of the cube of chunks to load for the spawn area. Setting this value to high will overflow the request buffer.

   #Amount of entities each client can track at most. If the number of spawned entitites near the player goes beyond this number the player will only see the first ones that spawned until some of them despawned

   #Width and Length of Chunk regions

   #After how many seconds a new calendar packet should be sent out to the client. You might want to reduce this interval for very laggy server / client in order for server and client game time to stay in sync.

   #After how many ms all the chunks should be checked if they can be unloaded

   #After how many milliseconds the chunk should get packed

   #After how many unused milliseconds the chunk should get unloaded

   #How much meter of the client position should leak into sever position (every 150ms), used as motion every 200ms

   #How many intervalls (=150m) shall we toleratate clients position out of sync with servers position before we kick him (not used)

   #How often the chunk generator should run in ms (thread sleep time)