What does this Warning mean?
plugin.bit is not configured in build.settings
A few daily builds back we enabled some checking to make sure if you tried to use a plugin but it’s not in the build.settings, we would issue you a warning that you need to do so.
-
It’s possible that you’re using the bit plugin but didn’t include it in build.settings.
-
Something you are using is using it and you didn’t include it in build.settings.
-
Something is triggering a “false-positive”. In which case you can ignore the warning.
Rob
Thx for the fast feedback.
I don’t even know what the bit plugin is 
I will look if something is using this but the message appears in a relative new project, so normally it shouldn’t.
The bit plugin lets you do bitwise math operations like shifting bits left and right, ANDing and ORing numbers together. Lua doesn’t support byte and integer type numbers (everything is handled as a double float).
Back in the day, if you needed to save space when sending data over the network, we had to pack as much as we could into a byte or two. A single byte is 8 bits, so you could save 8 different states of on or off and if you want to see if a specific bit is set, then the bitwise operators made life easy.
I’ve almost never needed them in Lua and other 4th generation languages. But we have the plugin if you need to do something that needs it. If you don’t know what it is, then you certainly are not using it. Which rules out scenario #1 above. I’m going to guess it’s #3 a false positive and this is a just ignore it situation.
Rob
Thx for the help and the details here Rob. Much appreciated!
Could you PM me any require statements from the app that is giving the false positive for the bit plugin? Are you using any third party code in your app?
Turned out the Dusk plugin requires the bit plugin in turn.
We’re also improving the warning to include the actual location of the require that’s triggering it.
A few daily builds back we enabled some checking to make sure if you tried to use a plugin but it’s not in the build.settings, we would issue you a warning that you need to do so.
-
It’s possible that you’re using the bit plugin but didn’t include it in build.settings.
-
Something you are using is using it and you didn’t include it in build.settings.
-
Something is triggering a “false-positive”. In which case you can ignore the warning.
Rob
Thx for the fast feedback.
I don’t even know what the bit plugin is
I will look if something is using this but the message appears in a relative new project, so normally it shouldn’t.
The bit plugin lets you do bitwise math operations like shifting bits left and right, ANDing and ORing numbers together. Lua doesn’t support byte and integer type numbers (everything is handled as a double float).
Back in the day, if you needed to save space when sending data over the network, we had to pack as much as we could into a byte or two. A single byte is 8 bits, so you could save 8 different states of on or off and if you want to see if a specific bit is set, then the bitwise operators made life easy.
I’ve almost never needed them in Lua and other 4th generation languages. But we have the plugin if you need to do something that needs it. If you don’t know what it is, then you certainly are not using it. Which rules out scenario #1 above. I’m going to guess it’s #3 a false positive and this is a just ignore it situation.
Rob
Thx for the help and the details here Rob. Much appreciated!
Could you PM me any require statements from the app that is giving the false positive for the bit plugin? Are you using any third party code in your app?
Turned out the Dusk plugin requires the bit plugin in turn.
We’re also improving the warning to include the actual location of the require that’s triggering it.