It would be easier to create a thread with what to keep locked ie player count/round amount ect thatd be the easy method for creators and epic
While I donāt disagree on that, we need to fix the min / max values on the devices as it would otherwise would still require the force overriding workflow which isnāt convenient at all. Iām fine with clamping as long as all values are reasonable, donāt hurt any creations, allow the max amount of creative use. However ALL values should be reevaluated at once, or Epic should roll out the changes per device they finished reevaluating and do not affect devices which they havenāt checked yet, because otherwise it will break many maps while only allowing fixed values for prioritized devices. That would be devastating for many of us. Vehicles for example donāt receive as much priority as as other things.
I agree they should do a device by device basis and post/share the old/new suggested limits and give people a few days to post if they have any objections. This would be controlled albeit would take time but i feel this would be a better approach and would involve creators opinions which i feel is something missing lately from any change
- HUD Message Device
- Damage Amplifier
should have more flexible settings with extended limits. These devices have too small ranges of settings, which is why developers forcibly ignore the maximum limit, especially when it comes to layers for HUD Message Device
Explosive Device
Property | Min | Expected Min | Max | Expected Max | Affects You Directly | Priority |
---|---|---|---|---|---|---|
Time Until Reset Allowed | 0.1 | 0.0 | 1.0 | Unlimited | YES | Major |
Use cases:
Working on a quick reflex map where user must do actions that become faster over time. The explosion is used to break builds and works completely fine with 0.0 reset delay. This is one of the core gameplay functionality of the map and we donāt have alternatives to make it work properly without needing absurdly complex setups or workarounds.
HUD Message Device
Property | Min | Expected Min | Max | Expected Max | Affects You Directly | Priority |
---|---|---|---|---|---|---|
Layer | 0 | 0 | 4 | Unlimited or min. 999 | YES | Critical |
TRACKER DEVICE
| Property | Min | Expected Min | Max | Expected Max | Affects You Directly | Priority |
| --- | --- | --- | --- | --- | --- | --- |
| Target Value 1 | 1 | 10K | Unlimited | YES | Critical |
USE CASES:
Possibility to create a persistent scoring system (rank, arena, etc.) [and easily resettable] without using Verse persistence or save point device (just duplicate the tracker to reset the value). The problem is that the maximum value is 10K, which is very limiting.
MINIMAP DEVICE
Property | Min | Expected Min | Max | Expected Max | Affects You Directly | Priority |
---|---|---|---|---|---|---|
Map Capture Box Size | 5 | 5 | 500 | Unlimited | YES | Critical |
Use cases:
For very large maps with the maximum value not all of the area is occupied, so the value must be increased in order to view the entire area on the minimap.
Movement Modulator
Property | Min | Expected Min | Max | Expected Max | Affects You Directly | Priority |
---|---|---|---|---|---|---|
Speed | 0.5 | 0.1 | 3.0 | Unlimited | YES | Critical |
Forward Impulse | 0.0 | 0.0 | 5000.0 | 100,000.0+ | YES | Critical |
Upward Impulse | 0.0 | 0.0 | 5000.0 | 100,000.0+ | YES | Critical |
Use cases:
For distance based games like Ramp Jump / Mega Ramps, where players upgrade their jump speed or distance as they play.
New thread is up by epic
Health of a boss class i want to set to a million
I had an admin panel which sets the health of an admin to 1 million.
Moreover things such as tracking minutes played that are needed such as time since we first spawned on the island by timer elapsing or tracker of distance travelled on TRACKER HUD.
Huge size mutator zone so i can detect players falling into it from any point of the obstacle course to respawn them back to the start in Only Up. Having this limit means i have to make new mutator zones, and the game runs perfectly fine on my mobile with the super extended mutator zone size.
Just set everything limited to 32-bit max value, If storing signed integers, this would range from -2,147,483,648 to 2,147,483,647, for all device platforms to be supported, and the equivalent for float values in 32-bits. But most of us wont max our devices or settings so wont even be performance-sucking.
The amount of hate towards my post is crazy, how about you focus on making your island work, instead of trying to find someone to blame.
GG WP
HUD Message Device
Property | Min | Expected Min | Max | Expected Max | Affects You Directly | Priority |
---|---|---|---|---|---|---|
Layer | 0 | 0 | 4 | Unlimited | YES | Major |
Use cases:
The HUD message device is still very useful for creating dynamic widgets, with editable text through Verse. The Layer option however removes the fun for this. Unlimiting this will create so many possibilities for dynamic UI. If thatās not possible, I would suggest at least 100 layers.
Volume devices
Property | Min | Expected Min | Max | Expected Max | Affects You Directly | Priority |
---|---|---|---|---|---|---|
Width/Depth/Height | 0.1 | 0.1 | 100 | 1000 or 50x scale | YES | Critical |
Use cases:
Volume devices width/depth/height can reach a max of 100 tiles. Combined with the 5x scale limit, itās 500 tiles. This is not enough for large maps, where you need a central unique volume that manages the whole map.
Map Controller
Property | Min | Expected Min | Max | Expected Max | Affects You Directly | Priority |
---|---|---|---|---|---|---|
Map Capture Box Size | 1 | 1 | 500 | 2500 | YES | Critical |
Use cases:
Same as volume devices. The current limitation (500 tiles) is NOT enough for bigger maps, where the only way to calculate a good mini map is through the copy/paste method.
Explosive Device
Property | Min | Expected Min | Max | Expected Max | Affects You Directly | Priority |
---|---|---|---|---|---|---|
Blast Radius | 1 | 1 | 10 | 70-100 | YES | Major |
Use cases:
The explosive device is really useful for destroying builds at runtime in FFA maps. Its current radius limit is a problem, though. 10 tiles is not enough to reset builds in the whole map.
Timer Device
Property | Min | Expected Min | Max | Expected Max | Affects You Directly | Priority |
---|---|---|---|---|---|---|
Duration | 1 | 1 | 60 minutes | 1440 minutes | YES | Minor |
Use cases:
The current timer duration (60 minutes) is not enough for some maps. Increasing it to 24 hours would help.
Damage Amplifier Powerup Device
Property | Min | Expected Min | Max | Expected Max | Affects You Directly | Priority |
---|---|---|---|---|---|---|
Damage Magnitude | 1x | 1x | 4x | 1000000x | YES | Critical |
Use cases:
4.0x is a non-sense limit. Creators shouldnāt even have a limit. But if thereās the need, at least bring it up to 100x, for proper damage upgrade systems in games like tycoons/roguelikes etc.