Beacon categories for checking the beacon_counter
Posted: Thu Jan 22, 2026 7:50 am
I'd like to ask for a change to how beacons count if/what other beacons are around eachother, instead of the two options of "same_type" and "total" that we currently have access too. I imagine this system to work similar to module categories, where you can give a beacon entity a specific category and then on another beacon, you can specify something like:
which means that beacon would only increase its profile if any beacon under that category was in its range. (If this was implemented, i think it'd be a great service to keep "total" as an option, similar to max_level having "infinite" - although I can see the arguement that a modder can easily do this with a for loop 
).
This'd help a lot with mods that add a variety of beacon types, like my own, for balancing and allowing neat interactions between different beacons. A couple examples are:
I have an extremely wide beacon (64x64 range) that i'd love to only ever affect itself, but even with "same_type", any beacon inside its range that uses "total" will be affected by it.
You could implement a system where different beacons entities have different 'frequencies', and only have certain frequencies increment their counter if another frequency beacon was around, which would encourge alternating beacons around a machine.
Code: Select all
beacon_counter = {"beacon-1", "beacon-2"},
This'd help a lot with mods that add a variety of beacon types, like my own, for balancing and allowing neat interactions between different beacons. A couple examples are:
I have an extremely wide beacon (64x64 range) that i'd love to only ever affect itself, but even with "same_type", any beacon inside its range that uses "total" will be affected by it.
You could implement a system where different beacons entities have different 'frequencies', and only have certain frequencies increment their counter if another frequency beacon was around, which would encourge alternating beacons around a machine.