Open in the app to sign in, vote and reply

Suggestions · Considering

Making abusive modifier permissions more specific

· · 6 votes · 4 comments · marked considering by on 2026-11-13

I can't give the permission of modifier abusive to players mainly because of the loop modifier where people can do ;loopGiveAll(inf,0) to all people in the server and add unnecessary memory to the server and cause lag and annoyance especially if someone doesn't like items flooding in their inventory (until the task ends).

Unlike loop, other abusive modifiers is very unlikely to cause that kind of annoyance like spawn, join, delay, schedule and expire.

If you could at least add custom rate limiting to loop (e.g. the delay of each loop cannot be lower than 1 second unless if the role allows you to), i'd be happy.

Comments

·

I also tested ;loopGiveAll(inf,0) and then it made the server shut down because of the memory overload of up to 6GB when the loop command gets used on just a singular player which was effectively worse than the ;shutdown command but mods with these permissions can do that 'effective' ;shutdown without the rank needed for the real shutdown. Please add a custom rate limiting to the loop modifier unless the role bypasses the limit like only the owner role.

Team ·

Nice catch, ;loop is.. dare I say in reference to the season. Quite a SPOOKY modifier to deal with. I have seen a few abusive cases in which it is generally used, which thank you for letting us know that it can be used to shutdown the server as well! And this is also being taken into consideration but once again thank you for raising the severity of the general issue.

·

great points here ryan so many thanks for sharing. i've added the ;loopGiveAll(inf,0) to top priority bugs to fix, and i think it's a great idea to explore custom limits for cooldowns too. thanks for sharing 🙏 will post updates here soon

Team · · in reply to Roblox player

Yeah the inf bug seems to be back, which you should also consider the Nan value in this so the program doesn't bug out trying to identify it. 🐛
As I assume this is a super similar glitch to what that was.