Headless Server Software/Managing Worlds: Difference between revisions

From Resonite Wiki
No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
== Saving Headless Worlds ==  
== Saving Headless Worlds ==  


When you're running a headless client, you may wish to save changes to the world for things like collaborative building. When doing this keep in mind:
When you're running a [[Headless Server Software|headless server]], you may wish to save changes to the world for things like collaborative building. When doing this keep in mind:


# You must have save access to the world you are trying to save.
# You must have save access to the world you are trying to save.
#* Simply loading someone else's world via your [[Headless_Client/Configuration_File|configuration file]] might not give you this permissions.
#* Simply loading someone else's world via your [[Headless_Server_Software/Configuration_File|configuration file]] might not give you this permissions.
# Saving must be configured or invoked, saving is not automatic.  
# Saving must be configured or invoked, saving is not automatic.  
#* Check the parameters with "save" in them on our [[Headless_Client/Configuration_File|configuration file]] page.
#* Check the parameters with "save" in them on our [[Headless_Server_Software/Configuration_File|configuration file]] page.
#* Also see [[Headless_Client/Commands|the headless commands reference]] for how to invoke a save.
#* Also see [[Headless_Server_Software/Commands|the headless commands reference]] for how to invoke a save.
# For Cloud saving ([[Headless_Client/Configuration_File##SaveAsOwner|saveAsOwner:"CloudUser"]]), you must:
# For Cloud saving ([[Headless_Server_Software/Configuration_File##SaveAsOwner|saveAsOwner:"CloudUser"]]), you must:
#* Ensure the headless is logged into a user account
#* Ensure the headless is logged into a user account
#* Ensure the logged in user has cloud storage space for the world and any changes
#* Ensure the logged in user has cloud storage space for the world and any changes

Latest revision as of 00:18, 19 April 2024

Saving Headless Worlds

When you're running a headless server, you may wish to save changes to the world for things like collaborative building. When doing this keep in mind:

  1. You must have save access to the world you are trying to save.
    • Simply loading someone else's world via your configuration file might not give you this permissions.
  2. Saving must be configured or invoked, saving is not automatic.
  3. For Cloud saving (saveAsOwner:"CloudUser"), you must:
    • Ensure the headless is logged into a user account
    • Ensure the logged in user has cloud storage space for the world and any changes

For a smooth experience if you want to save a world from a headless it is recommended to:

  • Copy worlds you might want to save changes to, to the headless user's account using Save As
    • You'll need to log in as the headless user on regular Resonite to do this
  • Utilize Groups, and load the headless world from a group's storage
    • This let's your group work on and save a headless' world without interacting with the headless. The next time it restarts it'll pickup the changes from the group storage.
    • When doing this make sure to disable saving on the headless, make all changes outside it.
  • Experiment: Create a headless, add a cube to the world, save it, make sure the cube stays there. Don't do a lot of work without validating your setup.