[Hot-Doc]

@Pierre-Marie Baty

Thank you very much for delivering such frequent updates to the source code of PODBot 2.6!

Unfortunatly you don't plan to add any new features, but you made so many bugfixes to the originally released sourcecode that by now it surely became the most convincing source of the 2.6 PODbot available. Therefore imho it should become the basis for any PODBot 2.6 derivates.

Would it be possible to organize a project around this WIP (why not call it "PODBot 2.6 BU template")? I mean here at the bots-united forums are at least three members who use the original 2.6 source as a basis and they all have to fix the same bugs. That sounds to me like inventing the wheel three times. Would it be possible to split up the source code in more logic fragments (like aiming, weopon selection, combat tactics, squad tactics, waypointing, etc.) and then letting all developers concentrate on what they probably want to do - adding features that help making the bot more smart, easyer to use and more challenging? Or as a further thought, would'nt it be nice for the enduser to be able to choose your modified WIP and then select for example austins waypoint editor (ok, it's allready included but might be improved later on) and the aiming system of LightNinja, the Navigation of IvPBot and so on?

Of course all developers work on their bots for fun, but from the point of view of an end user it is a pitty to see that for example bot "a" has a new sensational combat mode but is not able to navigate doors, whereas bot "b" navigates smoothly but lacks convincing combat behaviour.

Please don't get me wrong, I'm not a coder at all, but seeing that we use the halflife engine, with a hack for plugins (metamod), a plugin for integrating a bot and then another hack (mEAn) that itself overrides the aiming of the bot that is running under metamod seems to be inefficient. Using a hack to hack a hacked piece of program is to weird for me - it somehow reminds me of the development of windows me...

Nevertheless this method works. But woldn't it be better to have metamod loading a plugin that works as a botmanager (without admin tools) that can run in multiple instances and handle plugins for navigation, waypointing, aiming, and so on? This way seems to be more straight-forward.

As I said most developers do it for the fun of developing their bot and beeing forced to certain interfaces may not be challenging enough for them since they would depend on others. But wouldn't it be what Bots-United stands for - joining forces?