Die4Ever / Die4Ever/mods4ever-web

fix map parsing from death events

Open
#17 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

where did `Autoplay` come from? we shouldn't be using that for the map name, we have it in the json

EVENT: Autoplay.JCDentonMale0: {"type":"DEATH","victim":"JC Denton","victimBindName":"JCDenton","killerclass":"GuntherHermann","killer":"Gunther Hermann","dmgtype":"Flamed","PlayerName":"JC Denton","map":"04_NYC_BATTERYPARK","mapname":"NYC - Battery Park","mission":"4","TrueNorth":"16384","PlayerIsFemale":"False","GameMode":"Original Story","newgameplus_loops":"0","loadout":"All Items Allowed","location":"-3593.155762,1315.968506,363.899994"}

the deaths table doesn't actually have a map column though, it's joined to logs

Contributor guide

No contributing guide indexed for this repository

Research direction

Start from the death-event parsing entry point and inspect how the JSON `map` and `mapname` fields are handled. Follow how deaths are joined to logs and verify that the deaths view reports the map name from the event JSON rather than `Autoplay`; done means the provided event produces the expected `NYC - Battery Park` map name.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.