#Scene Loading - Expressing required data

2 messages · Page 1 of 1 (latest)

mint thunder
#

Experimenting with a design to try to prompt an author for supplying some kind of data when spawning in a scene.

Looking for answers/feedback regarding the following questions:

  1. Do you hate this, and if so, why?
  2. Is there a way to express this for some arbitrary component 'X' without requiring the author to register a system per X? EG, could this concept be made exportable?
#

Issues I see with this already -

  • Gets funky fast for anything that can't be expressed at the scene root - at the very least that makes this potentially challenging to export.
  • Scales poorly with additional "required" components - API gets unbearably clunky after ~3-4 components, but also, you only get the first panic / warning if you fail to supply the data for multiple fields, which could be a frustrating experience as a dev.