Leaderboard

We’re excited to bring you one of the most content-packed updates Roat Pkz has seen in recent months! This update introduces a variety of new gear and mechanics, including the powerful Oathplate Armour, its cosmetic upgrade Radiant Oathplate, and the versatile Soulflame Horn. Players will also find fresh utility items like the Surge Potion, Locator Orb, and Tome of Earth, offering new combat strategies and gameplay depth. Ranged users can enjoy the new Hueycoatl Hide Armour, and we’ve added an in-game Best-In-Slot Interface to streamline your gear setup. On top of that, Player-Hosted Tournaments are now live-giving you the power to create your own competitions with real rewards. Whether you’re a PvP purist or a collector, there’s something in this update for everyone. Watch a highlight video of the update here! Oathplate armour Oathplate armour has been added to the Bounty Hunter Point shop. Compared to torva armour, oathplate's main differences are the added offensive slash bonus, the lesser strength bonus, and the lack of any prayer bonus. It also penalizes magic attack slightly less, while also providing stronger slash and magic defence. However, it has less stab, crush and ranged defence, and a stronger penalty to ranged attack. Oathplate Helm: 30,000 BHP Oathplate Chest: 60,000 BHP Oathplate Legs: 60,000 BHP Radiant oathplate armour Radiant oathplate armour is a cosmetic upgrade of regular oathplate armour that can be created by using the purifying sigil on each piece of armour. The sigil is made by combining five separate pieces obtained from superior slayer monsters – a bottom, top, left, right, and middle. Soulflame horn The soulflame horn has a special attack, Entice, which is applied to up to 3 other players within a 3 tile radius of the user, costing 25% special attack energy per affected player. The soulflame horn is only usable when in range of at least one other player but will also apply the Entice effect to the user, regardless of the number of affected players and without impacting the cost. The player may configure the radius (0-3) by right clicking the horn. When under the effects of Entice, the player's next melee attack within 10 ticks (6 seconds) is always a successful hit; this also applies to melee special attacks. For multi-hitting attacks (such as the dual macuahuitl, Scythe of Vitur, or dragon dagger special attack), this effect only applies to the first hitsplat. However, due to the intricacies surrounding the special attacks of the dragon claws and burning claws, those will have their second hitsplat affected instead. If attacking another player, the effect is replaced by a 100% accuracy increase for their next melee attack. Soulflame horn has been added to the slayer shop for 500 Slayer points. Surge potion and Locator orb Surge potions restore 25% special attack energy per dose, but can only be drank once every five minutes. In the Wilderness, Surge Potions can only be used at level 10 or below. Surge potion can also be made via herblore. Surge potion has been added to the PK Point shop for 1000 PKP. Using the locator orb will reduce a player's health by 10 hitpoints down to a minimum of 1 hitpoint and cannot kill the player, similar to a dwarven rock cake. Because of this, it can be beneficial to use in combination with the Dharok's armour set. Locator orb has been added to the PK Point shop for 1000 PKP. Tome of Earth Casting earth spells with a charged tome equipped will increase the spell's damage by 10% (multiplicative with magic damage bonus from equipment) and consume one charge per spell. The bonus applies only to the standard spellbook's earth spells (Earth Strike, Earth Bolt, Earth Blast, Earth Wave, and Earth Surge). Tome of Earth has been added to the Mage arena shop for 50 Mage Arena points. Soiled page has been added to the Mage arena shop for 1 Mage Arena point. Hueycoatl hide armour Hueycoatl hide armour is a set of Ranged armour. Compared to blessed dragonhide armour, Hueycoatl hide armour possesses higher Magic defence and prayer bonus; the other stats are identical, essentially making most pieces of Hueycoatl hide armour an upgrade to blessed dragonhide. Hueycoatl hide coif has been added to the Range shop for 25 PK Points. Hueycoatl hide body has been added to the Range shop for 50 PK Points. Hueycoatl hide chaps has been added to the Range shop for 50 PK Points. Hueycoatl hide vambraces has been added to the Range shop for 25 PK Points. Best in slot interface A new interface allowing you to select, compare, and equip optimal gear setups seamlessly. You can use it by using ::BIS in-game or going through the Quest Tab. Player hosted tournaments Player-Hosted Tournaments are here! Use the Tournament Master to host your own tournament! Host with an item (2M+ PKP value) and the winner takes it all. Host with PK Points, and the prize gets split: 50% / 30% / 10% / 10% among the top 4. Multiple setups available: Dharok, Pure, Zerker, No Armor, and more! Tournament Crate A brand new Tournament Crate is now available (tradeable, valued at 100K PKP)! Win any tournament to earn one, and you’ll have a shot at rewards worth up to 500K PKP! The crate also features its own Collection Log with exciting rewards to chase. ----- Additional Changes Base reward for participating and winning a tournament has been raised significantly. You can now wear an item from the bank (inventory tab while bank is open). New items: Rada’s blessing 4 has been added to the PK Point shop for 25 PKP. Ring of shadows has been added to the PK Point shop for 100 PKP. Dragon kiteshield has been added to the PK Point shop for 500 PKP. Monk's robe (t) has been added to the Donator shop for 25 DP per piece. Leather body and chaps (g) have been added to the Donator shop for 10 DP per piece. Helmet of the moon has been added to the AFK store for 5000 AFK Tokens. New clue rewards: Guthix, Zamorak & Saradomin Scimitar kits added to Easy clue (2.5K value) Amulet of defence (t) added to Easy clue (2k value) Amulet of power (t) added to Easy clue (2k value) Holy wraps added to Medium clue (2k value) The following items are now spawnable: * Amethyst dart * Dragon sword * Granite gloves * Granite boots * Granite ring normal & (i) * Fancier boots * Zombie helmet * Ardougne cloak 3 * Ardougne cloak 2 * Ardougne cloak 1 * Granite longsword

Hello fellow members of the Roat Pkz community. The members of the Roat Pkz Staff Team would appreciate constructive criticism, preferably in-depth, as well as opinions on their contributions as a member of the staff team from the player's perspective. This will be a monthly announcement topic in order to stay up to date. Please ensure that you are being honest in your input, as this is to help the staff team provide better service and assistance to the members of the Roat Pkz community. The current staff team members are listed below for convenience. Note: Playtime is from the last 30 days. The ⭐ refers to most hours active in respected role and is purely to highlight top contributors. Owner GRETAR -> Playtime: NaN Elder HEMMI80 -> Playtime: NaN Senior Admin(s) ⭐SMACKD -> Playtime: 14 Hours (+86 Hours AFK) Administrator(s) RAG BOT V1 -> Playtime: 3 Hours (+25 Hours AFK) VALENCE -> Playtime: 2 Hours (+13 Hours AFK) ⭐FRUITIEST -> Playtime: 57 Hours (+96 Hours AFK) Account Support(s) LEGEND -> Playtime: NaN FANTASTIC CX -> Playtime: NaN Community Manager(s) SMOOTHIE -> Playtime: 103 Hours (+83 Hours AFK) ⭐OMODS -> Playtime: 106 Hours (+162 Hours AFK) Senior Moderator(s) NO NAME SET -> Playtime: 40 Hours (+35 Hours AFK) ⭐MAMBERROI JR -> Playtime: 71 Hours (+46 Hours AFK) Moderator(s) ⭐REAL DOZARD -> Playtime: 98 Hours (+22 Hours AFK) HEFNER -> Playtime: 82 Hours (+123 Hours AFK) 4OAK -> Playtime: 77 Hours (+104 Hours AFK) Senior Support(s) NECROFEAR PB -> Playtime: 35 Hours (+35 Hours AFK) ⭐JAY -> Playtime: 81 Hours (+135 Hours AFK) CRAIG -> Playtime: 53 Hours (+57 Hours AFK) Server Support(s) HUNNETSVILLE -> Playtime: 15 Hours (+563 Hours AFK) KING KEN -> Playtime: 25 Hours (+594 Hours AFK) ADAM -> Playtime: 1 Hours (+10 Hours AFK) FLY -> Playtime: 108 Hours (+70 Hours AFK) AZS878 -> Playtime: 135 Hours (+59 Hours AFK) LIN MING -> Playtime: 102 Hours (+7 Hours AFK) WUBWUBWUB -> Playtime: 25 Hours (+128 Hours AFK) LEONEL07 -> Playtime: 54 Hours (+8 Hours AFK) ⭐SIXT -> Playtime: 141 Hours (+95 Hours AFK) __ Promotions __ Demotions/Resignations SwayziPk has been demoted and is now a Regular Player. __ Please note that all feedback should be honest and constructive criticism. All negative and inappropriate comments such as trolling, spam, or unnecessary flame, will be removed without hesitation. Suggestions for current staff members, and even suggestions for potentially new staff members are welcome, but must have valid, well explained reasons alongside the suggestion. ~ Roat Pkz Staff Team

