Scripts break all of the time when new versions of mIRC come out. It's just the way it is. It's not mIRC's fault (unless it's a bug) and it isn't mIRC's job to fix the issue. It's the script author's responsibility or else other people who want to edit the script themselves.
How can you possibly not say mIRC and it's author are not at least partially responible? The langauge is horribly incosistant...
Scrips will check to see if the client version is of a high enough version before loading often. But you don't see scripts checking if the client is NEWER than expected. That's because the langauge isn't expected to change.
If the PnP people know what the problem is (ie. what was changed that broke PnP), then they shouldn't have any problem fixing the issue. If they are claiming it's a "known issue" that is a bug in mIRC rather than a valid change in mIRC, then they (or you) should explain what the problem is and I am sure someone here can offer a fix and/or a workaround to the problem. [/quote]
*sigh*... I have the last version of PnP released, though it's not loaded and I don't use it. I just kept it because I remember how long MissPai devoloped it... and when she said she was moving on I decided too keep the final installment..
Anyhow, so far the errors I get are the result of basically $mircdir returning a different value. I can fix this by incorperating some stuff I use and such... though I'm gonna have to write a parser (using a seperate language to do the work...)
Honestly though... maybe it's time to leave PnP to rest. I always thought it over complicated things w/ it's interface and
