Console says: Cannot ready *.ecl file

[*Edwards]

Exemple:

Item x
(
Name x

Script :mainHitScript:mainHit
)

When pol starts and cannot read :mainHitScript:mainHit.ecl he warn us on the console that ''cannot read :mainHitScript:mainHit.ecl''. I would appreciate if he could tell us which item cannot load the script because right now I have a really small problem to research the item using this script that is no longer available on my project. (I handle combat in a different way... )

[Turley]

Why not simply use the "find in files"-function of your favorite texteditor tool?

[*Edwards]

Yeah that would be smart!! But I probably have 50-60 pkg with itemdesc entries.

[Pierce]

For such a case i can recommend the following tool which does
a good job helping me converting 95 to 96:

http://www.harddisksearch.com/

You simple need to define searching .cfg files inside the pol directory
for e.g. the term mainHit and the tool lists all files that contain it
You can open each file and it points to where that "mainHit" appear in that file.

[Turley]

Yeah that would be smart!! But I probably have 50-60 pkg with itemdesc entries.

Mmmh i have 72 itemdesc's and UltraEdit takes about 2s to search inside all of them.
What texteditor tool are you using? And if you use notepad, then the explorer has also an "search in files" feature...

[*Edwards]

I though it would be better for pol itself if the error returned could be more specific. I'm using an old tool called Scripter.exe found on this forum. And I've take a look to all my possible weapon entry in my files but didn't find anything. Nyways, it's only one single item that spam my console each time I start pol it's not the end of the world ( I hope so! ) but maybe I'll find it one day and bring this topic alive for one last time!! Thanks or your help.. But it still a suggestion!

[Nando]

I can see if it'd be easy to make POL more verbose on this error. If you just want to discover which item/itemdesc is doing that, just place a script where it's searching and make the script print the objtype and serial (if it's already in your datafiles)

[CWO]

Probably the only thing that would be needed is the objtype of the item. You can then easily track it down.