Thanks for sharing!

Hmmm🤔

Gl king ♥️

#1 TEAM ❤️

RoatPKz Definitive Gambling & Tournament Ecosystem There's many things I would approach at this point within my experience of playing this amazing server in the past month, roughly 22 days I believe currently since I began RoatPkz and these are many ideas and interests sparking in my mind with this community and the potential within the pking community and gambling scene, today I'm presenting some suggestions and ideas for future updates, potentially boosting the community involvement between one another, while PvPing, Warring, Gambling, Tournaments, Clan Events. Today, I am asking for you to review and oversee the information I've put a lot of time into putting together after thinking for many hours I've bottled everything into a guided informational format, touching grounds on many levels of my thoughts. I'm open to any Questions, Support, Ideas, Help And Loving Guidance from any Community Youtubers/Streamers or Any Mods/Admins In-Game That would like to speak about this personally and touch base on anything as I truly have an interest in games and seeing the future growth of them I am open to discuss anything revolving this. Please, Provide Feedback, Support and Share! Mention This Forum To Your Friends & Community! I would like to get many people involved in this and talking about the potential within this as I previously have mentioned this similar structured idea to some of the community/streamers, them being supporting this already before, I've now decided to process everything and format this. So with all of our communities help, and some friends spreading the words in Discords and along through the server and word of mouth, maybe these ideas could potentially come true as it would introduce a lot of movement to the pvp community, wilderness and gambling throughout the entire server. 1. Introduction & System Vision 1.1. Preamble This document serves as the master blueprint for an advanced, integrated gambling and tournament ecosystem specifically designed for RoatPKz. It synthesizes all previously discussed concepts, aiming for maximum detail, operational clarity, and robustness. This ecosystem is envisioned as a premier feature, deeply woven into RoatPKz's renowned Player-vs-Player (PvP) culture. 1.2. Core Vision To establish a thrilling, transparent, and demonstrably fair PvP betting and tournament scene that: ● Provides engaging content for both active participants and spectators. ● Rewards skill, strategy, legitimate participation, and community trust. ● Implements state-of-the-art, multi-layered anti-rigging and fairness mechanisms, including sophisticated protections for the integrity of player reputation scores and host roles, making manipulation exceedingly difficult, and ensuring bettors are protected from losses due to faulty or exploited fights through a clear refund system. ● Introduces a dynamic, community-influenced "Elusive Trust Score" for all participants and facilitators, with strong safeguards against its abuse. ● Offers diverse and unique reward structures, including direct fighter/clan stakes, comprehensive war spoils distribution, and substantial tournament prize pools. ● Functions as a configurable and sustainable money and item sync, contributing positively to the RoatPKz server economy. ● Provides a wide array of betting options, from simple win/loss to intricate proposition bets on specific in-fight events. ● Empowers event hosts (players, Trusted Hosts, and Server Staff) with clear tools to define specific match rules and tournament themes, enhancing variety and strategic depth. This master blueprint aims to be the definitive guide for developing a cornerstone feature of RoatPKz, fostering competition, community interaction, and long-term player engagement. 2. Core System Components & Features: Detailed Operational Breakdown 2.1. Event Types: Mechanics and RoatPKz Context ● 1v1 Duels: ○ Initiation: Player A challenges Player B via the Gambling Hub (e.g., accessible via ::gamble command or a physical NPC near Edgeville/Grand Exchange). Player A proposes: ■ Rules: Selected from comprehensive lists (See Section 2.5), covering common OSRS setups like "NH Brid," "Max Melee," "Pure Tribrid," "DDS & Whip Only," etc. ■ Entry Fee: An agreed-upon GP amount (or potentially other RoatPKz-specific valuable currencies like PKP, if balanced by admins, though GP is standard for main pools) within server-defined min/max limits for the chosen betting tier. ○ Acceptance & Lock-in: Player B receives the challenge with all proposed terms clearly displayed. Upon acceptance, both players' entry fees are immediately transferred to a system-managed escrow account. This action is a binding commitment. ○ Listing & Forfeiture: The duel is listed on the Betting Board. Failure to be present and ready at the scheduled fight time (after a short, defined grace period, e.g., 60-120 seconds) results in automatic forfeiture of the absentees entry fee to the present opponent. Viewer bets on a forfeited match are voided and refunded. ● Clan Wars: ○ Initiation: A designated Clan Representative (Leader/Officer with specific clan permissions) uses the Gambling Hub. They define: ■ Target Clan (or issue an open challenge filterable by other clans). ■ Participant Count: (e.g., 5v5, 10v10, up to common RoatPKz war sizes like 25v25 or 30v30). ■ Gear Rules Options like "Matched Opts" (both clans use identical predetermined setups), "Own Gear - Full Out PKRI Style" (risking own items), "Specific Tier Gear Only." ■ War Stipulations: From a list (See Section 2.5), e.g., "Mage Arena Only," "Specific Wilderness Multi-Zone (e.g., East Dragons, Chaos Temple)," "No Vengeance Pures," "Ancients Only," "Single Spells Only." ■ Optional Clan Stake: GP amount from clan funds (verified by the system). ■ Betting Tier for viewer bets. ○ Acceptance & Listing: The challenged clan's representative reviews all terms. A system-mediated interface allows for negotiation on stipulations or stakes. Upon mutual agreement, terms are locked. Clan Stakes are transferred to escrow. The war is listed for spectator betting. The prestige of winning a bettable war, especially with high stakes/viewer count on RoatPKz, should be a significant motivator. ● Mod-Hosted Special Events: ○ Setup: Server Staff/Moderators use a dedicated admin panel to create and manage these unique events. They define: ■ Event Name & Theme: e.g., "RoatPKz King of the Hill Championship," "Legendary Weapon Tournament" (all participants use provided iconic OSRS weapons like Armadyl Godswords, Twisted Bows, Scythes), "Celebrity Deathmatch" (featuring well-known RoatPKz players, streamers, or even staff members). ■ Participants: Invitational (based on player name, Trust Score, tournament qualifications) or open registration with specific criteria. ■ All Rules: Gear (often unique or highly specific predetermined setups, e.g., "Everyone gets full Ancestral, Kodai, Arcane"), stipulations (non-negotiable for these events). ■ Prize Structure: Can be substantial GP, rare/unique RoatPKz untradeable items, exclusive cosmetic titles/icons, temporary server-wide perks for the winner's clan. ■ Betting Availability: Main outcome, and specific, curated prop bets designed by staff for the event. ○ Announcement & Listing: Prominently announced server-wide (e.g., global messages, forum posts, Discord) and listed on the Betting Board with a distinct "Mod-Hosted" tag. ○ Event Calendar & Unique Themes: "Publish a potential schedule for mod-hosted events to build anticipation. Design events with unique themes, challenges, or gameplay modifiers (e.g., "King of the Hill" with specific gear, multi-stage elimination fights, "mystery gear" events)." ○ Transparency and Impartiality in Hosting: "Outline procedures that ensure and visibly demonstrate mod impartiality during these events (e.g., public logging of critical decisions, predefined event rulesets mods must follow)." ● Player-Entered Bracket Tournaments: ○ Setup: Staff define tournament templates (e.g., "Weekly Dharok Annihilation," "Monthly Pure NH Open," "RoatPKz Zerker Cup," "Void Ranger Knockout," "Tribrid Masters"). Templates specify: ■ Tournament Ruleset: Gear (e.g., "Full Dharok's, Fighter Torso, Dragon Defender, Infernal Cape, specific inventory of 6 brews, 3 restores, rocktails, karambwans, vengeance runes"), banned items/spells, combat brackets (e.g., 1-45 Def, 75-99 Def). ■ Entry Fee, Participant Cap, Bracket Type (single/double elimination). ■ Prize Distribution for top finishers (e.g., 1st: 60%, 2nd: 30%, 3rd: 10% of prize pool). ○ Registration: Players register via the Gambling Hub, paying entry fees. Registration closes at cap or deadline. ○ Bracket Generation: System automatically and randomly generates the bracket. Buys handled systematically. Bracket is publicly viewable and updates in real-time. ○ Progression: Matches are scheduled or occur as participants become available. Each match is individually listed for betting. Winners advance automatically. ○ Seeding, Bracketing & Progression: "Detail how tournament seeding will work: options include random seeding, ELO-based (if a ranking system exists/is developed), or buy-in tier influencing seed. Specify how brackets will be generated, displayed in real-time (perhaps via an in-game UI or a dedicated section on the forums/website), and how match progression is updated." ○ Tournament Parameters & Payouts: "Define minimum/maximum participant numbers for tournaments to run. Create clear structures for how prize pools (from entry fees) scale with participant numbers and how they are distributed (e.g., percentage-based for Top 3, Top 8, etc.)." ● Trusted Host Facilitated Duels: ○ Host Role & Selection: Players achieve "Trusted Host" status via a rigorous application process (See Section 7.2), demonstrating extensive game knowledge, a consistently high Trust Score, and potentially vouchers from established RoatPKz community figures or staff. ○ Initiation: A Trusted Host uses a dedicated interface ("Host Panel") to set up a 1v1 duel. They can either invite two specific fighters or create an "open slot" advertising a fight with certain parameters (e.g., "Max Melee Fight, 10M Entry Fee, Hosted by [HostName]"). The Host defines/negotiates rules and the Fighter Entry Fee with participants. ○ Confirmation & Listing: Both fighters agree to the Host, rules, and entry fee. Fees are paid to escrow. The duel is listed, clearly identifying the Trusted Host. The Host's commission rate (fixed by server, e.g., 1-2% of viewer pool) is displayed. ○ Oversight: The Trusted Host is expected to be present or actively monitor the fight to ensure smooth conduct and adherence to any manually enforced rules. They act as a point of contact for issues during their hosted fight. ○ Detailed Calculation & Modifiers: "Specify how the "Elusive Trust Score" is precisely calculated. Factors could include: number of successfully hosted duels, total value of duels hosted, age of account, player commendations/reports (verified), successful dispute resolutions, and penalties for misconduct." ○ Visibility, Tiers, and Benefits: "How will the score be displayed (e.g., next to username, in a profile)? Consider trust tiers (e.g., Bronze, Silver, Gold Host) with tangible benefits or permissions, such as the ability to host duels with higher stake limits, access to special hosting tools, or reduced fees." ○ Dispute Resolution & Score Impact: "Establish a clear process for resolving disputes involving trusted hosts. How do confirmed issues impact their score and status?" 2.2. Betting Mechanisms: Mechanics and OSRS Context ● Spectator Betting (Main Outcome): Players select an event from the Betting Board, choose a side (Fighter A/B, Clan X/Y), enter their bet amount (within tier limits and their available GP), and confirm. GP is deducted. ● Odds System Determination: "How will odds be set for spectator bets? Options: Player-set odds (less common for fairness), System-calculated odds based on fighters' stats, gear (if visible), win/loss history, or even current betting volume (dynamic odds), or A pari-mutuel system where payout depends on the total pool and number of winning bets." ● Intuitive Betting Interface: "Design a clear UI for spectators to view upcoming/live matches, available bets, current odds, place their bets, and track their active bets and history." ● Proposition Bets ("Prop Bets"): ○ Types and Creation of Prop Bets: "Provide concrete examples: "First blood by Player A," "Fight lasts longer than X minutes," "Specific special attack K.O.," "Winner ends with X HP." Who can create these prop bets? System-generated for major events? Player-suggested? Mod-created? How are odds for prop bets determined?" ○ Availability: Clearly marked on the Betting Board for eligible fights (especially Mod-Hosted, high-tier duels, major tournament matches, or Trusted Host events where prop bet tracking is feasible). ○ OSRS-Specific Examples & Mechanics (requiring robust server-side combat log parsing): ■ First Blood (Damage Threshold): Bet on which fighter/clan achieves the first instance of PvP damage exceeding a minor threshold (e.g., >5 damage) to avoid chip damage confusion. ■ First Special Attack Landed (Weapon Specific): e.g., "Player A to land AGS spec first." System logs weapon ID, spec animation, and confirmed hit. ■ First Barrage/Blitz Freeze: System logs first successful binding spell cast by player X on player Y. ■ Number of Brews Used (Over/Under X): Tracks inventory usage of specific potion IDs (e.g., Saradomin Brew(4) ID) by each fighter. ■ KO with Specific Combo: e.g., "KO via AGS to Gmaul." Highly complex. Might involve checking for two distinct weapon hits from the same player on the target within a very short timeframe (e.g., 1-2 game ticks) leading to the KO. Initially for Mod-verified events. ■ Fight Ends in X Hits (Over/Under): For fast-paced pure fights. Counts total successful damage-dealing hits by the winner. ■ Lowest HP Remained (Dharok Fights): Bet on a fighter winning with <10 HP. System logs HP at the moment of opponent's death. ■ Most KOs (Clan Wars/Tournaments): Bet on which individual player achieves the most kills in a specific Clan War or throughout an entire tournament. ■ Will a specific Prayer be active at KO: (e.g., "Will Smite be active by winner at time of KO?"). ○ Odds/Pools: Each prop bet has its own separate betting pool and odds. Odds can be fixed by the system (e.g., for rare events) or pari-mutuel. A small server sync applies to each prop bet pool. ● Fighter Entry Fees (1v1 Duels): Both fighters contribute an agreed-upon GP amount. The maximum allowable entry fee is directly tied to the Trust Score tier of the lower-ranked fighter in the duel. Winner-take-all (minus optional small server sync) is the standard, emulating the OSRS duel arena stake feel. ● Clan Stakes (Clan Wars Only): Participating clans can agree to a mutual "Clan Stake." Maximum stake may also be influenced by the average Trust Score of participating clans. Emulates OSRS clan rivalries putting significant GP on the line. ● Parlay Betting (Future Enhancement): Players select winners for 2+ distinct events. If all selections win, payout is multiplied. Requires careful implementation regarding event timings and voided matches. ● Cross-Event Parlay Mechanics: "Clarify if players can parlay bets across different ongoing duels or tournament matches. Detail how the odds for these multi-leg bets will be calculated and displayed." ● Tiered Betting Pools & Trust Score Integration: ○ The Gambling Hub will feature distinct sections or filters for different betting tiers (e.g., "Bronze" "Silver" "Gold" "Platinum" "Royal" – names can be RoatPKz themed). ○ Each tier has defined min/max bet amounts, entry fee ranges, and critically, minimum Trust Score prerequisites for fighters to participate in or host events within that tier. ○ New fighters or those with lower Trust Scores are restricted to lower tiers with smaller potential prize pools and betting caps. As their Trust Score demonstrably rises through legitimate participation, they unlock access to higher tiers. ○ The maximum viewer betting pool that can be generated for a specific fight will also be capped based on the Trust Score tier of the participating fighters (specifically, the fighter with the lower Trust Score if they differ significantly). This prevents low-trust fighters from being vehicles for massive, potentially rigged, betting pools. ● Tournament Entry Fees: Collected upon registration. The majority forms the tournament's grand prize pool. A small percentage might be a server sync, and another small percentage could seed a special betting pool for the tournament's final match. ● Pool Mechanics and Structure: "How do these pools work? Do players buy into a pool with a fixed stake, with winners splitting the pot based on their contributions or a set structure? What are the tiers based on (e.g., stake amount, specific event types)?" 2.3. Reward Structures: Mechanics ● Bettor Winnings (Main Outcome & Prop Bets): Spectators who bet on the correct outcome (overall winner or specific prop bet) share a portion of the relevant betting pool, calculated based on the odds at the time of their bet or pari-mutuel distribution, after server sync. Automatically credited. ● Fighter's Pot (1v1 Duels): The winner of the 1v1 duel claims the entire sum of the combined entry fees paid by both fighters (minus any optional server sy). Automatically credited immediately post-match. ● Fighter/Clan Share from Viewer Bets (Main Outcome): The winning individual or clan receives a percentage of the post-sync main outcome viewer betting pool. (Prop bet pools typically do not contribute to fighter/clan share unless specifically designed to). Automatically credited. ● Trusted Host Commission (Trusted Host Facilitated Duels): Trusted Hosts receive a small, configurable percentage (e.g., 0.5% - 2%) of the total viewer betting pool (typically calculated after server sync) generated by the specific duel they successfully facilitate. This commission is awarded after the duel concludes and is verified as legitimate. ● Clan Stake Winnings (Clan Wars): The victorious clan claims the full sum of the agreed-upon Clan Stakes. Transferred to the winning clan's designated coffer or representative account. ● War Spoils (Clan Wars): Tradeable items dropped by defeated members of the losing clan during a bettable Clan War are collected and distributed among the participating members of the winning clan via the War Spoils Claim Interface (See Section 6.2). ● Tournament Prize Pools: Winners of bracket tournaments receive substantial prizes from entry fees, server contributions, and potentially a share of betting revenue generated by the tournament. Distributed according to the tournament's prize structure. ● Mod-Hosted Event Prizes: Unique or exceptionally valuable rewards determined by server staff for these special events. GP prizes auto-credited; item/cosmetic prizes might appear in a special claim interface or be awarded by staff. 2.4. Economic Management: Mechanics ● Server Money Sync (Viewer Bets): Applied automatically as a percentage deduction from the total viewer betting pool (main outcome and each prop bet pool) before any shares (fighter, host) or bettor payouts are calculated. Rate is configurable by admins (e.g., 1-5%) and should be transparent. ● Optional Syncs: ○ Clan Stakes: For extremely large stakes (e.g., >500M GP), a very small flat fee or 0.1-0.5% sync might apply. ○ War Spoils: A "processing fee" of 0.5-1% of the GE value of collected spoils could be a sync, or specific "junk" items from the spoils could be auto-removed before distribution. ○ Tournament Entry Fees: e.g., 5-10% of total entry fees collected could be a server sync. ○ Fighter Entry Fees (1v1): e.g., 1-2% of the total Fighter's Pot. ● Betting Insurance Premium Sync: If betting insurance is implemented, the premiums paid act as a money sync. ● Transparency: All sync rates and fees must be publicly viewable (e.g., in the Gambling Hub info section or on event listings). 2.5. Fight Customization & Rule Setting: Mechanics ● Rule Setting Interface (for Hosts): When initiating a 1v1 duel or Clan War, the host (challenger/Clan Rep/Trusted Host) will see a rule-setting interface. ○ Gear Rules: Radio buttons: "Predetermined Setup" (dropdown of server-defined loadouts like "Standard Dharok," "Max Melee NH," "Pure Void Ranger," "Ahrim's/Karil's Hybrid") or ("Own Gear"). ○ Stipulations Checklist: A comprehensive list of common OSRS PK rules: ■ Prayer: "No Prayers," "Protection Prayers Only," "No Smite," "No Redemption," "No Piety/Rigour/Augury," "Overheads Disabled for X seconds." ■ Inventory: "Limited Brews (e.g., 0-8)," "Limited Restores (e.g., 0-4)," "No Karambwans," "Food Type Restriction (e.g., Sharks Only)." ■ Spells: "No Ancients," "No Lunars (No Vengeance)," "No Teleblock," "No Entangle/Ice Spells," "Specific Spellbook Lock." ■ Combat Style: "Melee Only," "Magic Only," "Ranged Only," "No Special Attacks," "Limited Special Attacks (e.g., 1 per X seconds, or max 3 per fight)," "Specific Weapon Ban (e.g., No Blowpipe)." ■ Movement: "No Running (Walk Only)," "Arena Zone Restriction." ○ Custom Input (Limited Use): A small text field for highly specific, uncommon stipulations. These might require Trusted Host status or staff approval for general use to prevent overly complex or exploitable rules. ● Agreement Protocol: The challenged party sees all proposed rules and must individually check "Agree" for each stipulation or the entire ruleset. Any proposed change by either party re-prompts full agreement from the other. ● System Enforcement: As many rules as possible are system-enforced (e.g., preventing use of disabled prayers/spells, equipping predetermined gear, restricting movement to zones). For manually enforced rules (e.g., "no running for 30s," complex combo restrictions), these are best for Trusted Host/Mod events where observation is direct, or rely on player reporting (with video evidence) and severe Trust Score penalties if broken. ● Tournament Formats & Rulesets: Admins define these rigidly for each tournament template. Examples: ○ "Dharok PvP Tournament": Rules must specify: exact Dharok set pieces, axe, off-hand (if any, e.g., Dragon Defender/Avernic Defender or none), amulet, ring, cape (e.g., Infernal/Fire Cape), boots. Exact inventory (e.g., 6 Saradomin Brews(4), 3 Super Restores(4), 1 Stamina Potion(4), 12 Rocktails, 4 Karambwans, Vengeance runes). HP levels (e.g., all start at 99, or system forces to 1hp via a safe effect right before fight for max risk/reward feel). All other items/gear forbidden. ○ "Pure NH Tournament (1 Def)": Gear restrictions (e.g., Mithril Gloves, Climbing Boots, specific weapon tiers), spell restrictions (e.g., Ancients allowed, specific freezes), inventory setups tailored for NH PKing. 2.6. Integrity & Trust: Mechanics ● Community-Influenced Reputation System ("Elusive Trust Score"): A dynamic score for fighters, clans, and Trusted Hosts reflecting perceived fairness and reliability, with built-in safeguards against manipulation (Detailed further in Section 7.2). ● Comprehensive Anti-Rigging Measures: Multi-layered approach to prevent, detect, and penalize manipulation (Detailed further in Section 7). ● Direct Staff Oversight for Mod-Hosted Events & High-Stakes Finals: Ensuring fairness in critical matches. ● Trusted Host Accountability: Mechanisms to ensure Trusted Hosts operate fairly and transparently, tied to their own Trust Score and staff review. 2.7. User Interface & Experience: Mechanics ● Centralized Gambling Hub (NPC/Betting Board): For all event interactions. Betting tier limits based on Trust Score would be clearly communicated. ● War Spoils Claim System: For winning clan members. ● Tournament Bracket Display & Management Interface: Live updates for tournament progress. ● Clear Spectator Information: Comprehensive display of event details, rules, odds for main outcome and available prop bets, trust indicators, fighter entry fee amounts, and if a duel is facilitated by a Trusted Host. 3. Participant Roles & Interactions: Mechanics ● Fighters (1v1 Duels): Register for or initiate bettable matches, agreeing to and paying a mutual entry fee. Propose or agree to specific fight rules (gear, stipulations) with opponents. Compete for the Fighter's Pot, viewer bet share, and Trust Score. ● Clan Representatives & Participants: Issue and accept Clan War challenges. Negotiate and agree upon terms: participant numbers, gear rules, specific war stipulations, and Clan Stakes. Manage clan participation and Trust Score. Winners share in all relevant rewards. ● Tournament Entrants: Players who register (and pay entry fees if applicable) for bracket tournaments, adhering to the pre-set tournament rules (e.g., mandatory gear and inventory for a Dharok Tournament). ● Bettors: Analyze event details, participant stats, trust indicators, and odds. Place GP wagers on chosen victors (main outcome) and/or on specific proposition bets. ● Community Raters (Established Players): Provide feedback on fight fairness via a structured system, influencing participant Trust Scores, with mechanisms to prevent abuse of this role. ● Trusted Hosts: ○ Designated, highly reputable players (or staff-appointed) with a high Trust Score. ○ Can initiate and "host" 1v1 bettable duels, often for higher stakes or specific rule sets. ○ Responsible for ensuring clarity of rules and fair proceedings for fights they host. ○ Utilize a special interface ("Host Panel") to set up these hosted fights. ○ Their involvement provides an added layer of perceived security/legitimacy for bettors. ○ Do not typically participate as fighters in duels they host. ○ Incentives for hosting: Receive a predefined small percentage (e.g., 0.5% - 2%) of the total viewer betting pool from the specific duel they successfully facilitate. This rate is fixed by the server and transparent. ○ Accountability: Subject to the Trust Score system; negative feedback or evidence of misconduct leads to penalties, including revocation of Host status. ● Server Staff/Moderators: Oversee system integrity, investigate suspicious activity, moderate community feedback, and enforce penalties. Host and manage Mod-Hosted Special Events, defining all rules and prize structures. Oversee the setup and smooth operation of major Bracket Tournaments. Responsible for appointing/vetting Trusted Hosts and setting their commission rates. 4. Event Lifecycle: From Challenge to Payout: Mechanics 4.1. Event Initiation ● 1v1 Duels (Standard & Trusted Host): ○ Challenger/Host proposes terms, including rules and the Fighter Entry Fee amount. ○ Opponent reviews and must agree to all terms. ○ Both players pay their entry fee to the system escrow. Payment locks them into the fight. ○ Lock-in & Grace Period: Once entry fees are paid, a 60-second "Ready Up" countdown might begin. Both players must click "Ready." If one doesn't, they forfeit after the countdown. If both ready up, the fight proceeds to the arena. If the match is scheduled for a specific time, a 60-120 second grace or up to a 5 minute time period for appearance applies post-scheduled time. Notify all players entered receive a clear notification (e.g., in-game message/mailbox) before this period of time to ensure the player arrives. ○ Forfeiture Resolution: The present player receives the combined entry fees (minus optional sync). Viewer bets on that specific match are voided and refunded. The absent player's Trust Score is significantly negatively impacted ("No Show" FLAG). Repeated no-shows lead to temporary/permanent bans from the system. ● Clan Wars, Mod-Hosted Events, Player-Entered Bracket Tournaments: Initiation as previously detailed in (Section 2.1). ● Confirmation & Listing: All confirmed events are publicly listed on the Betting Board with comprehensive details, including fighter entry fees for 1v1 duels, Trusted Host information, and all active rules. 4.2. Betting Phase ● A timed window opens for spectators. ● Betting Board displays live pool sizes and odds for the main outcome and for each available proposition bet. ● Bets locked upon window closure or event start. 4.3. Event Commencement ● Participants moved to arena/war zone. ● Predetermined gear/rules enforced by the system. System checks for compliance before fight starts; discrepancies prevent start. ● War Spoils loot tracking activated for Clan Wars. ● System begins tracking metrics relevant to active proposition bets. 4.4. Event Conclusion ● System determines winner based on predefined conditions. ● System determines outcomes for all active proposition bets by querying detailed combat logs (See Section 2.2 for Prop Bet Mechanics). ● Loot Collection (Clan Wars): Items from the losing clan are collected. ● Fault/Exploit Check: Before final payouts, the system or staff (especially for flagged events) perform a final check for any detected critical server-side errors, exploits used during the fight, or confirmed rigging that would invalidate the outcome. 4.5. Payout & Distribution 1. Integrity Check & Voiding (If Necessary): ○ If an event is flagged and confirmed by staff as faulty (e.g., due to a critical server bug affecting the outcome), exploited by participants, or definitively rigged: ■ The event is declared "Void" or "No Contest." ■ All viewer bets (main outcome and prop bets) placed on this event are fully refunded to the bettors. This includes refunding any portion of the bet that would have been taken as a server sync. ■ Fighter entry fees may be returned to both participants, or forfeited by the guilty party to the innocent party/server, depending on the nature of the fault/exploit. ■ Clan Stakes are returned to the respective clans. ■ No fighter/clan share from viewer bets is paid out. No Trusted Host commission is paid for voided fights. ■ War Spoils are not distributed (or if collected, are returned/handled by staff). ■ Punitive measures (Section 7.3) are initiated against any guilty parties. ■ Bettors receive a clear notification (e.g., in-game message/mailbox) explaining that the event was voided and their bet has been refunded. 2. Fighter's Pot (1v1 Duels): If the event is valid, the combined entry fees are awarded to the winning fighter (or the present fighter in case of a forfeiture). An optional server sync might be applied here. 3. Server Sync (Viewer Bets): If the event is valid, calculated on the total viewer betting pool for main outcome and each prop bet pool. 4. Trusted Host Commission (Trusted Host Facilitated Duels): If the event is valid, calculated as a percentage of the total viewer betting pool (order of calculation relative to sync: e.g., PotAfterServerSync * TrustedHostCommissionRate). This is paid to the Trusted Host. 5. Fighter/Clan Share from Viewer Bets: If the event is valid, calculated on the remaining viewer betting pool after server sync and any host commission. 6. Bettor Payouts: If the event is valid, distributed from the final remaining viewer betting pool for main outcome and each prop bet. 7. Clan Stake Payout (Clan Wars): If the event is valid. 8. War Spoils Distribution (Clan Wars): If the event is valid, via claim interface. 9. Tournament Grand Prize Payout: If the event is valid. 10. Mod-Hosted Event Prize Payout: If the event is valid. 11. GP winnings automated; loot/special prizes claimed/awarded. Announcements made. All financial transactions meticulously logged. 4.6. Post-Event Actions ● Trust Scores updated based on metrics and community feedback, with anti-manipulation checks. Events declared void due to rigging by a participant will severely negatively impact that participant's Trust Score. ● Logs archived for review. 5. Financial Model & Economic Considerations ● Viewer Betting Pool Distribution (Trusted Host Facilitated Duel Example): 1. TotalViewerPot collected. 2. ServerSyncAmount = TotalViewerPot * ServerSyncRate. 3. PotAfterServerSync = TotalViewerPot - ServerSyncAmount. 4. TrustedHostCommissionAmount = PotAfterServerSync * TrustedHostCommissionRate. 5. PotAfterHostCommission = PotAfterServerSync - TrustedHostCommissionAmount. 6. WinnerShareFromViewerBets = PotAfterHostCommission * WinnerShareRate. 7. BettorPrizePool = PotAfterHostCommission - WinnerShareFromViewerBets. ● (Other financial model aspects as previously defined, covering Fighter's Pot, Clan Stakes, War Spoils, Tournament Pools, Mod Event Pools, and Configurable Rates.) 6. Interface & User Experience 6.1. Gambling Master NPC / Betting Board Interface ● Central Hub for: Viewing all event types (1v1, Clan Wars, Mod Events, Tournaments) across tiers. Placing bets. Displaying comprehensive event details, including all custom rules, tournament rulesets (e.g., "Dharok Tournament - Standard Set Provided"), odds (main outcome & prop bets), trust indicators, fighter entry fee amounts, and Trusted Host facilitation details (including commission rate if public). ● Registration/Challenge Functions: For 1v1/Clan Wars (with rule proposal/agreement and entry fee payment). Tournament Registration Tab (displaying tournament-wide rules and collecting entry fees). Interface for Trusted Hosts to set up and manage their facilitated duels. ● Information Section: Explaining all system mechanics, rules, payout structures, the trust system, prop bets, and anti-rigging policies. 6.2. War Spoils Claim Interface ● Accessibility: Only for participating members of the winning clan after a bettable Clan War. ● Display: Shows a list/grid of all collected items from the losing clan, with icons and quantities. ● Functionality: Clearly indicates whose turn it is to pick (if using round-robin). Allows selection of one item per turn. Shows remaining items. Displays a countdown timer for the overall claim period. Option to "Pass Pick" or "Auto-Distribute Remaining" if desired by clan leadership. ● Finalization: Button to "Finalize & Send All Claimed Items to Bank" once all personal picks are done or the overall claim period ends. 6.3. Tournament Bracket Interface ● Visual display of the live tournament bracket, updating in real-time. Shows upcoming matches, past results, contestant progression, and links to individual matches for betting or viewing details. 6.4. Spectator HUD or (Viewer Participant Area Overlooking The Fight Arena Specified For Bettors & Spectators) ● Minimalist, toggleable overlay during live events: ○ 1v1: Fighter names, HP, potentially active key stipulations (icons). ○ Clan Wars: Clan names, remaining members on each team, key objectives (if any). ○ Tournament: Current round/match details. ○ Active Prop Bet Tracker (Optional/Subtle for high-profile events): e.g., "First Blood: [Player A] | Brews Used (A/B): 2/1 | Duration: 01:15." 7. Anti-Rigging & System Integrity (Multi-Layered Defense): Operational Details 7.1. Preventative Measures ● Strict Prohibition of Self-Betting & Collusive Betting Rings: (As defined previously, including alt-detection). For Mod-Hosted Events & Tournaments, staff can explicitly bar participants from betting on any match within their own event/tournament. ● Randomized Matchmaking (Queue System & Tournament Brackets): Key anti-rigging for tournaments. ● Randomized Fight Stipulations (Optional): (As defined previously). ● Fighter/Clan Cooldowns (Direct Challenges): Limits how often the same two entities can fight each other via direct challenge to prevent Trust Score farming or repeated rigged matches. ● Betting Limits & Caps Tied to Trust Score & Event Tier: ○ Maximum individual bet amounts are enforced per event. ○ The overall betting pool cap for a specific 1v1 duel or Clan War is dynamically limited by the Trust Score tier of the participating entities (the lower score prevailing if there's a mismatch). This directly prevents new or untrusted players from being involved in generating excessively large prize pools that could incentivize large-scale rigging. ● Mandatory "Cool-off" Period/Lower Caps for New/Low-Trust Bettors: Prevents new or suspicious accounts from making massive bets immediately, requiring a period of legitimate betting activity to unlock higher limits. ● Rule Transparency & Locking: All active custom rules and tournament-specific rules (like mandatory Dharok sets) must be clearly displayed and locked before betting opens. The system must prevent rule changes after bets are locked. ● Standardized Rule Options & Tournament Presets: Providing common, well-defined rule options and tournament presets (like "Dharok Tournament Rules") ensures consistency and clarity, reducing ambiguity that could be exploited. ● Minimum Fight/War/Tournament Match Activity Metrics: ○ Examples: For a 1v1 duel to be valid: Both participants must deal/receive at least X% of their max HP in damage (e.g., 30%); OR the fight must last at least Y seconds (e.g., 20 seconds), unless a clear, fast KO occurs that involves significant damage exchange (e.g., a max hit Dharok KO); OR a minimum number of attack attempts/prayer switches/movement actions must be registered. ○ Flagging & Review: If metrics aren't met, the fight is automatically flagged. Payouts (fighter pot, viewer bets, host commission) are paused pending staff review. If deemed a "non-fight" or clear throw, the event is voided, entry fees might be returned or confiscated, and Trust Scores are heavily impacted. ● Visual Anonymity for Fighters During Betting (Optional/Specific Queues): For certain non-premier queued fights, fighter names could be hidden from bettors until after bets are locked (e.g., "Fighter A [Gold Trust] vs. Fighter B [Silver Trust]"). This makes it harder to collude with a specific friend if their identity in the match-up isn't known beforehand. ● Direct Staff Oversight for Mod-Hosted Events & Key Tournament Matches: Provides a strong deterrent against rigging in these specific high-profile matches. ● Entry Fee Forfeiture Enforcement: Strict and automated enforcement of entry fee forfeiture for no-shows to discourage accepting fights without intent to participate. ● Trusted Host Vetting & Oversight: ○ Rigorous process for selecting Trusted Hosts (e.g., proven long-term high Trust Score, staff nomination, community endorsement, application process detailing game/PK knowledge). ○ Clear guidelines, limitations, and expected conduct for Trusted Hosts. Revocation of status for abuse or negligence. ○ Transparent Commission Rates: Trusted Host commission rates should be fixed by the server and clearly communicated. 7.2. Detective Measures & Reputation System ● Community-Influenced Fighter/Clan Reputation (Elusive Trust Score) - Advanced Integrity & Anti-Manipulation Measures: ○ Core Principle: An evolving score reflecting perceived reliability. Its exact calculation is kept opaque ("elusive") to prevent direct gaming. It is influenced by automated data and heavily moderated community input, with multiple safeguards against manipulation. ○ Automated Inputs - How they affect score (Enhanced): ■ Fight history (number of fights, win/loss consistency against a diverse range of opponents with varying Trust Scores). ■ Diminishing Returns for Repeated Opponents: Trust Score gains/losses from fighting the same opponent repeatedly within a short timeframe (e.g., < 7 days) are significantly reduced after the first few encounters (e.g., 2-3 fights). This heavily discourages win-trading with friends to boost scores. ■ Opponent Diversity Modifier: Small, cumulative Trust Score bonuses for consistently fighting a wide array of unique opponents over time. ■ Adherence to "Minimum Fight Activity/Engagement" metrics. Failure results in negative impact or no positive change. ■ Absence of confirmed rigging reports from staff investigations. ■ Performance against varied opponents/Trust Scores (e.g., consistently losing to much lower-ranked players when high bets are involved, especially if activity metrics are low, is a major negative flag). ■ Tournament Performance: Consistent deep runs in legitimate tournaments = positive. Repeated first-round exits with low activity = neutral or slight negative if pattern emerges. ○ Community Feedback Mechanism - Anti-Abuse Enhancements: ■ Eligibility to Rate: Stricter criteria: e.g., minimum X hours of active playtime on RoatPKz (e.g., 100+ hours), minimum number of varied bets placed in the system (e.g., 50+ bets on 10+ different events), account linked to a verified forum/Discord account (if feasible), minimum own Trust Score (e.g., "Bronze" or higher) to rate others. This makes mass alt account rating abuse much harder. ■ Feedback Type & Moderation: After a bettable fight, eligible spectators might be prompted to give a simple "Rate Fairness of [Fighter A/Event]: Fair / Suspicious / Unsure." An option for a brief, structured comment (e.g., selecting from predefined concerns like "Possible intentional underperformance," "Unusual item usage/tactics," "Host mismanagement (if applicable)") is crucial. All "Suspicious" ratings and comments are mandatorily queued for staff review before significantly impacting a score negatively. ■ Rate Limiting & Cooldowns for Raters: Prevent individual players from spamming ratings for the same fighter/clan/host too frequently. A player might only be able to rate a specific entity once per day/week, or after observing a certain number of their events. ■ Detection of Coordinated & Retaliatory Rating (Enhanced): ■ The system analyzes rating patterns to identify groups (friends, clanmates, alts based on IP/trade/chat logs, shared betting patterns on obscure fights) who exhibit statistically improbable rating behavior (e.g., always upvoting each other, always downvoting specific rivals immediately after a loss). ■ Ratings from accounts flagged for coordinated behavior are heavily de-weighted or temporarily nullified for Trust Score calculation pending staff review of the raters themselves. ■ Sudden spikes in negative ratings for a player immediately after they defeat a well-known player or clan will be flagged for review as potential retaliatory rating. ■ Weighting & Normalization (Enhanced): Feedback from community members with a long history of providing consistent, accurate, and unbiased ratings (an internal "Rater Reputation Score" could be tracked by staff) carries more weight. Ratings are normalized against a rater's historical rating patterns to identify outliers (e.g., someone who rates 99% of fights "Suspicious" will have their individual suspicious ratings carry less weight). ○ Trust Score Dynamics & Anti-Gaming (Enhanced): ■ Score Decay/Activity Requirement: Trust Scores might slowly decay over periods of inactivity in bettable events (as fighter or host), requiring ongoing participation (e.g., X fights/hosted events per month) to maintain a high score. This prevents players from building a high score and then "cashing out" by rigging fights or becoming inactive hosts. ■ Volatility Control & "Probation" for Rapid Climbs: Rapid, large swings in Trust Score (either up or down) based on a small number of recent events or ratings would be dampened or flagged for review. New accounts or those with rapidly increasing Trust Scores might enter a "probationary" higher tier, where their betting/hosting limits are still somewhat restricted compared to established players in that tier, until their score stabilizes over more diverse interactions and time. ■ Hidden Sub-Metrics & Algorithmic Obscurity: While a general trust tier is visible, the underlying components and their exact weightings remain hidden to make it harder to pinpoint how to artificially inflate the score. The system might use decoy metrics or random noise in non-critical internal calculations to further obscure the exact formula. ■ Impact of "No Contest" / Voided Fights: Fights voided due to suspected rigging, extremely low activity, or mutual agreement to avoid a legitimate contest should result in a neutral or negative Trust Score impact for the involved fighters, never positive. If one party is clearly at fault for the voiding, only they receive the negative impact. ○ Impact (Trust Tiers & Privileges): Translates to visible trust tiers (e.g.,"Bronze" "Silver" "Gold" "Platinum" "Royal" - Very Trusted," "Red/Flagged - Untrusted/Under Observation"). Higher tiers grant access to higher stakes events, higher betting/entry fee limits, lower server sync rates on their fights (as a reward), eligibility to become a Trusted Host, or entry into exclusive events. Lower tiers lead to restrictions (mandatory stipulations, lower bet/entry fee caps, increased scrutiny, temporary suspension from system). ○ Staff Oversight & Manual Adjustment (with Audit Trail): Staff retain the ability to investigate and manually adjust Trust Scores in clear cases of proven manipulation or system abuse, with logged justifications for such actions. These logs are auditable by higher staff. ○ Moderation of Feedback: All negative community reports and detailed feedback comments are reviewed by staff to prevent abuse (e.g., false reporting, slander). Reporter identities are confidential from the public and reported parties. ● Comprehensive Logging & Analysis (Enhanced): ○ All Trust Score modifications, with reasons (automated trigger, community feedback batch, staff adjustment). ○ Logs of rater activity, their own Trust/Reputation, and any flags for coordinated rating. ○ Cross-referencing betting activity (amounts, on whom, by whom) with Trust Score changes, community ratings, and fight outcomes to find correlations indicative of collusion or manipulation. ○ Detailed logs for all prop bet triggers and outcomes. ● Pattern Recognition & Anomaly Detection: ○ System flags scenarios like a fighter's performance metrics (damage dealt/received, accuracy, APM, prayer usage, food/potion consumption rates) dropping significantly below their established average only when fighting specific opponents or when specific bettors are heavily invested. ○ Detection of "Shell Accounts" used for betting, rating, or as fight participants, based on creation date, playtime, wealth accumulation patterns, IP/client data, and minimal legitimate server interaction outside the gambling system. ○ Flags for unusual betting distributions (e.g., 95% of a large pool on a massive underdog with a low Trust Score against a high Trust Score favorite). ● Player Reporting System & Secure Whistleblower Channel (Enhanced Detail): ○ In-Game Reporting Tool: Accessibility A dedicated button/command (e.g., ::reportfight or an option in the Gambling Hub event history). Process 1. Player selects the specific fight/event ID they are reporting from a recent history list or by manual input. 2. Player selects the accused players/hosts involved. 3. Player chooses a category of suspected abuse (e.g., "Match Fixing/Throwing," "Rule Exploit," "Trust Score Manipulation," "Collusion," "Host Misconduct," "Exploiting Prop Bet"). 4. Player provides a detailed description of the suspected activity (min/max character limit, encouraging specific observations). 5. Crucially, prompt for and allow easy attachment/linking of evidence: Option to link to a video clip (e.g., player uploads to YouTube/Streamable/Medal.tv and provides link), or if server-side fight recording is implemented, allow players to reference a specific fight ID and timestamp range. Screenshots can also be attached for certain abuses. 6. Report submitted to a dedicated staff queue, timestamped and categorized. ○ Staff Review Interface for Reports: ■ Reports are categorized, prioritized (e.g., by severity, number of similar reports, value of event). ■ Staff can view all associated data: fight logs, combat replay (if available), betting patterns of accused and reporters, Trust Scores of all involved, community feedback for that fight, historical interactions between accused parties. ■ Staff can mark reports as "Pending Review," "Investigating," "Resolved - Action Taken," "Resolved - No Action (Insufficient Evidence/False)," "Duplicate." ○ Feedback to Reporter (Limited & Generic): To encourage reporting and manage expectations, a generic automated message: "Your report for Event #XYZ has been received and is under review. Thank you for helping maintain fair play." Further specific details of actions taken are generally not disclosed to individual reporters to protect privacy and operational security, unless it's part of a broader public announcement of a major rigging bust. ○ Secure Whistleblower Channel (Off-Game): For highly sensitive information about large-scale rigging operations, staff misconduct related to the system, or critical exploits. This could be a dedicated, encrypted email address or a secure form on the RoatPKz website/forum, managed only by top-level administration/server owners. Assurances of anonymity and protection for legitimate whistleblowers are paramount. Potential for significant (non-GP, e.g., unique untradeable cosmetic, real-world server store credit) rewards for information leading to the dismantling of major rigging rings or prevention of significant economic damage. ● Delayed Payouts for Highly Suspicious Fights/Tournament Outcomes (Use Sparingly): If a fight is automatically flagged with multiple severe anomalies (e.g., failed activity metrics, massive betting shift just before close from suspicious accounts, multiple "Suspicious" community ratings from highly trusted raters), the automated payout script is paused for that specific event. Staff are immediately alerted. They have a defined window (e.g., 1-6 hours) to conduct an initial review. If cleared, payouts proceed. If rigging is confirmed, penalties are applied. If inconclusive but still highly suspicious, a "No Contest" might be declared, and all stakes/bets refunded. This is a high-impact measure used sparingly and with clear server communication if invoked for a major event. ● Analysis of Rule Impact: Staff may analyze if specific custom rule sets or tournament formats are frequently associated with suspicious outcomes, potentially flagging certain rule combinations for review or disallowing them if they prove to be consistently exploitable. 7.3. Punitive Measures (Zero Tolerance for Confirmed Abuse) ● Immediate & Severe Consequences for ANY System Abuse: This includes rigging fights (main outcome or prop bets), manipulating prize pools (e.g., through collusive entry fee forfeitures), exploiting game mechanics or system bugs for unfair gain, and any confirmed attempt to artificially manipulate one's own or others' Trust Scores (e.g., coordinated false reporting, win-trading solely for score manipulation). ● "No Contest" Rulings / Tournament Disqualifications / Forfeiture Reversals & Bettor Refund Mandate: ○ Staff can void fights/matches, mandate full refunds of all viewer bets (including any server sync portion), return/confiscate entry fees/stakes, and disqualify participants/teams from tournaments if rigging, exploitation, or critical system faults are proven or strongly suspected based on overwhelming evidence. ● Tiered Penalties (Applied Swiftly for Confirmed Abuse): ○ First Strike (Major Offense - Rigging Fights/Pools/Trust Scores): ■ Immediate and permanent "Disgraced" or "Blacklisted" Trust Score status, rendering the account ineligible for any future participation in the gambling ecosystem. ■ Forfeiture of all winnings, stakes, entry fees, and commissions from any related event(s). ■ Full confiscation of illicitly gained wealth from the abusive activity, traced through all associated accounts (alts, mules). This may involve rollback of trades if necessary and feasible. ■ Extended (e.g., 3-12 months) or permanent suspension from all RoatPKz gambling system features (betting, hosting, participating). ■ Potential for a lengthy server ban (e.g., 30 days to permanent) depending on severity, scale, and prior offense history. ○ Repeat Offenses / Large-Scale Collusion / Exploiting System Mechanics for Major Gain: Permanent server ban for all involved primary and alternate accounts. No appeals. All associated wealth confiscated. ● Public (Anonymous) Announcements: Informing the community about actions taken against rigging and confirming when bettor refunds have been processed for a voided event. This reinforces trust in the system's ability to self-correct. ● Abuse of Rule Setting/Exploitation of Tournament Rules/Abuse of Trusted Host Position: Treated as a serious offense with consequences aligned with rigging. Revocation of Trusted Host status and forfeiture of any improperly earned commissions would be primary penalties, in addition to other sanctions. ● Penalties for Trust Score Manipulation (Reiteration): Confirmed attempts to artificially inflate or deflate Trust Scores (e.g., through coordinated false reporting by groups, win-trading specifically for score, using alt accounts to rate) will be treated as a major offense subject to the "First Strike" penalties or higher. 8. Other Potential Enhancements & Future Development Ideas ● Parlay Betting: Bet on outcomes of multiple events. ● Live Betting (Very Advanced): Bets during fights with dynamic odds. ● Advanced Proposition Bets: More complex in-fight event bets. ● Fighter/Clan Tiers & Leaderboards: Official rankings (including Dharok Tournament specific). Seasonal rewards. ● Bounty System: Server or player-funded bounties. ● Sponsored Events: Player/clan sponsored prize pool additions. ● Cosmetic Rewards: For high rank/trust, betting streaks. ● Enhanced Spectator Tools: Focus cam, gear display, interactive cheering. ● Fight Replays & Highlights: Record and share notable events. ● "Gambler's Tokens": Redeemable for cosmetics/perks. ● Event-Driven Lotteries: Bet-based lottery entries. ● Betting Insurance: Pay premium to insure a bet portion. ● Community Prediction Pools (Non-GP): For engagement. ● Server "Odds Boosts": Occasional improved payout odds. ● Staff-Sanctioned "Grudge Matches": Moderated high-profile rival fights. ● "War Chest" Contributions (Clans): Members contribute to clan stakes. ● Loot Share Options (Clans): More autonomy in War Spoils division. ● Automated Tournament Scheduling: Recurring daily/weekly tournaments. ● "King of the Hill" Style Events: Continuous defense events. ● Team-Based Tournaments (2v2, 3v3, 5v5): Ad-hoc team brackets. ● Rule Presets/Templates: Hosts save/load common rule configs. ● Community Voted Rules for Special Events: Community input on stipulations. ● Specific Currency Betting: Option for PKP, etc., in specific tiers. ● Wilderness Hotspot Betting (Dynamic): Short-term bets on area control/PKs. ● Discord Integration: Announcements, live odds, sign-ups. 9. Conclusion & Vision for the Future This definitive gambling and tournament ecosystem blueprint for RoatPKz, with its enhanced focus on tying betting limits directly to a rigorously protected Trust Score, implementing near-impregnable anti-manipulation measures, and ensuring a fair refund process for bettors affected by compromised events, aims to create a truly fair, competitive, and engaging PvP betting environment. The success of this complex system hinges on exciting gameplay, robust economic management, an unwavering commitment to integrity through comprehensive and evolving anti-rigging strategies including a zero-tolerance policy for any abuse and a dynamic, community-involved trust system that is itself heavily safeguarded against manipulation. Continuous monitoring, adaptation to new player behaviors, and transparent communication will be paramount to maintaining the system's credibility and ensuring it remains a prized feature of the RoatPKz experience for years to come.

