Database vs In Mod Storage

[Baaleos]

with some work... yes


You would need to script the onModLoad event, to reload the data onto the creature.


And then everytime you update the creature with new data, you need to make sure it writes the new values to the database at the same time.


This way, if the server resets, it will have the most recent data, and will load it up when the server loads up again.

[Tenshar]

[Disco]

I think you're getting a bit confused here. We're basically talking about two different things in this thread:

1. Caching of existent data on a waypoint for quick access. This would be a scenario like you got a small list of say colors in a database and you don't want to make a query every time you need a color. So, you do this:

- make an SQL query that retrieves the colors
- store them on a waypoint
- store the waypoint on the module as an object (so you don't need to run GetWaypointByTag() all the time)

This would eliminate a lot of database calls.

2. Collecting data and storing it in one convenient package, for example in the standard BioWare database. What you do is this:

- store your data on a creature (or item) as local variables
- store this creature (or item) in your database as a persistent object when your server closes
- spawn this creature when your server starts so you can read and update your data

I'd personally do #2 with a proper database and dedicated tables, though.

[Tenshar]

[Fireboar]

StoreCampaignObject and RetrieveCampaignObject. You can do this with or without NWNX. With requires some extra scripting.

[Tenshar]

Right its working now, thanks for all the help

- Tenshar