Hosting Control Panel for Personal GameGuardian Lua Scripts

✔️ Protect & Monetize Your GG Scripts
✔️ Device ID Access Control
✔️ Remote Updates & Management
✔️ Secure Hosting with Anti-Piracy Protection

The Main Problem:

Your script costs money, but revenue "leaks" away?

You created a quality script, invested time and effort. But after selling to one user, the file starts living its own life: shared with friends, posted in chats. As a result, you lose control and don't receive profit from each real user.

---

Our Solution:

Personal FTP Hosting with Device ID Access Control System.

This is your personal "control center" for scripts. You decide who can use your product and for how long.

---

Key System Features:

• 🔒 Access Control: Grant access only by Device ID of specific devices.
• 🔄 Remote Updates: Fix bugs or add features — all your users receive the new version automatically.
• 🎯 Flexible Monetization:
  • Set expiration dates (subscription model).
  • Offer trial periods with limited launches, plus a separate testing script.
  • Show users payment information and your contact details.
• 📊 Complete Statistics: Track all connections through logs.

---

How Does It Work?

1. You add our small "loader" code at the beginning of your script.

2. You encrypt your main script using any method you prefer.

3. You upload to your personal FTP hosting:

• Your encrypted script.
• Fill the users.xlsx file with client database (ID, name, payment date, comments).

4. Done! When launched, our code checks the user's Device ID against your database and decides: allow work, show payment message, or update the script.

VERS_script="1.1" --script version
PATH1="Apex" --Your nickname on server
PATH2="AngryBirds" --Game name
TG="https://t.me/Hacker" --your Telegram

local a=gg.makeRequest("https://files.script-run.com/load.lua")if a and type(a)=="table"and a.code==200 then File_for_Update=gg.getFile()a=pcall(load(a.content))if a==false or access=="update"then os.exit()end else gg.alert("Connection failed.")os.exit()end

if access then
local paid_msg=""
if client then
paid_msg="\n✅Your script is valid until "..user_date
end
gg.toast("Hello "..name.."!"..paid_msg)
else
gg.copyText(TG,false) --Automatically copy contact for payment
local alert_msg="Your ID: "..id.."\n\n"
if user_date then
alert_msg=alert_msg.."⚠️ Subscription expired "..user_date
else
alert_msg=alert_msg.."🔒 Script access denied."
end
alert_msg=alert_msg.."\n\n"..price.."\n\nTo get access, write to me:\n"..TG.."\n\n(Link copied to clipboard)"
gg.alert(alert_msg)
os.exit()
end


--Insert your Lua code below

Security and Hosting Structure

We understand that the security of your code is priority #1. Therefore, our system is built with protection from traffic analysis and unauthorized access in mind.

How your personal FTP account is organized:

your_login/
├── /Game1/                          # Folder for first game
│       ├── update1.1.lua         # Main script version for Game1
│       ├── update1.1test.lua   # Testing version for Game1
│       └── /WWp4eUxmcmo/      ← **SECRET FOLDER** (automatically generated)
│                ├── users.xlsx        # Your client database and settings ONLY for Game1
│                ├── yes.txt             # Successful connection logs
│                └── no.txt              # Denied/expired connection logs
└── /Game2/                           # Folder for second game
       ├── update2.0.lua
       └── /aB3dEfGhIjK/           ← **Unique secret folder for Game2**
                ├── users.xlsx
                └── ...

Why this structure? Protection from reverse engineering:

Separation of logic and data:

• Direct links lead only to script files (/your_login/Game1/update1.1.lua)
• Critical business logic (client database, logs) is stored in a randomly generated folder with an unknown path.

Protection from traffic analysis:

• Even if an attacker intercepts the update request, they only see: → https://users.script-run.store/your_login/Game1/update1.1.lua
• They WON'T see: the path to your users.xlsx database, because access verification goes through the server's internal mechanism that knows the secret folder path.

---

Try It Now! (Demo Access)

We provide a fully functional test account so you can test everything.

Install FileZilla Client on your PC, for Android ES-FileExplorer or similar.
FTP connection details:

• Address: users.script-run.store
• Login: script_Test
• Password: script_Test

Flexible Version and Access Management

Our system provides advanced control not only over who has access, but also over which version of the script they receive. Everything is managed through the users.xlsx file on your FTP.

1. Centralized Version Management (Auto-Updates)

Forget about users staying on old versions. The system automatically compares the script version on the device with what's specified in your database and updates it if necessary.

• "Default Version" (main):
This version is for all paying customers. Specify it in the corresponding field (e.g., 1.1). Upload a file named update1.1.lua to the server. If the client's version differs — they'll receive the current update automatically.

• "Testing Version" (demo/limited):
Specify your demo version name here (e.g., 1.1test). The file update1.1test.lua should be on the server. Any new user not in the database, or a user with an expired subscription, will receive this version. This allows safely giving the script for testing while limiting functionality.

• Individual Version for Specific Users:
In the comments column for any user, you can specify a specific version (e.g., 1.2beta). The system prioritizes this entry. This is ideal for:

• Testers: Give them a special debug build.
• VIP Clients: Provide an extended or experimental version.
• Post-Production: Fix a bug for one user without touching the main version.

2. Trial Period Management ("Number of Tests")

Want to offer a test but limit time or number of launches? Easy!

• In the "Number of Tests" field, set the launch limit for the demo version (e.g., 20).
• All non-paying users automatically go to the separate "Testing" sheet in your Excel file.
• The system tracks their launches. Once the limit is reached — the user sees a purchase message.

3. Flexible Price Messages ("Price Variable")

You fully control the text users see when access expires. In the "Price variable" field, write your message.
Default example: Script price: $5/month.

4. Smart Date Recognition

Don't worry about date formats. Our server automatically converts dates from your table to a single standard.
The system understands: 1.01.2025, 01.1.2025, 01.01.25, 01,01,2025, 01-01-2025 — all will be correctly processed as 01.01.2025.

---

What's Inside the Demo Account?

Demo files with script versions - update1.1.lua, update1.1test.lua, update1.2.lua

users.xlsx — editable client database file. Add a test Device ID and date. The file has 2 sheets. The first sheet contains paying customers, the second sheet automatically adds testing users.

Logs

• yes.txt — successful access.
• no.txt — subscription expired or tests finished.

You can edit all these files yourself.

Tracking all connection logs to your script. View Connection Logs

---

Pricing and Conditions

• 🥳 Free Testing: 14 days!
• After trial: $0.5 per month for each active user (with non-expired date in your users.xlsx).
• 🎁 3 Free Slots — for you, testers, or close friends (no charge for first 3 IDs).
• Transparent Billing: Once a month we automatically check the number of active IDs in your database. You pay only for real users.

---

Ready to Protect Your Work and Start Earning Steadily?

Contact us to get personal hosting and detailed integration instructions!

Telegram @golferstern

P.S. This isn't just file hosting. This is a business tool that transforms your script from a "leaking" file into a controlled service with regular subscriptions.

Domain: users.script-run.store