Not sure what was causing this, but commenting on this again because I miraculously was able to finally publish with the addition of adding a contributor. Didn't change anything. Since I made this ticket, the user was also having issues publishing mods of his own without any contributors, but that seems to have been fixed too! Wish I could give more insight as to why this now works, just happy it does now.

Fair enough. I stick to your suggestion then, thanks!

Confirmed internally, this will not change. You can use alternative methods to obtain the result you expect :-)

I thought the point is to pave the way for the future, so backward compatibility should be secondary. Also to consider is that the "default" generators sampling floats from 0 to 1 in modern programming languages are also execluding 1: random.random() in Python, Math.random() in Java, Random.NextDouble() in C#, etc.

I am having the same issue, except I don't have a dell computer. I tried all above what they tried and nothing seems to work and I also tried changing ports on workbench and in blender to see if I can try a different port but still nothing. It doesnt seem like its detecting workbench at all.

The common use case of this method is for handling probabilities

Math.RandomFloat01() is not used only for that, and changing the behaviour after release has the ability to break many existing mods and scripts.
Use Math.RandomFloat(0, 1) instead to obtain the behaviour you mention

Still happes...

Hey @Geez, I discovered that the "CampaignMPChatEntity.et" tool within Reforger Tools, which is supposed to automatically generate the necessary managers for a scenario, isn't spawning automatically. So, this isn't a bug after all.

The bounds that get reset are the ones under the "world" entity in the hierarchy. They are under the Dimensions section and have Bound Mins, Bound Maxs, and Block Size. Editing the bounds here does nothing. In terms of files, the bounds are found in the default.layer file. You can modify them there, save them, and then open your terrain and the world bounds will be correct. But as soon as you save your terrain in World Editor again they are reverted and you have to modify default.layer again. It's an annoying process.

Needs attention

Plz fix the issue

I recommend closing this. I had this issue on one map. Other people aren't seeing it. Not sure what's going on. It would be really nice if there was a list of requirements for things to work correctly.