Copy and paste large numbers in settings bug *URGENT*

Summary

Basically, you can type any number, copy it, and then paste it into the engine, causing it to override the limits that Epic has set up for us.

For example, you can override the round limit, which is typically 100, by typing a much larger number (e.g., 100,000,000) into the search bar and then pasting it into the round limit options. The engine will accept the new value.

You can also modify other settings, like changing the respawn time from 1.0 to 0.0, by using the same method: type 0 anywhere, copy it, and then paste it into the respawn option.

I know it might sound ambiguous, but I believe it might break stuff and we can solve it.

Thank you so much for reading.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Island Settings

Steps to Reproduce

Type the desired value (e.g., a large number) in a text field or search bar.
Copy the typed value.
Navigate to the relevant setting or option in the engine (e.g., round limit or
respawn time).
Paste the copied value into the setting or option.

TO PASTE YOU CAN USE SHIFT + LEFT CLICK OR JUST RIGHT CLICK AND PASTE. Thats how we did it.

Expected Result

No re spawning and many more.

Observed Result

No re spawning and 1 million rounds

Platform(s)

windows

Island Code

6308-3702-2505

Upload an image

Additional Notes

We do not have this issue this is an issue that can be avoidable but can be exploited.

I think this is down to the user. This has many perks including the layers on the hud widgets and scale of certain devices ie explosive device or scale on actual device like mutator ect

People who set rounds past 100 to as you gave in your example 100k are crazy like why would you even wanna do that. This is a useful perk that is used in a controlled manner by professional creators so i understand what your saying but also there is a ton of positives if its used in the same way.

ps This isnt a bug this has always been the case and i believe the limitation is there due to 1.0

Do not fix this