This workaround is currently used to fix many many issues that devices have, allows us to optimize our games (instead of 5 NPC spawners that each have 20 max spawn limit, I want to place 1 and set it to 90 which is the intended AI limit now, to save memory and have one device talk to verse, not 5 which they also have to talk between themselves). I want to make a damage zone that covers the entire map, not place 3-4 to do the same thing, just take longer to do it.
The other issue is that we spent months designing complex engines that use this workaround, we tested on our own to ensure stability on all platforms, and now this will break them. We are not building mini-games, and we cant afford to spam more devices to workaround the artificial limits placed on devices in 1.0
If you want to roll this out, first fix those limits, because the only thing you are going to do now is break games, which is what you intended to avoid by introducing this.
Timers not being able to go beyond 60 minutes and mutator zones not possible to be the size of a 16x16 grid to cover large fall zones such as in my only up is horrible
Please allow up to 64 UI layers for HUD devices implementing this change. Due lack of Epic works on Verse UI (i.e. text_block manipulation) - we just prefer to use HUD devices that require plenty of layers.
I cant exaggerate how bad this will be for absolutely loads of the biggest maps. This will not only destroy entire genres of games and make them unplayable in a lot of cases, but it will kill creativity.
There is no upside to this that would make it an even remotely reasonable change to make.
Not being the devils advocate but I think clamping is fine as long as it’s reasonable. Unclampped values can, but not necessarily have to, lead to crashes. In that sense Epic Games should at least not roll out this change in a fast manner until they reevaluated ALL our requested min/max changes. For that matter I opened up a thread to collect feedback and values creators rely on or need.
The fact that they’re deciding to patch the workaround rather than fixing the core issue that people are working around in the first place is mind-boggling. Clearly many devices are capable of supporting much higher and much lower values, and if it’s something that’s consistently being used then it means it’s stable enough to be left alone.