FAuction

Some auctions (and items sitting in the expired-items view) could no longer be cancelled or claimed. The console showed an error such as:

[FAuction] Auction X could not be deleted from the database ; kept on the market instead of being lost from the cache for nothing.

Cause: on SQLite, new listings were assigned an id guessed locally instead of the one the database actually generated. Once the highest-id listing had ever been sold or removed, that guess fell out of sync with the database — so any new listing added afterward got an id that didn't match any real row, making it permanently impossible to delete or claim.

Fix: new auctions and expired items now always use the id the database itself assigned. No more drift between the in-memory cache and the database, and no more stuck listings.

If you were affected, existing stuck items should resolve themselves once you sell/cancel/withdraw them again after updating; any that were already orphaned may need a manual database check (see the plugin's SQL tables if in doubt).