SL24W24: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
*** '''No reference as we want to keep easy unloading''' | *** '''No reference as we want to keep easy unloading''' | ||
*** '''As soon as a object has a set change-timestamp we no longer need to create UIDs and add them to the save system''' | *** '''As soon as a object has a set change-timestamp we no longer need to create UIDs and add them to the save system''' | ||
*Cleanup postDataLoading/prepareSaving from IPersistable | |||
*'''Slowly go trough all Features and convert to optioned''' | |||
**'''Chat''' | |||
**'''Crafting''' | |||
**'''Crate''' | |||
**Channel | |||
**Head | |||
**Skin | |||
**Trademark | |||
Revision as of 21:37, 17 June 2024
- Stramingling of Datacontainers to generally use Option-System
- Improve Option-System to automatically detect changes made to the objects
- Trigger persistence update for given object
- Implement importance-settings for objects to skip unimportant changes (fuel level)
- Implement delayed saving using first change-timestamping and object registration in a future timeslot?
- Would need generalized Id-System to find the object that needs to be saved in the timeslot
- No reference as we want to keep easy unloading
- As soon as a object has a set change-timestamp we no longer need to create UIDs and add them to the save system
- Cleanup postDataLoading/prepareSaving from IPersistable
- Slowly go trough all Features and convert to optioned
- Chat
- Crafting
- Crate
- Channel
- Head
- Skin
- Trademark