Problem is described in this thread.

No errors are reported during compilation. Using x86 latest pol build - 097 RC2 4 jan and latest distro version. Ecompile version is 1.08.

tried with

MethodScript :maps:/map/method

or just

MethodScript map/method

?

map/method

This one seems to work (no error appearing during pol startup), but could someone confirm if it solves the problem? And why did the error appear at all, as :maps:map/method seems to be the correct syntax for script pathname, at least thats what i found in documentation...

My guess is that Create, Control and Method scripts don't like to see package names in their definition. If you look at other itemdesc.cfg entries none of them use package names. Maybe this is a bug in the core, but for now I'll fix it in the distro.

I'd say it's due to the way beginning a path, is handled with the OS's. Same thing with php and web hosting. Using "/" at the beginning can cause problems if the host is not configured correctly (to make YOUR root, be from the location of your html root). Same thing here I would say. It's trying to forcecheck from a different root position in place of the package's root.

Interesting find though, for sure

Is this error only with methodscripts, or does it do the same thing for you with Equipscripts, usescripts, etc?

From what I am seeing, it is due to the "/" at the beginning of the path. There is a reason for that. It's forcing it to check off pols root from the best I can tell because of it. the format ":pkgname:maps/method.ecl" is that way for a reason. The root is the pkghome. If you add another root mark it confuses it.

The relative path answer is fine, but didn't Haos mention it didn't give a compile error?

Why would it give a compile error? It's under a pkg directory that is enabled. Compiling doesn't check itemdesc.cfg entries.

I must be reading it wrong. I thought the whole thread was about the location of method.ecl. Sorry.