Error

**Derpy Hooves** · April 12, 2011, 04:28 PM

So this is what it says in my log

Spoiler Alert, click show to read:

Now I bet you (the reader) is thinking that I somehow changed the export_descr_unit.txt, well you are wrong. This has not happened before when I have done my tests, but after I had added made new files for names, and added quotes, this error popped up. Now in closing I must say that I have edited this file but that was after I got the first error that said it originated from the export_descr_unit.txt

**Kandid** · April 12, 2011, 04:39 PM

Did you check mods/Lodoss/data/export_descr_unit.txt, at line 489, column 63?

Computers never lie.

**Derpy Hooves** · April 12, 2011, 05:56 PM

Yes I did, there was nothing wrong (since I did not change that part of the file)

Like I said everything worked perfectly, until I messed around with character names and quotes (which have no affect on the export_descr_unit.txt)

**Taiji** · April 12, 2011, 06:15 PM

Invalid ownership type 'slave' found in unit 'Mailed Knights'.
08:38:20.188 [data.invalid] [error] DATABASE_TABLE error found : error reading record from file mods/Lodoss/data/export_descr_unit.txt.

It says your battle_model for mailed knights is lacking an entry for slave.

Since receiving this message have you already tried removing 'slave' from the 'ownership' line in the EDU entry for this unit?

Now I bet you're thinking 'I only edited names and quotes, why won't the nasty man listen to me?'

**irishron** · April 12, 2011, 06:16 PM

Did your names affect the names in the descr_strat.txt or campaign_script.txt?

**Derpy Hooves** · April 12, 2011, 06:19 PM

I don't know if it affected the campaign_script, but I know it did affect the descr_strat (also I removed all names)

And Taiji, I did that every time it gave me a different entry, and as you can imagine I got sick of it and decided to ask the TWC forum

**Kandid** · April 12, 2011, 10:01 PM

Originally Posted by swordofjanak

I don't know if it affected the campaign_script, but I know it did affect the descr_strat (also I removed all names)

And Taiji, I did that every time it gave me a different entry, and as you can imagine I got sick of it and decided to ask the TWC forum

I'm going to take a wild guess here, but it sounds like the problem is a trivial syntax error. You're probably missing an opening or closing curly brace somewhere in your EDU. This would explain why a different unit gets messed up each time you fiddle with the EDU.

To test my theory, use a text editor that can highlight matching braces for you. Just go to the last brace in the EDU and see if that lines up with the opening brace. It may be your EDU that's messed up, or maybe some other file, or both.

If you had version control (git/mercurial/etc), you would never suffer from these cryptic error messages.

**Eothese** · April 13, 2011, 06:22 AM

Originally Posted by Kandid

I'm going to take a wild guess here, but it sounds like the problem is a trivial syntax error. You're probably missing an opening or closing curly brace somewhere in your EDU. This would explain why a different unit gets messed up each time you fiddle with the EDU.

To test my theory, use a text editor that can highlight matching braces for you. Just go to the last brace in the EDU and see if that lines up with the opening brace. It may be your EDU that's messed up, or maybe some other file, or both.

If you had version control (git/mercurial/etc), you would never suffer from these cryptic error messages.

EDU doesn't use curly brackets.

Invalid ownership means that the faction dosen't exist as a valid choice, check descr_sm_factions for the slave faction. Failing that set your log settings to trace. And post the line specified in the log, here in full.

Code:

[log]
to=logs/lodoss.system.log.txt
level = * trace
file = game.script.* logs/lodoss.script2.log.txt
file = game.script* logs/lodoss.script.log.txt
file = game.script logs/lodoss.scriptoutput.log.txt

**Kandid** · April 13, 2011, 12:17 PM

Originally Posted by Eothese

EDU doesn't use curly brackets.

Oops, I was thinking of the EDB.

Anyway, as Taiji pointed out, assigning a unit to a non-existant faction will certainly result in a crash. Well, referring to any undefined variable will likely result in a crash somewhere down the line.

**Taiji** · April 12, 2011, 06:40 PM

A different unit or a different faction each time?

**Derpy Hooves** · April 12, 2011, 07:48 PM

both

**Taiji** · April 13, 2011, 06:40 AM

I think Eothese is likely to be right. Probably something is messed up with regard to your factions.

**Derpy Hooves** · April 13, 2011, 07:40 AM

So, are you saying I should remove all the faction names in the export_unit_descr.txt that don't show up in the mod?

**Taiji** · April 13, 2011, 09:43 AM

You cannot give ownership for a unit to a non-existant faction, so you will have to amend every instance where this is the case.

It's worth noting that normally modders keep the internal names for factions. You can change the displayed name and avoid having to change everything you are going to have to change by doing it the other way.

For future reference: When you referred to names in your opening post it was natural to assume you meant character names. Had you mentioned changing faction names, or removing the factions referred to in the error message, this would have been a much easier problem for us to help you solve.

I'm telling you that to help you, not to reprimand you. I hope you're not offended.