-
July 18th, 2019, 16:50 #11
The issue you may have with database fields is that only the GM and one other player (if assigned as the owner) can change a database field. This carries into FG scripts running on a player instance - they have the same rights access rights. So, it's possible if you're running code on the GM and player side, that it's not updating the DB field because of ownership. If you have the FG console open on each instance, you'll see warnings about not being able to update fields because they aren't owned - it's not reported as an error, so the console won't pop up.
The usual way to address this is to use OOB messaging - to send the request to the GM instance to update the database.
The issue you'll have with global packages is that they are just "global" to each instance of FG - i.e. any variables stored in them are only within that instance. You could use OOB messaging to run the code on the GM side and access a global package there (so the GM global package stores the data), but if you're doing that you may as well use OOB messaging to read/write to the database and keep the database as the master data store.Private Messages: My inbox is forever filling up with PMs. Please don't send me PMs unless they are actually private/personal messages. General FG questions should be asked in the forums - don't be afraid, the FG community don't bite and you're giving everyone the chance to respond and learn!
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks