NOTICE: FPS unlockers in Stuntwar

madvillayo

Server Mapper | Stunter of the Year 2017 - 2020
Head Admin
Effective immediately, crashes.asi and FPS unlock modifications are no longer allowed in the Stuntwar (/swar) minigame, excluding some exceptions (See below). This modification remains allowed in all other gamemodes.

FORBIDDEN MODIFICATIONS IN STUNTWAR:
- All cheats
- FPS Unlockers
- crashes.asi, FrameRateVigilante
- Pole removals or broken object memory cleos (e.g. memory<size>.cs, [memory512.cs]).

This policy was decided upon after an extensive investigation revealed that crashes.asi and FPS unlock modifications grant significant advantages over other players even when capped, including but not limited to:
• Skyscraper-height bunnyhops (scrollhops to be specific);
• More distance and height with ramps with the same fps and other variables (e.g. runup);
• Less roadbumps when radding;
• Easier time landing/sticking to precisions;
• Floatiness (i.e. change in gravity, granting more height/distance than standard);
• Pole removal.

In summary, crashes.asi and FPS unlock modifications remove the 14ms delay in between frames which alters handling, game physics and overall vehicle performance. Therefore, crashes.asi and other FPS unlockers are considered modding and not allowed in the Stuntwar (/swar) minigame. It remains permitted in all other modes unless otherwise stated.

Additional information can be found here.

Players who are found in violation of the above policy will be informed about this post and be told to remove the modifications. Players who fail to comply will be at risk of stat removal and/or disciplinary action of their account.

Due to the severity of the advantages of these modifications, a small number of stuntwars had their leaderboard reset. A global stuntwar-wide and stunt stat reset is being considered but unlikely at this time. Any alterations to this policy shall be posted in this thread.



EXCEPTIONS
Players may be granted exemption from this policy by @madvillayo if a) their computer is incapable of running GTA:SA above 30fps. If an exemption is granted to a player, they must keep their framerate capped at 60FPS in stuntwar to prevent significant advantages over other players.

YOU MUST CONTACT @madvillayo IF YOU SEEK AN EXEMPTION FROM THIS POLICY.

Note: Players must attempt alternatives to crashes.asi & FPS unlockers before seeking an exemption (e.g. noleaves, lower-graphics and draw distance modifications, etc).

Any questions about the new policy shall be directed to @madvillayo. Thanks!

-MV
 
Last edited:

pokles

Goldpot Hunter of the Year | 2021
VIP
In summary, crashes.asi and FPS unlock modifications remove the 14ms delay in between frames which alters handling, game physics and overall vehicle performance. Therefore, crashes.asi and other FPS unlockers are considered modding and not allowed in the Stuntwar (/swar) minigame. It remains permitted in all other modes unless otherwise stated.
Speaking of this, does this also mean SilentPatch is also disallowed? It also removes the delay
 

madvillayo

Server Mapper | Stunter of the Year 2017 - 2020
Head Admin
SilentPatch will be under review to confirm, thanks

EDIT: Silentpatch is not a forbidden modification as Silentpatch has been developed to prevent advantages in SA:MP specifically.

FYI: Singleplayer stunters: Silentpatch is considered modding in GTAStunting in Singleplayer.
 
Last edited:

madvillayo

Server Mapper | Stunter of the Year 2017 - 2020
Head Admin
UPDATE: Any memory<size>.cs cleo mods, e.g. memory512.cs, are not allowed in StuntWar or /Race because they give an advantage over other players by remembering broken objects. Alternatively, players may use LimitAdjuster.

Thanks @s0ulreaper!
 
Last edited:
Top