As a Roblox developer, maintaining a shared folder of commonly used module scripts and systems across multiple games is currently too difficult due to how nested packages and package configurations behave.
Current Workflow
- Store and organize many game-agnostic systems into a folder
- Change attributes to modify system behaviors via package configurations
- This works fine on the top folder, but not for nested packages
Problem
- Modifying attributes on a nested package causes the entire parent folder to be marked as modified
Proposed Solution
- Changes to already-existing attributes on nested packages should be marked as a configuration change instead of a package change
- Adding/removing attributes should be when the whole package is marked as modified
If Roblox is able to address this issue, it would improve my development experience because it would help keep my systems portable, modular, and organized. Having to store all my attributes on the parent folder is getting quite ugly
Being able to modify already-existing attributes on something, like ClientFidelityService, without it marking ModulesUniversal as modified, would be very nice.
This would significantly improve workflow for developers who maintain shared system libraries. It keeps attributes meaningful and local to the modules they affect, improves organization, and avoids unnecessary coupling between child and parent packages.