If you wanted, I can give you some webspace for them to be uploaded, and have a .zip/.tarball created so you don't have to repackage it every day.
Thanks, I'll PM you when we get closer to the release.
Here is my current plan for the CTP.
I plan on releasing CTP 0.8 very soon. This is a pre-release of CTP 1.0, and CTP 1.0 will be backwards compatible with CTP 0.8.
CTP 1.0 is basically going to be resizing, bugs, and a few more textures.
My plan for CTP 0.8 is to simultaneously release:
-4-5 new maps I have created. (Mostly DM, TDM, and CTF)
-4-5 existing maps with the textures replaced with the new CTP textures (assuming I get permission in time)
-The CTP end-user files.
-The CTP 0.8 MDK (will work with CTP 1.0)
Once the bugs (repeating anomalies, seams, etc.) are worked out, I'll add a few more textures to the package and release the CTP 1.0 package, along with the CTP 1.0 MDK.
Here is my plan for naming maps.
Maps using the CTP 0.8 or 1.0 will have ctp1_ in front of the map name.
(e.g. ctp1_newmap.bsp)
Pros:
+ Players will know what CTP they need in the likely event we release an update
+ Existing maps ported to the CTP textures merely need to add ctp1_(filename) and will not overwrite the previous copy
+ People can easily identify CTP maps before they download them.
Cons:
- If some mappers do not conform, it will be very confusing.
thoughts?