Hello there!
I’ve got a question about how bladeid works. I’ve got a Luke Mandalorian Chapter 16 hilt with a crystal chamber and motor. I measured the scanid values of the hilt open (upper hilt that’s not quite a grenade off), hilt closed (upper hilt screwed back on), and blade inserted.
Here’s the scenario:
Using NO_BLADE_ID_RANGE I was able to set up open and closed hilt presets that worked perfectly. On a hunch since the measured id of the blade being inserted was so low compared to a completely open hilt (5800ish versus 700,000ish) I made a third set of blades with a value of 5800ish that also worked perfectly.
I wasn’t using exact numbers since they jump around ± 50 in scanid.
On a second hunch, I set the “blade_in” style to 0 instead of 5800. Still works perfectly!
HERE’S the actual question:
Does BladeID basically scan from 0 on up - meaning, if the blade_in is set to 0 (measured value always over 5800ish) closed hilt is set to 640000 (again, number jumps around a bit but is always over 640k) and NO_BLADE catches the open hilt from 700k to 999999999 - does this work (and it does) because the number in the config is actually minimum cutoff number in a range going up?
It all still works with a blade with a scanid of around 10k
I’m trying to get a handle on how this code actually functions, I’d love to do some fun stuff with sabers that don’t have a grenade section - just a chassis outside the hilt and then a blade inserted. If I’m understanding how this works correctly, it’ll be easy to program.
BY THE WAY - thanks to everyone already asking all kinds of bladeID questions, reading all this has helped immensely.