We have a map. Here is the device interaction map (shows the channel and wire connections):
It looks ugly, right? It’ll be really hard to debug. This guide will show you how to improve your map logistics and organization.
So first, how do we want to debug? We want to know where the bug occurs and in what system. So, we organize the devices by system. But that’s not enough! The interactions are fundamentally intertwined! This means that to debug, we’ll have to dive into a bowl of noodles. So here, I introduce a concept of boxing.
What do I mean? I mean that sort things into device systems, and the devices can only be wired or broadcast to devices within its own system and a central hub that does all the main stuff. Properties and triggers/buttons that activate the systems are part of the central hub. So now lets look at the device interaction map:
This is so much better! Now we can activate and deactivate systems so much easier! We can activate certain systems for certain people, check what is causing the bug, and much more!
WARNING: This concept can reduce efficiency. To increase efficiency, you can break the rule a bit if you’re using devices like tag zones. But those devices are usually part of the central/main hub.
You can use this concept for minigames and other things. I’ve used that in my voting system.
but thanks.