Any entered intensity over 100% should throw an error message

If you don't scale your intensity to 0-100 in the fixture editor, the number could be whatever you set the range to.

If you don't scale your intensity to 0-100 in the fixture editor, the number could be whatever you set the range to.

If people are using maximums of over 100, then it could be an option to enable/disable intensity values over 100.

never used intensity over 100.
Did you, and when?

In situations where I want to use an intensity parameter to control a DMX device with a non-intensity parameter, eg: animatronics via DMX where the functions are unknown - sometimes I want the raw value (255) to be what full is so I can test along the full dmx range, no need to run the address up from 0-255 or use @ // to post raw dmx to the command line.

Why do i want this for intensity? because it's easier to grab channel 101 @ full than specifying 101 Animation at Full, when all the fixture has is that one parameter. Also being able to group multiple functions into an MC channel and use the .0 channel to master the output of the channels.

Understood. Good samples.

ok, so if a fixture has 0-100 writen in the library, than a value over 100 should not be possible.
But if a fixture has some other values in the Lib or you run "simple" DMX in the Commandline than values over 100 should be aloud.

So it should be not forbidden at all, but need to consider the Fixture-Lib or dmx value. 

Valid, although I am of the opinion that ranges should be the determining factor. OP's original issue is just a keystroke problem at heart, I expect that sending a value to a light would return that value or the maximum of the available limit, whichever is lower. (eg: light is at 75, and I type @/150%, I still expect the light to end up at full, because the light can't turn on to 112.5%).