02 Apr 11, 10:31PM
Yes, it's not been acknowledged much yet .. that's why I've tried to explain the forms of usage here. But we should really try to make the wiki-page about MediaPack be readily understandable for someone who didn't write the code.
Viper: that's exactly what it's for!
In-depth explanation: if MP-Y was installed by the mapper of map-X and he uses a texture from MP-Y then this is saved into the header of the map. So when someone then does a "getmap", or somehow else get's map-X onto his system without having MP-Y installed then the engine will output "this map requires the following mediapacks: 1234" (assuming MP-Y is #1234) and then output a URL where you can get it.
Currently only one MP has been published so the URL is still hardwired to R4zors page - I assumed he'd be taking charge of compiling & hosting all upcoming MPs.
I've already built a stub for handling different locations for each MP on our website, so in the future the URL will basically always point you to our site first, then pass you on to whoever and wherever the respective MP is hosted.
And if we ever get to "feature paradise" we may see the engine able to download the ZIP automatically, unpack it and put it into use instantly .. but that's probably still a long way off.
Viper: that's exactly what it's for!
In-depth explanation: if MP-Y was installed by the mapper of map-X and he uses a texture from MP-Y then this is saved into the header of the map. So when someone then does a "getmap", or somehow else get's map-X onto his system without having MP-Y installed then the engine will output "this map requires the following mediapacks: 1234" (assuming MP-Y is #1234) and then output a URL where you can get it.
Currently only one MP has been published so the URL is still hardwired to R4zors page - I assumed he'd be taking charge of compiling & hosting all upcoming MPs.
I've already built a stub for handling different locations for each MP on our website, so in the future the URL will basically always point you to our site first, then pass you on to whoever and wherever the respective MP is hosted.
And if we ever get to "feature paradise" we may see the engine able to download the ZIP automatically, unpack it and put it into use instantly .. but that's probably still a long way off.