RIFT COMBATLOG PARSER
Rules & Guidelines
These rules define what is and is not permitted to be uploaded on PrancingPika, and what qualifies for the “Top” leaderboards. Keep logs honest so rankings stay meaningful.
These rules pertain to what is and is not permitted to be uploaded on PrancingPika.
Uploads & integrity
- Do not use broken or knowingly bugged abilities to gain an unfair advantage on charts/rankings.
- Exploitable abilities may remain unfixed; abusing them still invalidates rankings (example: Frostkeeper “Hailblast”).
- Do not upload prior-tier raids — upload current-tier only.
- Current tier (example set): Bastion of Steel, Intrepid Rise of the Phoenix, and Tartaric Depths (Normal Mode).
- DPS Dummy parses are allowed (recommended: level 70 / end level dummies).
- Absolutely do not toggle /combatlog on/off once an encounter has begun. Keep it enabled for the full session from start to finish.
- No edited logs or “half parses”. Manual modifications or fudging segments is grounds for removal.
Session uniqueness
- Each Raid Lock ID is its own session — no duplicates.
- If your Raid ID is “123”, only one combatlog from Raid ID 123 should be upload.
These rules apply in addition to the main rules above. Violations may remove a parse from Top and can hide the session from public views.
General details
- Date cutoff: only parses after 01-01-2020 are accepted. (You can re ReUpload old logs)
- Raid zone limitation: All Prophecy of Ankhet raid are included (for Top).
- Parser cadence: backend runs every timmes you upload a logfile.
Top rules
- Absolutely NO second Lava Field or Flaring Power buff after a raid death within five minutes (“exhausted debuff resetting”). This does not forbid follow-up buffs once the five-minute debuff wears off.
- No stacking broken/bugged buffs to create skewed DPS (example: stacking multiple Primal Savagery buffs).
- No intentional skipping of hard-timed, hard-percent-set, or unskippable raid mechanics.
High raid DPS or server issues can cause delayed/queued mechanics — that is not the same as forcing a boss to skip an invulnerability mechanic.
Example: Azranel’s “Defensive Spin” starts at 45% then every 44 seconds. The initial 45% activation cannot be skipped; skipping it violates Top rules.
Automated checks detect common forms of log manipulation and suspicious patterns.
If an upload never shows up in your session list, it’s likely because something was detected. If you believe it’s a false positive, reach out on Discord.
What it checks (examples)
- Edited logs (files modified after being generated by the game).
- “Double burst” or bug patterns with Wild Storm.
- Some impossible damage/healing values.
Fair play enforcement — transparent actions, consistent rules, and an open Discord for discussion.
If rules are not respected, moderation is progressive and aims to keep the leaderboards clean without punishing honest mistakes.
What happens when rules are broken
- First step: suspicious or non-compliant scores can be removed from public leaderboards.
- If it continues: the uploader account can be banned from uploading.
- Severe or repeated abuse: actions can target the offending in-game character (IG player) involved in the manipulation/abuse.
Impartiality
I’m impartial. Even if I play in raids myself, the goal is never to boost one guild over another. This project exists to bring back a baseline of competitiveness and trust across all raids.
Need to discuss a decision?
If you think something was misclassified, or you want to contest a removal, my Discord is open. We can review the context together and keep things fair for everyone.