ancestor-v2-cipikturbo

bycipik aja

Tolong bantu aku untuk ubah semua nama Ancestor V2 menjadi cipikturbo dan buat ui minize agar bisa di buka dan tutup

No preview

Comments (0)

No comments yet. Be the first!

System Requirements

Page 1 of 18

System Requirements Document

1. Introduction

This System Requirements Document (SRD) defines the requirements for cipikturbo, a client-side Roblox scripting tool delivered as an executor-loaded Lua script. cipikturbo (previously named "Ancestor V2") provides an in-game control GUI that lets a player modify their own character, teleport, manage property load/save slots, farm and manipulate trees, automate shop purchases, modify vehicles, and apply optional server/player moderation actions within a Lumber-Tycoon–style game.

Two explicit user directives drive this revision:

  1. Rename all "Ancestor V2" references to "cipikturbo".
  2. Add a UI minimize control so the interface can be opened and closed.

The requirements below preserve the full capability set recovered from the uploaded script source and the user's chat instruction, including the source's underlying iteration and data-handling behaviors.

Page 2 of 18

2. System Overview

cipikturbo is a single-user, client-executed control surface. It is loaded inside a Roblox session through a supported script executor, hooks into the game client's existing remotes, GUIs, and services, and then presents a tabbed GUI for configuration and automation.

Core characteristics:

  • Delivery shape: Executor-loaded Lua script (client-side), with a remote UI library and configuration stored to local files.
  • Branding: The product name, configuration files, slot-name files, CoreGui identifiers, and in-GUI labels use the name cipikturbo.
  • Control style: Tabbed GUI with sliders, toggles, buttons, dropdowns, keybinds, textboxes, and live label readouts.
  • State: A shared settings table persisted as a JSON configuration file, plus a per-account slot-name JSON file.
  • Extensibility hooks: Anti-kick namecall hooking, remote proxying, thread-context manipulation, and connection management through a Maid utility.

3. Functional Requirements

3.1 Branding & Naming

  • As a script user, I want every occurrence of the name "Ancestor V2" (and "Ancestor") renamed to cipikturbo across GUI titles, tabs, sections, config filenames, CoreGui screen identifiers, and file references, so that the product is consistently rebranded.
  • As a script user, I want the configuration file renamed from AncestorV2Configuration.cfg to a cipikturbo-branded equivalent, so that saved settings persist under the new name.
  • As a script user, I want the slot-names file renamed from AncestorSlotNames.cfg to a cipikturbo-branded equivalent, so that slot naming persists under the new name.
  • As a script user, I want the on-screen GUI screen object (CoreGui reference) renamed to a cipikturbo identifier, so that detection, toggling, and cleanup functions target the rebranded GUI.
Page 3 of 18

3.2 Script Initialization & Loading

  • As a script user, I want cipikturbo to detect the running executor at launch, so that executor-specific features behave correctly.
  • As a script user, I want cipikturbo to wait until the game is fully loaded and the onboarding GUI is confirmed loaded before initializing, so that startup does not fail on incomplete sessions.
  • As a script user, I want first-time-execution protection applied to god mode, so that the character is protected on the first run before I configure it.
  • As a script user, I want cipikturbo to load its shared Maid, settings tables, and connection registry on startup, so that all subsystems have consistent state.
  • As a script user, I want cipikturbo to notify me when a new version has updated my configuration with new default keys, so that I know my settings were migrated.
  • As a script user, I want cipikturbo to iterate every entry in the default settings table (for Index, Value in next, DefaultSettings do) and, wherever the loaded GUISettings lacks a key, backfill that key with the default value and rewrite the configuration file, so that configuration migration from an older version is automatic.
  • As a script user, I want cipikturbo to create a default settings record when the configuration file is missing, so that a first-run session always has a complete settings table.
  • As a script user, I want cipikturbo to create default slot-name records (Slots 1–6) keyed by my player identifier when no slot-name file exists, so that slot naming always has a baseline.
  • As a script user, I want cipikturbo to detect a corrupted configuration, delete it, rewrite defaults, and notify me that a power-loss-safe fallback occurred, so that a bad file cannot break startup.