Thankyou, all for the support and thoughtful replies. I do understand it is a lot of information and a large sum of information about many mechanics and systematic views of these suggestive ideas. This is something I will be continuing to update and edit. It might consist of a lot here but i feel like in the case of this type of system there is much needed attention to detail and extensive mechanics that go into these type of suggestive updates. Any Supportive thoughts and ideas to add to this would be appreciated very much.

Nice suggestion bro 😎 We are always open for new suggestions & feedback to improve even more!

Wow, what a beast of a post. Nice job putting all of this together. I do think there is some good potential here. I would say this would likely need to be scaled down on a massive basis. The system you've described would take a ton of development time to properly implement, not to mention the upkeep and maintenance that would be required. I think it would be awesome, but this is just a lot. I'd recommend tuning this down quite a bit and making a similar post with a simpler system that still runs with the core idea.

Very detailed and well explained suggestion, They should really take a few into consideration. Thank you for caring so much and taking your time to help the server become better.

Lets go fellas

Im not talking down on u , this is roatpkz brother if u were a bit longer around u would understand me , ur suggestions are def cool but its not that ez to put it out there . Greetings , G

Buy 2025 halo pm - O N i B LA

Poor saymon 😆 Next 1 will be great ♥️💪🏼

AFTER A LONG ROAD WE CAN SAY WE HAVE MADE IT!!!!!!!! 99 COOKING ON ROAT PKZ LIKE COMMENT SUBSCRIBE FOR MORE CONTENT RANDOM COMMENT SELECETED