Floating point numbers that end in .0 cannot be added to blocks

[mybearworld]

Expected Behavior

It should be possible to create a pick random (1.0) to (10) block. (This makes the block output a floating point number instead of an integer.)

Screenshot from regular Scratch

Actual Behavior

Whenever you enter 1. or 1.0 into a block, it autocorrects to "1".

Steps to Reproduce

• Drag out any block that takes in a number.
• Try to enter "1.0".

Operating System and Browser

Windows 11 on MS Edge 128

[GrahamSH-LLK]

This is caused by the original scratch-blocks and modern Blockly implementations for decimals being very different- scratch-blocks has a custom rolled(?) regex implementation that simply checks for periods in the string. Blockly has a more robust approach that ends up stripping that "unneeded" decimal that VM relies on for the random behavior. I believe it happens here

Edit: this behavior was briefly fixed in #54 but was reverted