3.3 UI Shell, Minimize & Tabs

  • As a script user, I want a minimize control that collapses the cipikturbo UI into a small restorable state and lets me open it again, so that I can hide the interface without unloading the script and bring it back on demand.
  • As a script user, I want the minimized state to be a small, draggable rail that keeps the cipikturbo wordmark and live-state indicator visible, so that I can still see the tool is running while it is out of the way.
  • As a script user, I want the minimize control's glyph to reflect the next action (collapse vs. expand), so that the control always shows what it will do next.
  • As a script user, I want the minimize/restore transition to be instant and mechanical, so that the panel gets out of my way without a distracting animation.
  • As a script user, I want a keybind to toggle UI visibility, so that I can show/hide the interface with a single key.
  • As a script user, I want a "Close GUI" control that fully destroys the cipikturbo interface, so that I can unload the product and restore the original game state.
  • As a script user, I want tabbed navigation (Client Options, Game Options, Troll Options, Property Options, Tree Options, Shop Options, Axe Options, Vehicle Options, Settings), so that related controls are grouped and reachable.
  • As a script user, I want each tab to contain sections and sub-sections with titles, so that large control sets remain organized.
  • As a script user, I want a GUI Tips toggle that shows/hides help sections across the interface, so that I can learn controls without permanent clutter.
  • As a script user, I want cleanup on GUI destruction to disconnect all tracked connections, reset fly state, and remove injected effects (Stats/GUI screens, head light), so that closing the UI leaves no residual hooks.
  • As a script user, I want global settings and player-list button changes to re-apply the theme automatically, so that newly opened windows stay visually consistent.
Page 4 of 18

3.4 Humanoid Options

  • As a script user, I want a Walk Speed slider, so that I can change my character's walk speed.
  • As a script user, I want a Sprint Speed slider combined with a hold key, so that I can temporarily boost my speed while sprinting.
  • As a script user, I want a Jump Power slider, so that I can change my character's jump power.
  • As a script user, I want a Hip Height slider, so that I can change my character's hip height.
  • As a script user, I want a Fly Speed slider, so that I can set the speed used while flying.
  • As a script user, I want a keybind for Fly, so that I can toggle flying with my chosen key.
  • As a script user, I want a keybind for Sprint (hold), so that I can choose which key triggers sprinting.
  • As a script user, I want a keybind for Noclip, so that I can toggle collision off with my chosen key.
  • As a script user, I want a keybind for Key-TP (teleport to mouse), so that I can blink to the cursor within a valid range.
  • As a script user, I want an Infinite Jump toggle, so that I can jump repeatedly without landing.
  • As a script user, I want a Light toggle that places a point light on my character's head, so that I can illuminate dark areas.
  • As a script user, I want an Invincibility/Invisibility toggle, so that I can toggle character god mode on or off.
  • As a script user, I want an Anti-AFK toggle, so that I am not idled out by the game.
  • As a script user, I want a Safe Suicide button, so that I can reset my character while keeping my axes.
  • As a script user, I want a BTools button, so that I can spawn building tools to modify the environment.

3.5 Camera Options

  • As a script user, I want a FOV slider, so that I can change the camera field of view.
  • As a script user, I want a Reset FOV button, so that I can return the camera FOV to the default value.

3.6 Teleportation Options

  • As a script user, I want a "Teleport to Location" dropdown with named map locations, so that I can jump to predefined points of interest.
  • As a script user, I want a "Teleport to Player" dropdown, so that I can teleport near a selected player.
  • As a script user, I want a "Teleport to Player's Base" dropdown, so that I can teleport to another player's property.
Page 5 of 18

3.7 Miscellaneous / Session Options

  • As a script user, I want a "Re-Execute Upon Rejoin" toggle, so that cipikturbo reloads itself after rejoining.
  • As a script user, I want a "Rejoin Game" button, so that I can reconnect to the current server.
  • As a script user, I want a notice if re-execution is unsupported on my executor, so that I understand why the feature is unavailable.

3.8 Graphical Options

  • As a script user, I want an Always Day toggle, so that I can force daytime in-game.
  • As a script user, I want an Always Night toggle, so that I can force nighttime in-game (mutually exclusive with Always Day).
  • As a script user, I want a No Fog toggle, so that I can remove environmental fog.
  • As a script user, I want a Spook toggle, so that I can enable the Halloween-style spook lighting mode.
  • As a script user, I want a Global Shadows toggle, so that I can control global environmental shadows.
  • As a script user, I want a Better Graphics toggle, so that I can apply enhanced lighting effects (blur, color correction, sun rays).
  • As a script user, I want a Brightness slider, so that I can adjust the game's brightness.

3.9 Water Options

  • As a script user, I want a Water Walk toggle, so that I can walk on water surfaces.
  • As a script user, I want a Water Float toggle, so that I can toggle whether my character floats in water.
  • As a script user, I want a Water Godmode toggle, so that water damage cannot kill my character.

3.10 Dragging Options

  • As a script user, I want an X-Axis rotate slider, so that I can set my object-rotation speed on the X axis.
  • As a script user, I want a Y-Axis rotate slider, so that I can set my object-rotation speed on the Y axis.
  • As a script user, I want a Fast Rotate toggle, so that I can rotate dragged objects much faster.
  • As a script user, I want a Hard Dragger toggle, so that I can more easily pick up and move heavy objects.
Page 6 of 18

3.11 Troll / Moderation Options

  • As a script user, I want a Moderation Action dropdown (Kill, Hard Kill, Bring, Fling), so that I can pick which action to perform on a target.
  • As a script user, I want a Moderation Type dropdown (Vehicle, Axe), so that I can choose the method used to apply the action.
  • As a script user, I want a target-player dropdown, so that I can select the player to act upon.
  • As a script user, I want a "Perform Action" button, so that I can execute the selected action against the selected player.
  • As a script user, I want validation messages when prerequisites are missing (no axe, no vehicle, target left, self-target, not in driver seat, target seated), so that misuse is prevented with clear feedback.

3.12 Server Options

  • As a script user, I want a "Stop Players From Loading" toggle, so that I can block other players from loading large bases.
  • As a script user, I want a "Force Whitelist" toggle, so that I can interact with objects I am not whitelisted for.
  • As a script user, I want a "Close All Stores That Have Doors" toggle, so that store doors are kept closed against other players.
  • As a script user, I want a "Fire All Scoobis" button, so that I can trigger every Scoobis I own or am whitelisted for.
  • As a script user, I want a "Fire All Bold & Brash" button, so that I can trigger every Bold & Brash painting I own or am whitelisted for.

3.13 Property Load / Save Options

  • As a script user, I want a "Slot To Load" slider, so that I can select which save slot to operate on.
  • As a script user, I want a "Load Selected Slot" button, so that I can load the chosen save slot.
  • As a script user, I want an "Unload Selected Slot" button, so that I can unload the currently loaded slot.
  • As a script user, I want a "Delete Selected Slot" button with an irreversible-action confirmation, so that I can safely delete a slot only after confirming.
  • As a script user, I want a "Save Selected Slot" button, so that I can save my current loaded slot.
  • As a script user, I want the loaded-slot slider header to display the custom slot name when one is set, so that I can identify slots by name.

3.14 Property Information

  • As a script user, I want a player dropdown in Property Information, so that I can inspect another player's save data.
  • As a script user, I want per-slot datasize labels (Slots 1–6), so that I can see how much data each slot holds for the selected player.
  • As a script user, I want cipikturbo to iterate the returned metadata (for Index, Data in next over the slot metadata list) and extract each slot's NumKeys value into an info collection, so that the per-slot datasize labels are populated accurately.
Page 7 of 18

3.15 Property Housing Options

  • As a script user, I want a "Free Land" button, so that I can acquire a free land plot.
  • As a script user, I want a "Max Land" button, so that I can expand my property to its maximum size for free.
  • As a script user, I want a "Sell Land Signs" button, so that I can sell all my property signs.
  • As a script user, I want an "Expand Land" button, so that I can manually expand my land as desired.

3.16 Tree Teleportation Options

  • As a script user, I want a "Bring Tree target position" dropdown (Current Position, Spawn, To Property, Sell Point), so that I can choose where brought trees land.
  • As a script user, I want a "Teleport Player With Tree" toggle, so that I can control whether I am teleported back after bringing a tree.

3.17 Bring Tree Options

  • As a script user, I want a tree-type dropdown (Generic, GoldSwampy, CaveCrawler, Cherry, Frost, Volcano, Oak, Walnut, Birch, SnowGlow, Fir, Pine, GreenSwampy, Koa, Palm, Spooky, SpookyNeon, LoneCave), so that I can select which tree to bring.
  • As a script user, I want a tree-size dropdown (Largest, Smallest), so that I can select the target tree by size.
  • As a script user, I want a Quantity slider, so that I can bring a chosen number of trees at once.
  • As a script user, I want an "Autofarm Selected Tree" toggle, so that the chosen tree is automatically brought and modded in a loop.
  • As a script user, I want a "Bring Tree" button with a dynamic header reflecting type/quantity, so that I can start the bring operation with clear confirmation of what will be brought.
  • As a script user, I want an "Abort" button for the tree operation, so that I can stop a bring tree action in progress.
  • As a script user, I want prerequisite notices (needs correct axe, needs property for "To Property", no matching trees in server), so that I understand why an action cannot proceed.

3.18 Mod Wood Options

  • As a script user, I want a "Sell Plank After Mod" toggle, so that modded planks are automatically sold.
  • As a script user, I want a "Mod Wood" button, so that I can mod the selected tree through the sawmill.
Page 8 of 18

