documentation:planning
Planning
- Think about a system that automatically creates a form from attributes in a class. This could make testing a lot easier.
Support rendering entities in the client (clean up/remake old version) EDIT: all these things are postphoned for the moment, since all below depend on render batching algorithms, and shader usage structure, not yet defined
- Networking:
- Created the auto NetworkPacketFactory code generater
- Implement the tests
- Support properties!
- TODO: make sure no invalid factories are loaded from the cache!
- TODO: not using the attribute on the class itself atm
- Implement custom serialization support
- Write a performance test: send loads of packets after each other, see if they all arrive and at what speed (packets/sec)
- Cleanup unused/ commented code
- Add security checks:
- If not all transporters in the manager have a remote counterpart (partial synchronization), then notify.
- If a packettype has been added multiple times, and there are conflicts in resolving the transporters synchronization: notify
- Make sure the networksystem cannot deadlock
- Support UDP
- Support Compact packets
- Create the ServerTransporters: sending to multiple remotes?
- Implement the ConnectClientNonNetworked functionality.
documentation/planning.txt · Last modified: 2024/08/26 13:25 by 127.0.0.1