JobExperiencesUpdateEvent

WHAT TO DO WHEN YOU RECEIVE IT: for each entry, create or overwrite that one job; leave every other job alone. SEND NOTHING BACK - no handler of this message builds a request, and a static walk through everything it notifies reaches none.

WHEN IT ARRIVES. It follows whatever earned the experience - harvesting, crafting - and no request asks for it.

The server's update of the character's own job progress. It carries one JobExperience per job concerned.

IT IS AN UPSERT PER JOB, NOT A SNAPSHOT. For each entry the client looks the job up by JobExperience.job_id, creates the record if it has never seen that job, and overwrites its level, experience and both floors. Jobs that are not listed are left exactly as they were. A message listing one job says nothing about the others - do not clear your state.

ONE NOTIFICATION PER ENTRY. After updating each job the client raises a job-experience notification carrying that job's id, and the crafting and smithmagic windows refresh their gauge when the id is the job they are showing.

THIS IS ONLY YOUR OWN CHARACTER. The progress of another player - the crafter on the other side of a cooperative craft - arrives in a different message that carries a single JobExperience and that player's id.

SEVERAL BUILDS PAD THIS MESSAGE. Beside the real list the schema may declare a second list of the same type, an optional int64, a bool or a string. The client reads none of them; only JobExperiencesUpdateEvent.experiences carries data.