3.19 Mod Sawmill Options

  • As a script user, I want a "Mod Sawmill" button, so that I can configure a sawmill to mill logs faster.
  • As a script user, I want a "Maximum Size Sawmill" button, so that I can set the sawmill output to its maximum size.
  • As a script user, I want a "Minimum Size Sawmill" button, so that I can set the sawmill output to its minimum size.

3.20 Shop / Autobuy Options

  • As a script user, I want an item dropdown listing store items with prices, so that I can select what to auto-buy.
  • As a script user, I want an Amount slider for autobuy, so that I can specify how many to purchase.
  • As a script user, I want an "Automatically Unbox Items After Purchase" toggle, so that purchased boxes are opened automatically (structures excluded).
  • As a script user, I want a dynamic "Purchase" button whose header reflects quantity and item, so that I can start the autobuy with clear confirmation.
  • As a script user, I want an "Abort" button for autobuy, so that I can stop a purchase run in progress.
  • As a script user, I want an affordability notice showing the required money amount, so that I know when I cannot afford a purchase.

3.21 Blueprint Options

  • As a script user, I want a "Purchase All Blueprints" button, so that I can auto-buy every blueprint I do not already own.

3.22 NPC Options

  • As a script user, I want a "Faster Dialogue" toggle, so that I can interact with NPCs more quickly.
  • As a script user, I want a "Fix NPC's Range" toggle, so that dialogue prompts appear more quickly/reliably near cashiers.
Page 9 of 18

3.23 Axe Options

  • As a script user, I want an Axe Range slider, so that I can modify the axe cutting range.
  • As a script user, I want an "Activate Axe Range" toggle, so that my axe range modification is applied.
  • As a script user, I want a "No Axe Cooldown" toggle, so that the client-side axe swing cooldown is removed.
  • As a script user, I want a "Tomahawk Axe Fling" toggle, so that thrown axes fling players/objects at the mouse position.
  • As a script user, I want an "Auto Chop" toggle, so that nearby trees are chopped automatically.
  • As a script user, I want an "Instant Drop Axes (Requires Respawn)" toggle, so that dropping all axes respawns my character.
  • As a script user, I want a "Drop All Axes" button, so that I can drop every axe I carry.
  • As a script user, I want "Current Axe Information" labels (name, range, cooldown), so that I can see my equipped axe's live stats.

3.24 Vehicle Options

  • As a script user, I want a Vehicle Speed slider, so that I can modify my vehicle's speed.
  • As a script user, I want a Vehicle Pitch slider, so that I can modify my vehicle's pitch.
  • As a script user, I want an "Activate Vehicle Modifications" toggle, so that my vehicle modifications take effect.
  • As a script user, I want a "Sit In Any Vehicle" toggle, so that I can seat in any vehicle.
  • As a script user, I want a vehicle-colour dropdown, so that I can choose the colour of the vehicle to spawn.
  • As a script user, I want an "Auto Stop On Pink" toggle, so that the vehicle spawner stops if a pink vehicle spawns.
  • As a script user, I want a "Delete Vehicle Spawn Spot Once Completed" toggle, so that the spawn pad is removed after spawning.
  • As a script user, I want a "Spawn Vehicle" button, so that I can spawn the selected vehicle into a chosen spot.
Page 10 of 18

3.25 Settings & Configuration

  • As a script user, I want Credits labels, so that authorship is shown.
  • As a script user, I want an "Execute Toads GUI" button, so that I can launch the Toads GUI.
  • As a script user, I want an "Execute Butter GUI" button with a warning notice, so that I am informed of the skidded nature of Butter before use.
  • As a script user, I want GUI Information labels (Game Version, Executor, Ping, CPU, Current Loaded Slot), so that I can monitor session status.
  • As a script user, I want a "Save Configuration" button, so that I can persist my settings.
  • As a script user, I want a "Delete Configuration" button, so that I can remove my saved settings.
  • As a script user, I want an "Autosave Configuration" toggle, so that settings save automatically as the UI updates.
  • As a script user, I want six "Slot N Name" textboxes, so that I can rename each save slot.
  • As a script user, I want a "Save Slot Names" button, so that I can persist custom slot names for my account.
  • As a script user, I want a "Toggle UI" keybind, so that I can show/hide the interface.
  • As a script user, I want a "Dropdown Name Settings" dropdown (Both, DisplayName, UserName), so that I can control how player names are displayed.
  • As a script user, I want a "Close GUI" button in Settings, so that I can fully unload cipikturbo.

