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.

My new workaround

As for fixing it myself, is there any current method for checking if an AIAgent is allowed max LOD? I don't see one in AIAgent.c, so my current workaround is a looped WaitAndExecute that just reapplies DisableLOD constantly.

all the new mods ive tried making recently, i havent had issues uploading them. Just this one for some reason

@Geez Just wondering if there's been any movement on this.

New Upload, same issue!

Haven't been able to update my scenario mod due to this error out of the blue. My larger mods update fine, but the smaller scenario mod keeps failing to 403 with no explanation given... No servers running the scenario are able to boot up with previous version of the mod after update either.

other folks in the modding lounge have been having this problem also

yep this is currently right now as im posting this took me about 4-5 trys to update this time (i got lucky). My life has dwindled to desperately pressing publish, while the time before I have to go to work slowly gets closer... Will the mod update and server be stable for the rest of the day, the world may never know xD{F5565465}

On myside? No.

Was it crashing?

Update: After 5 - 6 trys (3 hours) it worked.

Hello.
Is this still an issue at the moment?

@NiiRoZz i did a workround for this issue. I created a new "InventoryStorageSlot"

Hello, this issue should be fixed since version 1.3.0.144 but mention of it was missing in changelogs.

@Geez - its not resolved. Please see edited post. Maybe Niirozz knows what happening here. Thanks

Update: You can set "ShowAllChildrens" on the ItemPreviewAttributes, but this will make thinks strange. The attachment with the Offset will now show double! And on the Deployment Screen, the offset will still not set.