[DiscordArchive] Eluna aside, isn't the worldserver itself one single thread? Across all maps?
[DiscordArchive] Eluna aside, isn't the worldserver itself one single thread? Across all maps?
Original source
My idea was to add a key-value pair struct core side to set/get non-userdata, then you could set up your own automated events for dealing with specific cross-state events
rektbyfaith
08-23-2022, 08:38 PM #11Archived author: Foe • Posted: 2022-08-23T20:38:16.534000+00:00
Original source
My idea was to add a key-value pair struct core side to set/get non-userdata, then you could set up your own automated events for dealing with specific cross-state events
Original source
I don't think anything more than that is *really* necessary
rektbyfaith
08-23-2022, 08:38 PM #12Archived author: Foe • Posted: 2022-08-23T20:38:38.908000+00:00
Original source
I don't think anything more than that is *really* necessary
Original source
Then you'd be able to handle delayed event calls based on that
rektbyfaith
08-23-2022, 08:38 PM #13Archived author: Foe • Posted: 2022-08-23T20:38:54.266000+00:00
Original source
Then you'd be able to handle delayed event calls based on that
Original source
But this is not something I'll add on the first version, I want to figure out what's exactly necessary first before locking into a solution like that. Async database calls or an in-memory database implementation could also serve this purpose
rektbyfaith
08-23-2022, 08:40 PM #14Archived author: Foe • Posted: 2022-08-23T20:40:41.931000+00:00
Original source
But this is not something I'll add on the first version, I want to figure out what's exactly necessary first before locking into a solution like that. Async database calls or an in-memory database implementation could also serve this purpose
Original source
The idea is then to have a global struct and a per-player struct for persisting data across map changes
rektbyfaith
08-23-2022, 08:48 PM #15Archived author: Foe • Posted: 2022-08-23T20:48:32.717000+00:00
Original source
The idea is then to have a global struct and a per-player struct for persisting data across map changes
1 Guest(s)
1 Guest(s)