3.26 Theme / Dark Mode

  • As a script user, I want a dark theme applied by default, so that the GUI is readable over the game.
  • As a script user, I want a light theme option, so that I can switch the interface palette on demand.
  • As a script user, I want the theme to restyle all major game GUIs it touches (menu, load/save, property purchasing, notices, money GUI, donate GUI, settings, changelog, credits, onboarding, chat, item dragging, item info, interaction, structure dragging, wire dragging, overwrite confirm, and blueprints), so that the interface is visually consistent with cipikturbo.
  • As a script user, I want cipikturbo to iterate each themed window's descendants (for _, v in next, <gui>:GetDescendants() do) and recolor frames, text labels, and buttons to the active theme, so that every touched window is uniformly restyled.
  • As a script user, I want rounded corners applied to themed frames, labels, and buttons, so that the interface matches the cipikturbo visual style.
  • As a script user, I want tick marks converted to a checkmark glyph, so that toggled states read clearly.
  • As a script user, I want keycap labels normalized (black text at 14 px, non-scaled) when the theme is applied, so that key hints remain legible.
Page 11 of 18

3.27 Clock / Session HUD

  • As a script user, I want an FPS readout, so that I can monitor performance.
  • As a script user, I want a time readout, so that I can see the current time.
  • As a script user, I want a date readout with an ordinal day suffix, so that I can see the current date.
  • As a script user, I want a "You Can Load / You Cannot Load" indicator tied to load eligibility, so that I know when loading is permitted.

3.28 Internal System APIs

  • As a script user, I want an api that enumerates loaded trees, so that tree features can find targets.
  • As a script user, I want an api that identifies the axe with the best damage for the selected tree type, so that auto-chop and bring-tree use the optimal axe.
  • As a script user, I want an api that applies axe range and swing-cooldown modifications to the equipped tool, so that axe stats update live.
  • As a script user, I want an api that teleports my character or its seated vehicle to a CFrame, so that all teleport features work uniformly.
  • As a script user, I want an api that toggles client-side fly with body velocity/gyro and directional steering, so that fly mode responds to WASD.
  • As a script user, I want an api that applies and reverts character god mode, so that invincibility can be toggled safely.
  • As a script user, I want an api that manages dragged objects and network ownership, so that moving objects is reliable across the network.
  • As a script user, I want an api that brings a model to a target position with repeated drag confirmation, so that objects move without desync.
  • As a script user, I want an api that hovers/highlights a selected object, so that selection is visually confirmed.
  • As a script user, I want an anti-kick namecall hook that blocks Kick, Ban, DamageHumanoid (when water god mode is on), and rewrites the RunSounds pitch when vehicle modifications are on, so that the script resists common server countermeasures.
  • As a script user, I want a thread-context setter, so that the script can elevate context for privileged operations when the executor supports it.
  • As a script user, I want a transparent-function cache for privilege checks, so that repeated permission checks do not stall the UI.
  • As a script user, I want a connection manager (Maid-style) that tracks and disconnects named connections, so that toggles clean up after themselves.
  • As a script user, I want a startup loop that calls the tree-enumeration API every few seconds while the script is loaded, so that tree targets remain fresh.
Page 12 of 18

3.29 Source Iteration & Data-Handling Behaviors

  • As a script user, I want cipikturbo to iterate the merged list of my backpack children and character children (for Index, Value in next over the merged table) to collect my axes, so that axe-dependent features always see every tool I hold or carry.
  • As a script user, I want a table-merge utility that iterates a source table (for Index, Value in next, Tbl do) and appends each value into a destination table, so that backpack and character contents can be combined into one list.
  • As a script user, I want the object-tracking system to iterate its per-type categories (for Index, DataType in next, PlayerObjects do) and log each category's count, so that the tracked object tallies (Tool, Structure, Loose Item, Furniture, Vehicle, Vehicle Spot, Wire, Gift) are observable for diagnostics.
  • As a script user, I want the tracked-object table (PlayerObjects) to be re-initialized with empty categories for Tool, Structure, Loose Item, Furniture, Vehicle, Vehicle Spot, Wire, and Gift whenever the current save slot changes, so that stale object references are cleared whenever I switch slots.
  • As a script user, I want cipikturbo to iterate the collected descendants of a structure model (for _, Object in next over that model) and classify each object by its type before entering purchase mode, so that load/plot previews accurately group the objects in a base.
  • As a script user, I want cipikturbo to iterate a target property's children (for _, Property in pairs(Property:GetChildren()) do) and test horizontal and vertical proximity, so that "player close to property" checks return a correct boolean.
  • As a script user, I want cipikturbo to iterate the current default settings table and rewrite the configuration file whenever any default key was missing, so that the on-disk configuration matches the running version after migration.
  • As a script user, I want cipikturbo to iterate over a slot-name table and merge it back into the on-disk slot-name file, so that renamed slots persist per account.

4. User Personas

