Data too long for column '<name>'
Something was too big for where it was being saved, so it was not saved at all — inventories are the usual case.
Do this first
The database column needs to be made bigger. Ask your host or a developer to widen it.
What it means
The value is bigger than the column can hold and MySQL refused to truncate it silently. The write did not happen, so whatever was being saved is lost.
What causes it
Ordered by how often it is the answer.
- 1
JSON stored in a column that is too small
Inventories, metadata and job payloads grow.
VARCHAR(255)holds a starter inventory and not a real one;TEXTcaps at 65 KB and a large inventory can pass it. - 2
A player name with multibyte characters
A name that is 20 characters is 60+ bytes in utf8mb4. A
VARCHAR(20)measures characters, but an index over it measures bytes. - 3
Accumulating instead of replacing
A log or history column appended to rather than overwritten, growing every save.
- 4
The schema was never migrated
The resource shipped an updated .sql and only the code was updated.
How to tell which one is yours
Check the column, then the value:
SHOW COLUMNS FROM users LIKE 'inventory'; SELECT LENGTH(inventory) FROM users ORDER BY LENGTH(inventory) DESC LIMIT 5;
If the longest existing value is close to the limit, everyone is about to hit this, not just the player who reported it.
Where to look
The column definition, and what the resource writes into it.
How to fix it
Give the column room. LONGTEXT costs nothing until it is used:
ALTER TABLE users MODIFY inventory LONGTEXT;
For a genuinely unbounded log, move it to its own table with one row per entry rather than one growing blob.
Still stuck on your own code?
This page is what this error usually means. Paste your console into Server Fixer and it will rank everything in it and tell you what to do first, and if you would rather not touch it, ORBIE can repair the script and hand the resource back ready to drop in.
bug_reportOpen Server Fixer