[PAID] Weed Studio Tornado — Synchronized Cinematic Tornado System

RedM Releases
, , , ,
1

exec-12f866b2-a3c8-45c5-993e-df6f61ff63c2
exec-12f866b2-a3c8-45c5-993e-df6f61ff63c21672×941 329 KB

Bring large-scale natural disasters to your RedM server with Weed Studio Tornado.

This standalone resource creates a server-synchronized tornado that moves dynamically across the map. Every connected player receives the same tornado position, route, weather state, map blip, and event status.

The tornado combines a permanent curved funnel with rotating debris, NPCs, cattle, and wagons. Nearby players, vehicles, objects, and ambient NPCs can be pulled into the vortex while heavy rain, powerful winds, dense smoke, and lightning transform the surrounding atmosphere.

Preview

YouTube Video

Features

  • Server-synchronized tornado for all connected players;

  • server-authoritative position, route, start, stop, and weather state;

  • automatic synchronization for players joining an active event;

  • random map-wide movement;

  • configurable routes between Blackwater, Strawberry, Valentine, Emerald Ranch, Rhodes, Saint Denis, and Armadillo;

  • permanent curved funnel visible from the ground to the cloud base;

  • rotating debris, NPCs, cattle, and wagons;

  • attraction physics for nearby players, NPCs, objects, and vehicles;

  • native RDR2 hurricane weather;

  • heavy rain, powerful winds, and dark storm clouds;

  • irregular global lightning;

  • visible lightning bolts inside the tornado funnel;

  • layered native smoke for close and long-distance visibility;

  • configurable RedM map blip and danger radius;

  • optional player invincibility for demonstrations;

  • ACE-protected administrator commands;

  • configurable command cooldown;

  • automatic cleanup after stopping or restarting the resource;

  • automatic fallback for unsupported particle effects and blips;

  • fully translatable player-facing messages through config.lua;

  • standalone operation with no framework or database required.

Multiplayer Synchronization

The server controls the authoritative tornado state and broadcasts it to every connected player.

Cinematic debris, cattle, wagons, smoke, and particles are generated locally for better performance, but they follow the same globally synchronized tornado position.

Players who connect while an event is already active automatically receive its current state.

Commands

  • /tornado_start — starts the global tornado in front of the administrator;

  • /tornado_here — starts it at the administrator’s current position;

  • /tornado_move — moves the active global tornado;

  • /tornado_npc 5 — adds demonstration NPCs;

  • /tornado_effects — toggles the synchronized storm effects;

  • /tornado_stop — stops the event for every player.

Commands require the weed.tornado.admin ACE permission by default.

Configuration

The editable config.lua includes settings for:

  • language and translations;

  • ACE permissions and command cooldown;

  • tornado size, height, and attraction radius;

  • movement speed and map destinations;

  • attraction, rotation, and lifting forces;

  • weather, rain, wind, and lightning;

  • funnel dimensions and colors;

  • smoke intensity and profiles;

  • NPC, cattle, wagon, and debris counts;

  • player attraction and demonstration immunity;

  • map blip appearance and danger radius;

  • entity limits and performance optimization.

English is included by default. All player-facing messages can be translated through Config.Locale.

Requirements

  • RedM server;

  • OneSync recommended;

  • chat resource recommended for notifications;

  • no framework required;

  • no database required;

  • no external dependencies.

Compatible with VORP, RSG, RedEM, and standalone servers because it does not depend on framework-specific functions.

Installation

Add the resource and ACE permission to server.cfg:

ensure weed_studio_tornado
add_ace group.admin weed.tornado.admin allow

Restart the resource and use:

/tornado_start

Escrow Information

  • client.lua — protected;

  • server.lua — protected;

  • config.lua — open and editable;

  • distributed through CFX Asset Escrow.

Purchase

Tebex Store

Support

For installation assistance, bug reports, and future updates:

Weed Studio Discord

Please include your RedM artifact version, complete console error, modified configuration, and a short video when reporting an issue.

Checklist

  • I have reviewed the latest version of the Releases rules.
  • I have included a detailed description of my work as described in the rules.
  • I have included a download link or a store link.
  • I have filled out the required information at the end of the topic.

Required Information

Information Details
Code is accessible No — core client and server code are protected through CFX Asset Escrow. config.lua remains fully accessible.
Subscription-based No — one-time purchase.
Lines (approximately) 1,580 lines across client.lua, server.lua, and config.lua.
Requirements RedM server. OneSync is recommended. The chat resource is recommended for notifications.
Framework dependencies None — standalone resource compatible with VORP, RSG, RedEM, and other RedM frameworks.
Database requirements None.
External dependencies None.
Support Yes — installation assistance, bug fixes, and product updates are provided through Weed Studio support.

Escrow Information

  • client.lua — protected;

  • server.lua — protected;

  • config.lua — open and editable;

  • all player-facing messages can be translated through Config.Locale;

  • distributed through CFX Asset Escrow.

1 Like