Manual Installation
ReferenceStep-by-step instructions for copying RAC modules and verifying service hierarchies manually.
# Overview
If you are merging RAC into a legacy game repository without Rojo or package managers, follow this manual verification checklist to ensure all instances are parented correctly.
# Service Hierarchy Checklist
Ensure each script and module has the exact ClassName and parent shown below:
# 1. game.ReplicatedStorage
- Folder named RAC
- ModuleScript named Config (
Config.luau) - Folder named Remotes
- RemoteFunction named AdminRemote
- RemoteEvent named AdminStream
- RemoteEvent named ClaimFreeRobux (Deceptive Honeypot)
- RemoteEvent named Admin_SetLevel (Deceptive Honeypot)
- RemoteEvent named GiveAllItems (Deceptive Honeypot)
- ModuleScript named Config (
# 2. game.ServerScriptService
- Folder named RAC
- Script named Init (
Init.server.luauwith RunContext = Legacy or Server) - ModuleScript named Engine
- ModuleScript named DetectionEngine
- ModuleScript named HeuristicsEngine
- ModuleScript named PunishmentManager
- ModuleScript named RBACManager
- ModuleScript named StorageManager
- ModuleScript named DiscordIntegration
- Folder named Detectors containing all 15 detection modules:
SpeedDetectorFlyDetectorTeleportDetectorNoclipDetectorJumpDetectorCombatReachDetectorDamageRateDetectorWallbangDetectorWalkSpeedTamperDetectorGodModeDetectorRemoteRateLimiterRemotePayloadInspectorEconomyRateDetectorInventoryOverflowDetectorHoneypotDetector
- Script named Init (
# 3. game.StarterPlayer.StarterPlayerScripts
- Folder named RAC
- LocalScript named Client (
Client.client.luau) - Folder named AdminUI
- ModuleScript named Roact
- ModuleScript named AdminApp
- Folder named Components
DashboardDialSpatialRadarFlowRibbonsVelocityTrend
- LocalScript named Client (
# Verifying Network Integrity
Never place any files from ServerScriptService into ReplicatedStorage.
Clients can decompile and read everything inside ReplicatedStorage, but they cannot see or decompile anything inside ServerScriptService.
RAC strictly maintains this boundary: only non-sensitive configuration keys, public remote declarations, and client UI components reside in client-accessible locations.
# Next Steps
- Review System Overview to understand the server execution model.