Senior Member
Join Date: Sep 2012
Location: Ottawa, Canada
Posts: 788
|
You need to remove the ? in the tag name.
Watch your back, Conserve your ammo, and NEVER cut a deal with a dragon! |
#11 |
Senior Member
Join Date: Sep 2012
Location: Ottawa, Canada
Posts: 788
|
I'd give it a tag name like ioKYSMO with the KY representing that it is a personal file. A Community Pack file would be: io5CSMO.
Watch your back, Conserve your ammo, and NEVER cut a deal with a dragon! |
#12 |
Senior Member
|
Sorry to be such a pain. I've changed the Unique ID as you suggest, but I'm still getting error message:
Hero Lab was forced to stop compilation after the following errors were detected: File: COM_5ePack_DMG - Equipment.user (line 571) - Thing - Invalid unique id 'ioSMO?' for attribute 'id' But when I search for line 571 I get the message: Line 571: thing 'Crown of Wound Closure' (unique id: ioKYSMO) from component set 'Wondrous' So I don't know what's going on. Line 571 doesn't say what the compiler says that it says. -- Lexin GM from Gwynedd, Wales - seriously old school - playing RPGs since 1980! Tools: Realm Works, HeroLab, Campaign Cartographer 3+ |
#13 |
Senior Member
Join Date: Sep 2012
Location: Ottawa, Canada
Posts: 788
|
Somewhere in your file, you have an item that has the tag: ioSMO.
You have to either rename it or delete it. It is what is causing you your issue. I think the file causing you the issue is actually in the COM_5ePack_DMG - Equipment.user file though. I;d find the ioSMO? file that is in there and delete it. Then save tile and run the Watch your back, Conserve your ammo, and NEVER cut a deal with a dragon! |
#14 |
Senior Member
|
I finally sorted it. You were right, it was a stray question mark in the original COM_5ePack_DMG file. I was going nuts there, so thank you so very very much.
-- Lexin GM from Gwynedd, Wales - seriously old school - playing RPGs since 1980! Tools: Realm Works, HeroLab, Campaign Cartographer 3+ |
#15 |
Member
Join Date: Mar 2014
Posts: 60
|
A quick tip, you can open the user files in a text editor (I prefer Notepad++) and then see the actual line referenced in the error message. This can be a great help in debugging.
|
#16 |
|
|