Quick answer: Construct 3 event sheet structure inconsistent - some logic in functions, some in event blocks? Mixed organization confuses contributors - establish per-system conventions.
New contributor adds a feature; their code doesn't match the project's style. Reviews catch but slow.
Functions for reuse
Cross-called code lives in functions. Event blocks for trigger-driven gameplay.
One event sheet per system
Inventory.es, Combat.es, Audio.es. Each sheet has clear ownership.
Document the rule
Project README explains the convention. New contributors learn upfront.
Lint via review
Code review catches violations. Convention learned through feedback.
“Inconsistent codebases are slow. Conventions speed up.”
Pick conventions early; revise rarely. The cost is one decision; the value compounds.