Primary Persona — The cipikturbo Script User (Lumber-Tycoon Player) An individual player who loads cipikturbo through a supported executor in a Lumber-Tycoon–style Roblox game. They use the GUI to customize their own character (speed, fly, noclip, god mode), teleport around the map, manage property load/save slots, manipulate trees and sawmills, auto-buy shop items, and modify vehicles. They also optionally use troll/server tools and moderation actions against other players in the same server.

External recipients (not active product personas): other players in the server, who receive the effects of moderation actions, forced privileges, or affected properties but never operate the cipikturbo interface.

5. Core User Flows

Page 13 of 18

5.1 Initialization Flow

  1. User runs cipikturbo through a supported executor.
  2. The script detects the executor and waits for the game and onboarding GUI to load.
  3. The script loads its Maid utility, settings tables, and connection registry.
  4. The script loads or creates the configuration file and the slot-names file, recovering to defaults if the config is corrupted.
  5. The script iterates the default settings table and backfills any missing keys into the loaded settings, then rewrites the configuration file if changed.
  6. The remote UI library is fetched and the cipikturbo GUI is built with the dark theme applied.
  7. The script marks itself loaded and begins the periodic tree-loading loop.

5.2 Character Modification Flow

  1. User opens the Client Options tab.
  2. User adjusts Walk Speed, Sprint Speed, Jump Power, Hip Height, or Fly Speed sliders.
  3. User binds keys for Fly, Sprint, Noclip, and Key-TP.
  4. User toggles Infinite Jump, Light, Invincibility/Invisibility, or Anti-AFK as needed.
  5. Character behavior updates live; changes are saved according to autosave settings.

5.3 Tree Farming Flow

  1. User selects a target tree type and size, and sets the bring quantity and destination.
  2. User presses "Bring Tree"; the script chops and drags a tree to the chosen position.
  3. Optional: user enables "Autofarm Selected Tree" to loop bring + mod.
  4. User selects a sawmill and presses "Mod Wood" to mill the tree (optionally selling the plank after milling).
  5. User can abort the operation at any time.
Page 14 of 18

5.4 Property Slot Management Flow

  1. User selects a slot via the "Slot To Load" slider.
  2. User loads, unloads, saves, or deletes the slot; delete requires an irreversible-action confirmation.
  3. User can inspect other players' per-slot datasizes via Property Information, which iterates each slot's metadata to extract the datasize counts.
  4. User can acquire Free Land, Max Land, or Sell Land Signs as needed.
  5. Whenever the current save slot changes, the tracked-object table is cleared and reinitialized with empty categories.

5.5 Shop Automation Flow

  1. User picks an item from the shop dropdown and sets the amount.
  2. User optionally enables "Automatically Unbox Items After Purchase".
  3. User presses "Purchase"; the script checks affordability and finds the store item and nearest cashier.
  4. The script moves the item to the cashier, completes purchase, returns it, and optionally unboxes it.
  5. User can abort; the script notifies the required money if unaffordable.

5.6 Moderation Flow (Optional)

  1. User selects a target player, a moderation action (Kill, Hard Kill, Bring, Fling), and a moderation type (Vehicle or Axe).
  2. User presses "Perform Action".
  3. The script validates prerequisites (axe/vehicle presence, seat position, target still in-game, not self).
  4. The script executes the action and cleans up privileges afterwards.

5.7 Session & Configuration Flow

  1. User toggles "Re-Execute Upon Rejoin" if desired and can press "Rejoin Game".
  2. User opens Settings to review Game Version, Executor, Ping, CPU, and Current Loaded Slot.
  3. User saves or deletes the configuration, renames slots, and saves slot names (merged back into the per-account file).
  4. User can execute the Toads GUI, or trigger the Butter warning.
  5. User can toggle UI visibility, minimize the interface to a small restorable state, or close the GUI entirely.
Page 15 of 18

6. Visuals, Colors and Theme

The uploaded source defines an explicit two-mode palette, which cipikturbo preserves:

  • Dark mode (default): Primary background RGB(15, 15, 15), primary foreground/text RGB(255, 255, 255), secondary surface RGB(15, 15, 15).
  • Light mode: Background RGB(255, 255, 255), text RGB(0, 0, 0), secondary surface RGB(220, 220, 220).
  • Emphasis / CTA: The donate amount label uses a green accent RGB(0, 155, 0).
  • Corner styling: Frames, labels, and buttons receive UICorner with a radius of ~5–6 px.
  • Typography: Labels and buttons use a semibold gothic-style font at ~14 px; keycap labels are forced to black text at 14 px.
  • Depth: A dedicated DropShadow element is recolored per theme (black for shadows in dark mode).
  • Status styling: Toggle tick marks render as a checkmark glyph.
  • HUD styling: The clock/FPS status panel uses rounded, near-black cards anchored to the bottom-right, with a "You Can / Cannot Load" indicator card on the left.

