Is this against the rules?

Basically to stop exploiters from spamming nukes when a nuke is in progress the only way I thought I could do it properly would be to let the player buy the nuke and then check with an attribute if the nuke is currently in progress through the process receipt callback. If it’s in progress and a player bought the nuke then that means an exploiter prompted themselves so I ban that person. Could I get in trouble for not giving the exploiter what they purchased even though they exploited to try and get it?

Regular players won’t be prompted the nuke product by checking the attribute through the client-side to see if the nuke is in progress.

i mean if they’re purchasing the nukes then i don’t see why you can’t just let them buy another. if only one can happen at a time then create a queue system for them.

Because if the nuke is already happening and they buy it while its happening then it would cause bugs.

just create a table of bought nukes and when one finishes you can start another. or if you’re sure nobody can buy these during a nuke without exploiting, you can simply ignore the purchase

edit: as for “Is this against the rules?” you’re not discriminating so you can freely ban who you want

I’m pretty sure a queue system though would be OOP related and i’m garbage at OOP.

Why did you like the fact that I’m garbage at OOP

2 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.