[ Sorry, this is a long mail, but please read it when you can as I feel that we are at an important point re mod development... ]
In the first version of your mod that I made work in the ZQ QC CVS repository, there were lots of files such as ``tornado.qc'', ``firebomb.qc'' and so on. In the one you just sent me there are only a few (as opposed to about ten before). If you've merged them all into wepaons.qc, then it will be very difficult for me to un-merge them and put things back to how they were. I think it would be easier for me to implement function overrating in the original version of your mod that you sent me, then you can add the bits to it that you've added since. I'm apprehensive at the thought of how much work lies ahead for me if you've spread your code across all the AGRIP/QW QuakeC code. The modularised version of your mod that I made last time (but didn't get to you, of course, due to hotmail hating me) had all your code separated out into one place so that all was good. The only thing it didn't have was function overriding. Now we know how to do that, I could make it work. Have you looked at the ZIP file I uploaded for you? It contains the modular version of your mod. I think it would be a good idea for you to have a go with it, as for me to have to separate out all the extra weapons code and then modularise it all again could take weeks at this rate :-(. The version I sent you only needs overriding implementing and then it's good to go and be upgraded whenever you need. I'm assuming that your code has been spread out, 'cos I can't find in anywhere else. If I've got the wrong end of the stick, please let me know. I do feel, if I'm right on this, that rolling back to the modular base I created for the mod and then continuing on that path would benefit us all. I would be happy to remove all the duplicate code for you using the overriding technique you used. Then you get all our updates automatically and your mod will be easier to develop and maintain. It will also serve as a great example for future developers. I have to say I was worried about this situation arising a while back, when I started the development manual -- there's so much information I want to give you before we end up with an unmaintainable code-base, but there wasn't time :-(. Still, I think this one is perfectly salvageable by rolling back a little, but we need to be very careful and try to keep things well organised and modular (as they are in the reference implementation I did) or we could end up with your mod not being upgradable to new AQ releases -- a situation I really would hate to see as it's a good mod and it would benefit from all the new teamplay stuff and other fixes in beta 4.1. Please do let me know what you think when you can. I am not saying this because I'm lazy -- I already did 90% of the work and I genuinely feel that the hooks available now (and in the near future, based on what I've seen in your mod) will be enough to allow you to do what you need and still allow seamless code upgrades on our side. We really need to be able to stay in touch about what you are planning to do and how we (AGRIP) can make it easier for you. I can also give you advice on why certain things may not be good ideas (as you said, you've been waiting for more knowledge). I think that if we had a better dialogue on development issues (perhaps another mailing list, not sure yet) we could avoid this situation in future and all learn a lot from it. bye just now, best regards, -- Matthew T. Atkinson <[EMAIL PROTECTED]> _______________________________________________ AGRIP-discuss mailing list [email protected] http://lists.agrip.org.uk/cgi-bin/mailman/listinfo/agrip-discuss
