Drxp

Changed Status from Work in Progress to Fixed

Changed Status from Pending to Work in Progress Changed Fixed In to Next Version

1. Database Setup If you’re hosting on a Pterodactyl panel: Go to your bot’s panel. Navigate to Databases → Create New Database. After it’s created, copy the JDBC Connection String. Example provided: jdbc:mysql://host:3306/database?user=username&password=password Important: Remove the jdbc: prefix. Modified example: mysql://username:password@host:3306/database 2. Environment Variables Step 1: Rename Example File Rename .env.example → .env Step 2: Required Variables Inside .env (or .env.local for local dev), add: # Database DATABASE_URL="mysql://username:password@host:3306/database" # Authentication NEXTAUTH_SECRET="your_generated_secret" NEXTAUTH_URL="http://localhost:3000" # API Keys API_KEY="your_generated_api_key" NEXT_PUBLIC_API_KEY="your_generated_api_key" # Steam API STEAM_API_KEY="your_steam_api_key" Step 3: Generate Keys Run this twice in your terminal: node -e "console.log(require('crypto').randomBytes(32).toString('hex'))" First value → NEXTAUTH_SECRET Second value → both API_KEY and NEXT_PUBLIC_API_KEY Save your API key separately you’ll need it for your Rust plugin. Step 4: Steam API Key Go to Steam Web API Key. Enter your domain (localhost:3000 for dev). Copy your API key → STEAM_API_KEY. 3. Database Initialization Run the following in your project root: npx prisma generate npx prisma db push node prisma/seed.js This sets up schema, tables, and default data. 4. Add Your First Admin Method 1: Prisma Studio (Recommended) Get your SteamID64 from steamid.io. Open Prisma Studio: npx prisma studio In Admins table → Add: steamId: your SteamID64 displayName: your display name ownerId: same as SteamID64 In AdminPermissions table → Add: adminSteamId: your SteamID64 permissionId: the ID for owner_access 5. Hosting (Vercel) Go to Vercel → Import Git Repository. Select your repo → Import. Under Build & Output Settings → toggle Build Command → set to: prisma generate && next build Add your Environment Variables in Vercel dashboard (same as .env). <- do this before you Deploy. Now Deploy 6. Rust Plugin Setup (Stats.cs) Copy Stats.cs to your server’s oxide/plugins/ or carbon/plugins folder. Edit oxide/config/Stats.json: { "Web API URL": "https://yourdomain.com", "Web API Key": "your_api_key_from_env_file", "Server ID": "your_server_id", "Batch Interval": 5.0 } Make sure Web API Key matches the one in your .env. 7. Permissions Reference Available permissions: owner_access – full access view_stats – view player data manage_admins – manage admins manage_permissions – manage permissions view_admin_panel – access admin panel edit_player_stats – modify stats delete_player_stats – delete stats server_management – manage servers manage_themes – manage themes 8. Troubleshooting Connection errors: ensure you removed jdbc: from DB URL. No admin access: add your SteamID manually in Prisma Studio. Schema mismatch: run npx prisma db push . No Rust data: verify API URL (don’t include /api/stats) and API Key match.

Changed Status from Work in Progress to Closed

Changed Status from Work in Progress to Closed

Changed Status from Work in Progress to Closed

Changed Status from Pending to Fixed

Changed Status from Work in Progress to Fixed

Changed Status from Pending to Work in Progress Changed Fixed In to Next Version

Changed Status from Pending to Work in Progress Changed Fixed In to Next Version

Changed Status from Pending to Work in Progress Changed Fixed In to Next Version

No it has been working, ill fix!

Changed Status from Pending to Work in Progress Changed Fixed In to Next Version

Changed Status from Not a Bug to Closed

You're using Node.js v24.4.1, which is too new for [email protected] downgrade to Node.js v18.x or v20.x LTS. This should fix this issue.

Changed Status from Pending to Not a Bug

i will get this updated and pushed out asap!

Changed Status from Pending to Not a Bug

Hi! Thanks for your detailed questions and feedback. Here are answers to each of your points: 1. Stack Size by Category as Percentage (Min/Max) Currently, the plugin sets stack sizes per item or per category using a fixed number, not a percentage. To achieve what you want (e.g., give between 25% and 75% of the server’s max stack size for a category), the plugin would need to be updated to support min/max percentages per category. This would allow you to define, for example, that all "ammo" items are given in random amounts between 25% and 75% of their max stack size, keeping things balanced even as new items are added. If you want this feature, let me know! It’s a great idea and can be added. 2. updatestacksize <category> <newSize> Command The <newSize> is a fixed number, not a percentage. For example, updatestacksize ammo 30 sets all "ammo" items to a stack size of 30. There is currently no minimum/maximum or percentage option just a single value. If you want to set by percentage or set min/max, that would require a plugin update (see point 1). 3. "Interval Seconds" – What is an Automatic Drop? "Automatic drop" means the plugin gives every online player a random item every X seconds (as set by "Interval Seconds"). If you only want items to be given when players jump (not automatically), set "Give Item On Jump": true in the config. This disables the timer-based drops. 4. "Hardcore Mode" – What Does It Block? When "Hardcore Mode" is enabled, players cannot gather resources from dispensers (e.g., mining rocks, chopping trees, etc.). This is to make the game harder by forcing players to rely on random item drops. 5. "Happy Hour" – How Does It Work? "Happy Hour" limits automatic drops to a specific daily time window and announces when it starts/ends. If you use "Give Item On Jump," Happy Hour does not affect jump-based drops only the timer-based (automatic) ones. 6. Jump Detection – Even for Short Jumps The plugin already gives an item whenever a player jumps, regardless of how high or where (even on boxes or inside structures). If you notice missed jumps, let me know there may be edge cases, but the intent is to reward every jump. 7. Removing the Item Receipt Message To remove the chat message players get after receiving an item, you’ll need to comment out or remove the line in the code that sends the message. Specifically, look for lines like: player.ChatMessage($"<b><color=yellow>Random</color><color=red>Items</color></b>: {message}"); and either comment them out or delete them. If you want, I can provide a code snippet or update to do this for you. Let me know if you want help with any of these changes, especially the percentage-based stack sizes or removing messages! Thanks for using the plugin and for your suggestions they help make it better for everyone.

Problem 1 – “Jump” gives nothing On first start the plugin created oxide/config/RandomItems.json with its default settings. By default the option "Give Item On Jump": false is set to false, so nothing happens when you jump. Either wait for the normal timed drop (every 300 s by default) or turn the jump feature on: Open oxide/config/RandomItems.json. Set "Give Item On Jump": true Save the file and reload the plugin: oxide.reload RandomItems  (or o.reload RandomItems) After that, every valid jump (not on cooldown) will hand out an item. Problem 2 – How to manage / control the plugin A. Console command supplied by the plugin updatestacksize Usage: updatestacksize  → lists all item categories in the config updatestacksize <category> <newSize> → sets stack size for every item in that category Must be run from the server console (not in-game chat). B. Configuration file options (oxide/config/RandomItems.json) Interval Seconds – time between automatic drops. Hardcore Mode – true = block resource gathering. Debug Mode – verbose logging. Happy Hour Enabled / StartTime / EndTime – limit drops to a daily time window and announce start/end. Give Item On Jump – true = disable timer, give item whenever a player jumps. items [] – full list of items, categories, stack sizes (auto-generated the first run; you can edit or remove entries).

Sorted, give it a few the images should start to come back if not let me know ill update the image links