Introduction

Currently, data loaded from packs are consolidated into master objects and then dispersed to various logical classes. This disbursement and secondary storage are unnecessary and add to memory load. This effort would simplify the backend and make for a cleaner runtime data storage scheme.

Why is this feature needed

• Reduced Memory Usage
• Centralized access to configurations
• Direct link between configuration sources and the configurations used
• Takes advantage of changes made for CT to improve the codebase.

Technical Considerations

• Client side storage of Loader Objects
• Removal of intermediate objects like CodecObjectMap => CodecObjectContainer and instead use one record/class
• Remapping of all getter/setter methods to the Loader Objects
  • consolidation of getter/setter methods into fewer distinct classes.
  • Client side references differing from server-side loader object references
• Codec redesign