RIFT COMBATLOG PARSER
Prancing Pika
Upload your logs, parse sessions automatically, and compare performance with clean, fair metrics (including boss-only windows when fights include waves/adds).
If you think there's an issue, please reach out on Discord.
The parser is new and it comes with an anti-cheat system. Please be patient and a bit forgiving while it’s being tuned — and don’t hesitate to ask why a run didn’t show up.
A few important notes :
- - Large “ninja pulls” (more than ~3 seconds before the real pull) can break the timing, ruin your parse, and may trigger the anti-cheat.
- - Pulling a lot of adds and killing the boss with them (without a wipe/reset) can confuse encounter detection. In that case, the parser may not recognize the exact fight window and can set the combat aside.
If you think your run was flagged incorrectly, reach out and we’ll review it together.
Designed to feel like the OG Prancing Turtle : data-first, readable, fast.
How it works
- Enable logging in-game: /combatlog
- Upload the log (or zipped folder)
- Get your scores and compare on leaderboards
Sessions
Clean boundaries
Metrics
DPS / HPS
Special
Boss-only
Other things :
The OG will always be Prancing Turtle
Keep rankings meaningful. Logs must reflect real gameplay.
Core rules
- No knowingly bugged/exploitable abilities to gain unfair advantage.
- Do not toggle /combatlog mid-encounter.
- No edited logs or “half parses” intended to skew leaderboards.
- One public “master” upload per unique session/raid ID.
Anti Cheat
I have made an anti cheat system to detect some common forms of cheating or log manipulation. If your uploads never shows up in your sessions list, it's probably because something was detected. If you think a mistake has been made, please reach out on Discord to discuss.
What doeas it do ?
- Detects edited logs (logs that have been modified after being generated by the game)
- Detects double burst or some other bug with the Wild Storm
- Detects some forms of impossible healing or damage values