Same root cause as #311, and the items are back.

The disconnect was not the cause — it only made the damage visible. The save guard is the server-side check that refuses a save it believes was tampered with, and it holds a bounds table of the highest each stat can legitimately reach per item. 7,523 of its 10,485 entries were generated without base stats, so for those the check treated the item as zero-attack armour and invented a ceiling of 21 attack. Pajé's Staff is 25 attack, Indigenous Bow and Dom Pedro I's Sword are 35 — each legitimately over a cap we made up.

That is exactly why Lv and EXP were kept. The guard never rejected the save; it accepted it with the inventory reverted to the last stored copy. Level, EXP, quests and mesos wrote through normally. Only the bag, equipped slots, storage and ETC rolled back — and because one bad item reverted the WHOLE collection rather than just itself, everything else in the bag went with it. It was a deadlock too: the guard forgives an item once it has seen it stored, and the revert meant these never could be. Logging back in simply showed you the last copy that had survived.

Both halves are fixed and live: an entry with no real stat data no longer gets a fabricated cap, and a rejected entry is corrected in place instead of reverting the collection.

Restored by hand on Evil, stats taken from the catalog — Pajé's Staff, Stolen Fence, Maple Claw, Dom Pedro I's Glove, Blood Snowboard, Dom Pedro I's Sword, Indigenous Bow, Maple Bow, Pink Flower Tube, The Stars and Stripes.

I swept all 661 characters against the old rule rather than trust the reports to be the full list. Five were ever affected — Evil, Love, Red, Nothing, Aeris — and all five now save cleanly, verified on the live database.

Evil's quest ETC items are all present again. If a specific one is still short, name it and I will grant it directly.

Correction to my reply above — see #311 for the longer version.

I got the figure wrong (it is 2,071 of 5,249 equip entries, not 7,523 of 10,485 — the larger count swept in items that have no stats by definition and are never stat-checked), and more importantly I stopped one layer short of the cause.

Those weapons should never have been judged against an invented ceiling at all. The game's catalog has carried their real attack all along; the bounds table is GENERATED from that catalog, and nobody had re-run the generator since the Brazilian items gained their stats. The table was stale, and a stale entry is what made the guard invent a cap of 21.

Regenerated, they read as real weapons with real bases and their ceilings are 70, 70 and 60 against actual values of 35, 35 and 25 — nowhere near tripping. Verified against all 661 characters on the server with the grandfather rule switched off so nothing could be masked: nothing anywhere falls outside the new table.

There is now a test that re-derives every equip entry from the catalog and fails the build if the table falls behind again. I staled the table on purpose to watch it fail before trusting it.

Everything in my earlier reply about why Lv and EXP survived while the bag rolled back still holds, and the guard-side changes stay regardless. But the real repair is that the table is current again.