IRX RUST 2x
Publicada el 2026-07-14
Descripción de la oferta
# IRX Rust — Core Systems Specification ### Developer Handover (Essential Modules Only) --- # 1. IRX Score System The IRX Score System is the core of the entire project. Every player action that contributes to the competition must be validated, scored, logged, and synchronized in real time. ### Responsibilities * Calculate all PvP scores * Calculate Farm scores * Calculate Objective scores * Apply bonuses * Apply penalties * Prevent abuse * Update clan score instantly * Update leaderboard instantly * Store every score in Score Ledger ### Important Rules * Only Clan Score determines winners. * Solo players never participate in rankings. * Every score event must be permanently stored. * No score should ever be calculated only on the client side. * Backend must always be the source of truth. --- # 2. Clan System The clan system manages every team participating in the weekly competition. ### Features * Create Clan * Join Clan * Leave Clan * Kick Member * Clan Ownership * Clan Member List * Clan Statistics * Clan Ranking * Clan History ### Required Logic Every player belongs to only one clan. If a player leaves or is kicked: * Remove all score contributed by that player from the current clan. * Do NOT transfer score to another clan. * Save the event in history. Every clan change must synchronize immediately with: * Website * Leaderboard * Backend * Discord * Admin Panel --- # 3. Weekly Competition System The server runs weekly competitions. Competition duration includes two wipes. At the end of the week: * Calculate Top 3 Clans * Lock final scores * Generate winners * Store history * Prepare prize distribution This system must never allow score manipulation after weekly lock. --- # 4. Leaderboard System Leaderboard is completely dynamic. There should never be manual refreshes. ### Must display * Top Clans * Clan Score * Weekly Rank * Player Contribution * Total Members * Live Updates Every score change should immediately update: * In-game leaderboard * Website * Admin Dashboard * Discord announcements Backend is the only source of leaderboard data. --- # 5. Score Ledger Every point earned must have a permanent record. Each entry should contain: * Timestamp * Player * Clan * Event Type * Weapon * Points * Bonus * Final Score * Server * Wipe ID Nothing should ever modify score without creating a ledger entry. This is the audit system of the project. --- # 6. PvP Score System Weapon scores follow the official configuration. The system must support: * Weapon Score * Headshot Bonus * Distance Bonus * Strong Player Bonus * Objective Bonus The system must also prevent abuse. Examples: * Team Kill → 0 * Sleeper Kill → 0 * NPC Kill → 0 * Scientist Kill → 0 * Trap Kill → 0 * Turret Kill → 0 Repeated kills should reduce score automatically according to project rules. --- # 7. Farm Score System Farming contributes to clan progress. Supported resources include: * Sulfur * Metal Ore * Wood * Scrap * Other configured resources Farm score can contribute only up to **20%** of the final clan score. PvP remains the primary ranking factor. --- # 8. Kit System The Kit System should be modular and fully configurable. Features: * Starter Kits * VIP Kits * Event Kits * Cooldowns * Permissions * Usage Logs Admin should be able to create or edit kits without modifying source code. --- # 9. Loot System Loot should be managed independently from score logic. Features: * Custom Loot Tables * Bradley Loot * Helicopter Loot * Locked Crate Loot * Event Loot * Multipliers * Drop Chances Configuration should be editable without recompiling plugins. --- # 10. Admin System Create a complete in-game admin panel. Functions include: * Teleport * Spectate * Kick * Ban * Mute * Give Items * Spawn Items * Wipe Commands * Broadcast * Reports * Player Lookup * Clan Lookup Every admin action must be logged. --- # 11. Website Synchronization The website should never calculate data independently. Everything displayed must come directly from the backend. Pages include: * Homepage * Live Leaderboard * Clan Profiles * Player Profiles * Weekly Rankings * Prize Information * Server Status Updates should happen in near real time. --- # 12. Discord Integration Discord should receive automatic events. Examples: * Wipe Started * Wipe Ended * Weekly Winners * Top Clans * Ban Notifications * Cheat Detection * Reports * Server Restart * Plugin Errors Manual posting should never be required. --- # 13. Anti-Abuse System The system must automatically detect: * Spawn Killing * Repeated Kill Farming * Clan Boosting * Score Exploits * Alternate Accounts * Suspicious Activity Suspicious actions should generate alerts for admins. --- # 14. Performance Requirements The server must remain optimized even with high player counts. Requirements: * Low CPU usage * Low memory usage * Optimized database queries * Efficient caching * Minimal network traffic * Fast leaderboard updates Plugins should never block the main server thread unnecessarily. --- # 15. Code Standards The entire project should follow production-quality standards. Requirements: * Modular architecture * Clean folder structure * No duplicate code * No unused files * No dead code * Proper documentation * Consistent naming * Easy maintenance * Easy future expansion The project should be simple for another developer to understand and continue without needing to rewrite existing systems. --- # Important Business Rules (Do Not Change) The following systems are considered core business logic and **must not be modified without approval**: * Weekly Prize Logic * Clan-based Ranking * Score Calculation Rules * Weapon Scores * Farm Contribution Limits * Anti-Abuse Rules * Score Ledger Integrity * Real-Time Synchronization * Leaderboard Calculation * Clan Score Ownership These systems define the identity of IRX Rust and must remain consistent across future updates.
Skills
Fuente original: freelancer