- Identify the File That’s Failing
The “[Item: ###]” numbers (like 671, 690, etc.) are row indices in the data file UEFN is trying to read.
These are usually from one of:
A Data Table (.csv) you imported
A Hotfix file (if you’re editing data live)
A Gameplay Data Table (for items, abilities, etc.)
If you’re unsure which one:
→ In Output Log, scroll a few lines above those errors.
UEFN usually logs something like:
Loading data table: /Game/Data/Items/ItemDataTable.ItemDataTable
That’s your problem file.
⚙️ 2. Check the Table Format
Open that .csv or Data Table and look at the structure.
UEFN expects either 3 or 5 semicolon-separated values per line, like:
Name;Value1;Value2
or
Name;Value1;Value2;Value3;Value4
But your file has too many columns (e.g., 6 or 9).
So, one or more rows have extra semicolons.
Common causes:
You used commas (,) and then converted to semicolons manually.
A field contains text like "Weapon;Rare;Blue;Extra;Data" — an extra ; inside the data.
You exported from Excel or Google Sheets with the wrong delimiter.
🧰 3. How to Fix It
Open the file in a text editor (VS Code, Notepad++).
Turn on “Show line numbers”.
Go to the line number matching each “Item:” (e.g., Item: 671 → line 671).
Fix that row so it only has 3 or 5 fields, like the others.
Save, reimport, and restart your UEFN session.
💡 4. If You’re Using a Hotfix (Data Override)
If this comes from a Hotfix Data Asset, make sure:
Each entry has matching structure (same number of parameters).
You’re not pasting copied data with semicolons from Excel.
→ Excel exports often use commas by default, not semicolons.
You can re-export the working format:
Export one of your valid tables as .csv from UEFN.
Use that as a format reference for your others.
#error
1 messages · Page 1 of 1 (latest)