Full Bleed wrote:my understanding was that uploading the tables to the MT campaign I was connecting to as a GM and then player, hosted by another, would dump said table in everyones cache like a token, what you seem to be saying is otherwise, so how should I go about distributing the tables?
Tables are server centric judging by the check box options you can see on them, so the server is the only one that needs to have the tables (though you will have to have "allow look-up by players" check marked on the tables.) If the tables aren't already in the campaign that the server loaded, you can export the tables and send them to whoever is serving and have them import them and save the campaign accordingly.
There is a chance that the server *might* require a restart at that point (not sure about that because I've never installed a table after I started a server.)Lee wrote:FullBleed mentioned on another thread that, as opposed to how MT normally disseminates image assets, table data is sent upon request. Honestly, I haven't gone over that part of the code in detail since it's something I marked for another time.
Not to confuse the issues... but now that I'm looking at it again I wonder if the "Show Table to Players" check box on tables affects this behavior. Probably not, but I usually have this off, so it makes sense that all of the tables wouldn't be disseminated before being accessed (just like assets on maps players don't see aren't disseminated until they access those maps.) It's possible that the table data would be sent to players when they connect to a server if the table was set to "Show Table to Players."
if it dissemenated automatically when you connect or view it, wouldnt it work? I think I did have those listed things checked when I entered them.