I was involved in a total repackaging of the S3 textures so I got a good inside look at them. Too many people have had hands on them, "updating" and "fixing" but without renaming the packages
so the problem is that while some package versions may very well be valid, there are S3 packs released that are not and you will get a version mismatch from players who picked these up on various other servers. Also the (also not renamed correctly) mega S3 textures released a couple years ago will cause some versions of Nexgen to completely lock you as a client, not allowing you to move, fire, or do anything but chat and quit.
Dude, I am completely behind ANYone who does dev work and tries to forward my favorite game. I'm telling you though as someone who has worked on this, it's doomed from the start if you include S3 at all. I bailed out of the S3 conversion project after seeing the errors and it was pretty much stopped. Every person I know who installed them has removed them because of conflict, and I have seen them posted to a couple of redirects even after STRENUOUS warnings in the installation package by me NOT TO PUT THEM ON SERVER.
If you still have doubts, throw on a base install and I'll find the S3 textures on a redirect somewhere that is public. Then you can join any 109 nexgen MH server and see the suckage yourself.
I'm sorry bro, I'm not trying to be a killjoy. I just want to save you some heartache.
Edit: I dug up the readme for the project we were working on:
Last edited by gopostal on Sat Oct 17, 2009 4:16 pm, edited 1 time in total.