Hey Quozl, Thanks for the general pointers. I've generally hacked up other people's code for my own personal use. Participating in an Open Source environment is pretty new to me. As I have a great idea for a "newbie" server... BUT I have no access to a Linux Box or other unix box out on the internet... So, this is my only recourse, is to add it into the Vanilla source (and hope someone else uses it for a newbie server). I really dunno if putting it into a "newbie" type server is even appropriate. My aspiration is by the time, I am done tweaking the AI of hadley's bots, even experienced players will have a hard time. The next patch will include commentary in the ChangeLog and news. Following the current format of the Changelog. To be honest, those changes are it! I can't think of anything else that will make the bots tougher. I have been thinking about re-writing the dogfighting code. Computers are faster these days :-P. The first time I re-wrote the dogfighting code (6 years ago), it took so much CPU cycles, the bots couldn't keep up... Jimmy --- James Cameron <quozl at us.netrek.org> wrote: > On Tue, May 16, 2006 at 12:02:08AM -0700, Jimmy > Huang wrote: > > Sorry about that, didn't know I was supposed to > modify > > ChangeLog and NEWS. > > That's okay, we probably didn't make it very clear. > You'd only know by > looking at the differences made by others, or by the > changes from one > version to another. > > Take a look at > http://www.tldp.org/HOWTO/Software-Release-Practice-HOWTO/ > the Software Release Practice HOWTO. > > Especially section two, "Good patching practice". > Sections 2.6 and 2.7 and 2.8 are cool. > > Some of the patch is to gain acceptance, but some > has to live forever in > the code until someone removes it. Review the patch > I've just made, and > you'll see what I thought of it. ;-) > > -- > James Cameron mailto:quozl at us.netrek.org > http://quozl.netrek.org/ > > _______________________________________________ > netrek-dev mailing list > netrek-dev at us.netrek.org > http://mailman.us.netrek.org/listinfo/netrek-dev >