Page MenuHomeFeedback Tracker

Technical Suggestions: The root of all Evil, server performance, duping, item managing
New, WishlistPublic

Description

I think the Database design for dayz needs a complete overhoul.
Currently I think objects/items don't have a Unique ID on the Databases, which supports Duping.

Pro's for this:
Your database entries in the database does not need to be deleted or moved while live. Maintanance on restarts can delete and move data for clean up.
Only the attributes of them change ( deleted,color, location, stackcount and so on.
Possibly saves tons of database and hive hardrive IO... (needs to be theoretical tested by experts)
You have full control over your objects/items.
Hotbar will work better, because when you paint a gun, it will be still the same, only color attribute changes and stuff related to this.

Downs
Managing the unique id's needs to be done on the big public hive, which is an extra load. Servers need to communicate with the hive to call the id's for new spawned stuff etc....

Solution for this: an extra machine which does only manage unique id's, and sends a pool of precalculated id's the servers can pick from if they need to spawn a new item...(if this pool is large enough the communication for id's can be reduced to happen at restart as an idea...and the hive can only check for valid attributes(antihack)

The other thing is: Server side range checks on item manipulation...
I think you are already working on this...

My Suggestions are possibly not new to the Devteam.
My wish is that Dayz steps forward on performance and fighting the cheaters front.
Best Regards Vati.

Details

Legacy ID
2552890480
Severity
None
Resolution
Open
Reproducibility
N/A
Category
Server

Event Timeline

vatixerid set Category to Server.Jul 31 2014, 2:08 PM
vatixerid set Reproducibility to N/A.
vatixerid set Severity to None.
vatixerid set Resolution to Open.
vatixerid set Legacy ID to 2552890480.May 8 2016, 7:16 PM