7. Signature Design Concept

The signature concept is a compact dark command console layered over a bright game world. Near-black rounded cards, terse labeled controls, and drop shadows keep the tool legible without obscuring the scene. Every window cipikturbo touches — including the game's own menu, load/save, purchasing, notice, and dialogue GUIs — is re-skinned to the same rounded dark palette so the experience reads as one coherent product. The newly requested minimize control reinforces this concept by letting the whole console collapse to a small, unobtrusive restorable chip.

Page 16 of 18

8. Interaction Model & Motion Direction

  • Controls: Sliders (with live value display), toggles, buttons, dropdowns, keybinds, textboxes, and read-only labels.
  • Navigation: Vertical tab rail plus sections and sub-sections; per-tab scrolling.
  • Feedback: SendUserNotice style toasts for confirmations, errors, and warnings (e.g., corrupted config, missing prerequisites, saved/deleted configuration).
  • Confirmation pattern: Destructive or irreversible actions (slot deletion, property duplication) use an inline confirmation prompt.
  • Motion: Restrained — no large transitions. The dominant motion is the minimize/restore of the whole UI shell; otherwise motion is limited to status updates (FPS, ping, CPU, slot, axe stats) and theme restyles applied when windows open.
  • Cleanup behavior: Closing the GUI disconnects tracked connections, resets fly/fling state, and removes injected effects, restoring the game's original presentation.

9. Non-Functional Requirements

  • Executor compatibility: Supported on Synapse X, Fluxus, Krnl, and Valyse; features that depend on specific executors (thread context, re-execution on rejoin, Anti-AFK) must degrade gracefully with a clear notice.
  • Resilience: Must block server-side Kick, Ban, and (when water god mode is enabled) DamageHumanoid, and must exit cleanly when the GUI is destroyed.
  • Configuration persistence: Settings saved to a JSON .cfg file; corrupted config must be detected and reverted to defaults with a user notice; missing keys must be backfilled with defaults (via iterating the default settings table) and the file rewritten.
  • Per-account persistence: Slot names saved per Roblox account; a default slot-name record created for first-time accounts; renamed slots merged back into the per-account file.
  • Performance: Minimize per-frame overhead; the loader uses throttled loops; autosave writes are bypassed from user notices when triggered automatically.
  • Reliability: Object-moving operations wait on network ownership and re-issue drag requests until the target moves; operations are abortable; tracked object tables reset cleanly on slot change.
  • Safety: Operations blocked during save/load and property duplication; self-targeting moderation prevented; seated-state checks enforced.
  • Localization of notices: Notices use clear, terse English phrasing with explicit causes (e.g., "No Data Found For Slot N.").
  • Branding integrity: After rebranding, no "Ancestor V2" text may remain in user-visible strings, file names, or CoreGui identifiers.
Page 17 of 18

10. Tech Stack

cipikturbo is a client-side executor script. The layers it actually requires are:

  • Language / runtime: Lua (Luau) executed inside the Roblox client via a script executor.
  • Remote library source: A UI library and shared Maid utility fetched over HTTPS from a remote repository (game:HttpGetAsync), then initialized to build tabs and sections.
  • Executor environment APIs: identifyexecutor, loadstring, getgenv, getconnections, setconstant, getupvalues/setupvalue, getupvalue, hookmetamethod/getnamecallmethod/setnamecallmethod, setthreadcontext / syn.set_thread_identity, syn.queue_on_teleport, firetouchinterest, isnetworkowner, readfile/writefile/isfile/delfile.
  • Roblox services used: Players, TeleportService, UserInputService, CoreGui, StarterGui, Lighting, RunService, ReplicatedStorage, HttpService, Stats.PerformanceStats, Workspace/Terrain.
  • Client-server bridge: RemoteEvents and RemoteFunctions of the host game (LoadSaveRequests, PropertyPurchasing, Interaction, NPCDialog, PlaceStructure, Notices, TestPing).
  • Data storage: Local JSON configuration files via HttpService:JSONEncode/JSONDecode written through the executor's file APIs.
  • UI rendering: Roblox ScreenGui/Frame/TextLabel/TextButton/ImageLabel/ScrollingFrame instances with UICorner, plus injected lighting effects (Blur, ColorCorrection, SunRays, PointLight).

No backend server, database, authentication product, or admin panel is required by the accepted delivery shape.

