Favor to ask

Hmm, I'm really not quite sure what problems you're getting.
I've gone through both of the avs folders presets and checked the result compared to what is listed in the files (I haven't actually looked at them with AVS), and what's in the Res folder, and no matter where the folders are (different disks, deep or shallow) it still works correctly.

I don't want to doubt you, but are you sure you're sending the correct resource dir?

my brain is shot for the night now, I should probably give you my msn so it can be nailed down, which I will send now.

would it be possible to get a unicode build of this plugin as well? sooner or later, i will switch to the unicode version of nsis so i thought i better ask now that you still remember how the plugin works 😉

there are currently 5 nsis plugins not available for unicode nsis, at least two of them can not be integrated using the CallAnsi plugin. i guess a unicode build of pimpbot could take a looong time to be realized. it's said as i have some unicode language files that i can't convert to ansi without losing information (e.g. cyrillics).

out of interest, what are you using to compile your plugin?

I'm using Code::Blocks with GCC (I'm used to that set up due to previous open source work).
I didn't bother including any project files in the zip because I assumed very few people would use that set up.
(I'm also still not interested in spending hours flapping about in a naive attempt to produce a unicode version)

well, for a second i thought i might take a look at it and make it work for unicode. i doubt i would even get as far as compiling, as don't know any c++ 🙂

okay, it looks like i found a workaround. pimpbot itself will still be built using the ansi version of nsis, but it will create unicode installers. that way i don't rely on avstools in unicode.

will post a working version in the next couple of days.