[DiscordArchive] I remember seeing those. It's an interesting concept.
[DiscordArchive] I remember seeing those. It's an interesting concept.
Archived author: Honey • Posted: 2025-01-17T16:56:23.717000+00:00
Original source
I remember seeing those. It's an interesting concept.
What i don't understand is, if (first pic for all of the below) an object is in a green zone and another object is in a red zone, the objects in green zones are always calculated first. All their actions, spells, gains... anything.
Once all green zones are done the smaller zones are calculated, resulting in a disadvantage of one tick for all objects in these zones.
Also, if an object is in a red zone and casts at another object in the green zone, but the green zones have already been calculated... when does the spell hit? Another full tick later?
Archived author: Takenbacon • Posted: 2025-01-17T16:58:58.697000+00:00
Original source
N worker threads per continent map * N continents (4?) + extra map threads for non continents and instances to prevent blocking + db threads + network threads + ah threads + logger threads + anything else. No cpu is going to support that
Archived author: Takenbacon • Posted: 2025-01-17T16:59:32.588000+00:00
Original source
And again, the big problem is going to be interaction
Archived author: Takenbacon • Posted: 2025-01-17T17:01:00.115000+00:00
Original source
Multiple threads now interacting with zone scripts, pooling, map containers themselves (adding, removing objects), grouping, spells, outdoor pvp zones, battlefields, transports, the list goes on and on
Archived author: blinky • Posted: 2025-01-17T17:01:02.446000+00:00
Original source
Couldn't you just make each continent its own thread so that you don't have the have the problem with between zones
Archived author: blinky • Posted: 2025-01-17T17:01:29.108000+00:00
Original source
Could also serve as starting point for POC
Archived author: Honey • Posted: 2025-01-17T17:02:07.408000+00:00
Original source
The problem is that you can stand in zone 1 and cast at something in zone 2. Or interact in another way. It would need to be thread-safe.