It divides the integer by 100.0, which causes it to have a value from 0.0 to 1.0. It is expected to return a float.
Although it might be better if it returned an integer, it won’t make a difference in the workings of the blueprint. If it currently returns 0.15 instead of 1.0, it will also return 15 instead of 100 if I would change it to return an integer.
The fact that the result is divided by 100.0 doesn’t mean the weird bug is caused by the blueprint.
Edit: Ow, I missed the part that the max is supposedly 15. That is weird, because in the code it says the max is 100. I’ll fix it asap haha 
This does mean there is a mistake in the internal code commenting, which can also cause bugs to other developers.
In the AndroidMisc.h it says this:
As you can see, it says it returns 0 to 100, not 0 to 15.
Maybe it’s useful if Epic also knows about this so they can fix it.