-
April 28th, 2011, 10:14 #51
Lesser Deity
- Join Date
- Mar 2006
- Location
- Arkansas
- Posts
- 7,411
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.
-
April 28th, 2011, 13:55 #52
- Join Date
- Jun 2010
- Posts
- 35
Originally Posted by Griogre
-
April 29th, 2011, 23:30 #53
Lesser Deity
- Join Date
- Mar 2006
- Location
- Arkansas
- Posts
- 7,411
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.
-
May 1st, 2011, 00:49 #54
Supreme Deity
- Join Date
- Mar 2007
- Posts
- 20,613
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