Closed madcowfred closed 8 years ago
HI NERAUD. I've finally added proper support for the 'cuid' JSON field to PADherder - there's now a new 'pad_id' field on Monster user-api objects:
{ "id": 5918, "monster": 4, "note": "", "priority": 1, "current_xp": 4406, "current_skill": 1, "current_awakening": 0, "target_level": 99, "target_evolution": 1919, "plus_hp": 0, "plus_atk": 1, "plus_rcv": 0, "pad_id": 784 },
The Upload JSON code in PADherder handles cuid->pad_id monsters first then uses the old fuzzy matching on any leftovers (setting pad_id=cuid on best guesses), should be simple enough to do that for PADListener too.
HI NERAUD. I've finally added proper support for the 'cuid' JSON field to PADherder - there's now a new 'pad_id' field on Monster user-api objects:
The Upload JSON code in PADherder handles cuid->pad_id monsters first then uses the old fuzzy matching on any leftovers (setting pad_id=cuid on best guesses), should be simple enough to do that for PADListener too.