Right now it processes any new kills in the order received from the API (or it is thrown into a dictionary at some point, and loses all order)
Consider sorting by date such that the latest message, or kill in the kill-message as posted is on the bottom, with later kills ascending
At the moment it's going into a list, and seems to be writing the most recent first. Reversing the list before posting should solve this, and I'll test it on a local version.
Right now it processes any new kills in the order received from the API (or it is thrown into a dictionary at some point, and loses all order) Consider sorting by date such that the latest message, or kill in the kill-message as posted is on the bottom, with later kills ascending