Starfinder Playlist
Page 6 of 6 First ... 456
  1. #51

    Join Date
    Mar 2006
    Location
    Arkansas
    Posts
    7,381
    It depends on how you build your modules. If they are client modules, then yes they should work that way. Client modules have to be on the local machine to be opened. Only if the server and clients have identical versions of the client modules can they be force loaded.

  2. #52
    Quote Originally Posted by Griogre
    It depends on how you build your modules. If they are client modules, then yes they should work that way. Client modules have to be on the local machine to be opened. Only if the server and clients have identical versions of the client modules can they be force loaded.
    Ah. I believe mine were all built with the default db.xml. I never realized the impact this had. So common.xml it is (and a lot of rebuilding/renaming). Thanks.

  3. #53

    Join Date
    Mar 2006
    Location
    Arkansas
    Posts
    7,381
    The db.xml modules are server only modules. The common modules are also only server only and can be force loaded onto the clients. Typically you should keep common modules as small as possible since they have to be loaded and transfered every time a client connects.

  4. #54
    One caveat on making them a non-host module type is that it will increase the download time at the beginning of each session. While the module data should cache, it's one more file to check, and if there are any changes, another large download.

    Regards,
    JPG

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
FG Spreadshirt Swag

Log in

Log in