Price Point is a simple game about guessing the prices of a bunch of items from the Roblox marketplace!
- Little or loose coupling between components/systems for modularity.
- To be at a comfortable level of challenging - I specifically wanted to use Price Point as a way to experiment with methodology and concepts in a full game, before I take those learnings and work on bigger projects.
This project is partially managed using Rojo. No game framework - just plain old requiring modules!
There's a few interesting things I have noticed that I would like to improve on, even if not for Price Point:
- The file structure could be more organised if things were more structured using folder-by-feature instead of folder-by-type. Folders such as
src/Dataandsrc/Utilend up bundling unrelated modules together, which proved to be less convenient to navigate. - Going forwards my projects will comply with Roblox's Lua style guide. I think it's important that a standard is established within the Roblox OSS space, this is likely our best shot!
- Fusion: Hydrating instances twice can cause conflicts with Value objects. Many of Price Point's UI components were doing this to reduce boilerplate - many of which have been updated to instead use the methods within PropsUtil to avoid this.