Cukie
Active Member
- Joined
- Dec 3, 2011
- Messages
- 1,255
- Reaction score
- 3
This x10000. This area is where Pirox was better than HB in my eyes, you could set your own custom routes. While the "idea" of BG logic is nice, the implementation is flawed. I would rather have for example 10 custom routes for AB, and have a different one chosen after each death or w/e. So 1 route would only defend, while if you were killed while defending, upon rez the next path would be chosen at random, and could be an offensive route, or what have you. This is the way PVPTool functioned, and it worked very well. You VERY RARELY ended up with a bot train, unlike ALL of BGs with BGBuddy, which is the #1 reason for BG bans. I would rather fight in the middle of WSG with my bots alone like a noob, then have a congo line of BGBuddies following around the FC because of "Defend Flag Carrier" logic.The trouble is, the problems lay in the core, writing a plugin to correct the core besides being a waste of time, would be so inefficient as to make the whole concept unworkable.
Bgbuddy says: Moving to biggest pack.
Plugin says: No you are not, you are moving to X location.
AMD processor melts
Bgbuddy should provide the core elements needed to perform the bg, entering/exiting, capping flags, movement, etc, the logic of the bg should be handled by .xml files. A Bg is no different to a combat routine in this regard. You perform the same tasks over and over with slight changes based on the situation and what class you are. Everything is just about there in the api, it just needs handler code to push all the logic out to file, so we can then hackup our own bg routines based on our class and the objectives of the bg. Something that really should not be all that hard to do.