11. Assumptions and Constraints

  • cipikturbo runs only inside a supported Roblox script executor; it cannot run in unsupported environments.
  • Some features are executor-gated (re-execution on rejoin requires Synapse X; thread-context elevation and Anti-AFK are blocked on Krnl).
  • Slot deletion and property duplication are irreversible from the user's perspective and require explicit confirmation.
  • Certain operations are blocked during save/load or property duplication to prevent data corruption.
  • Object-moving features depend on server network ownership and can fail under high ping; the tool warns when duplication is unreliable above 500 ms ping.
  • The script hooks namecall methods; this may conflict with other hooked scripts loaded into the same session.
  • The user explicitly requires (a) the full rename from "Ancestor V2" to cipikturbo and (b) a UI minimize control; both are mandatory.
  • The uploaded source is described by its own startup notice as a public release with known bugs; requirements assume ongoing maintenance, not a bug-free baseline.
  • Data files (configuration and slot names) live on the local machine and are tied to the executing account.
  • Table contents such as the merged backpack/character tool list and the tracked-object categories are iterated at runtime; their exact contents depend on the live game session.
Page 18 of 18

12. Glossary

  • cipikturbo: The rebranded name of this executor script (formerly "Ancestor V2").
  • Executor: A third-party tool that allows running custom Lua in a Roblox client (e.g., Synapse X, Fluxus, Krnl, Valyse).
  • Maid: A utility object that tracks and cleans up connections, threads, and timers.
  • GUISettings: The shared in-memory settings table persisted to the configuration file.
  • DefaultSettings: The default settings table iterated at startup to backfill missing keys.
  • PlayerObjects: The tracked-object table keyed by category (Tool, Structure, Loose Item, Furniture, Vehicle, Vehicle Spot, Wire, Gift), reset on slot change.
  • Slot: One of six save slots for a player's property/data.
  • Datasize: The number of keys stored in a save slot, used to gauge how loaded a base is.
  • Whitelist: Permission granted by a player allowing cipikturbo to interact with that player's property or objects.
  • Bring Tree: The operation that locates, chops, and drags a selected tree to a chosen destination.
  • Mod Wood / Mod Sawmill: Adjusting wood sections or sawmill settings to process/sell logs.
  • Autobuy: Automated shop purchasing of a selected item, optionally unboxing after purchase.
  • Moderation Action: A troll action (Kill, Hard Kill, Bring, Fling) applied to a target player.
  • Notice: An in-game toast message produced by cipikturbo for feedback and errors.
  • Dark Mode / Light Mode: The two theme palettes available for the cipikturbo interface and touched game GUIs.
  • Anti-Kick: A namecall hook that blocks Kick/Ban-related server calls and adjusts specific outgoing remotes.
  • Minimize (requested): A control that collapses the cipikturbo GUI into a small restorable state, allowing the interface to be closed and reopened without unloading the script.

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

Landing: Load script via executor
Client Options: Configure walk speed slider
Client Options: Bind fly and noclip keys
Client Options: Toggle infinite jump and god mode
Game Options: Select teleport destination
Game Options: Toggle rejoin re-execution
Property Options: Select slot to load
Property Options: Load selected slot
Property Options: Inspect player slot datasizes
Property Options: Click free land
Tree Options: Select tree type and size
Tree Options: Click bring tree
Tree Options: Toggle autofarm selected tree
Tree Options: Click mod wood
Shop Options: Select item and amount
Shop Options: Enable auto unbox after purchase
Shop Options: Click purchase
Shop Options: Click purchase all blueprints
Axe Options: Activate axe range toggle
Axe Options: Toggle no axe cooldown
Vehicle Options: Activate vehicle modifications
Vehicle Options: Click spawn vehicle
Troll Options: Select target and action
Troll Options: Click perform action
Settings: Save configuration
Settings: Save slot names
Settings: Toggle UI keybind
Settings: Click close GUI

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

Landing: Load script via executor
Client Options: Configure walk speed slider
Client Options: Bind fly and noclip keys
Client Options: Toggle infinite jump and god mode
Game Options: Select teleport destination
Game Options: Toggle rejoin re-execution
Property Options: Select slot to load
Property Options: Load selected slot
Property Options: Inspect player slot datasizes
Property Options: Click free land
Tree Options: Select tree type and size
Tree Options: Click bring tree
Tree Options: Toggle autofarm selected tree
Tree Options: Click mod wood
Shop Options: Select item and amount
Shop Options: Enable auto unbox after purchase
Shop Options: Click purchase
Shop Options: Click purchase all blueprints
Axe Options: Activate axe range toggle
Axe Options: Toggle no axe cooldown
Vehicle Options: Activate vehicle modifications
Vehicle Options: Click spawn vehicle
Troll Options: Select target and action
Troll Options: Click perform action
Settings: Save configuration
Settings: Save slot names
Settings: Toggle UI keybind
Settings: Click close GUI