Quote:
Okay so what you are saying is " fix it for me " and screw everyone else? im 100% oposed to anything that will work for some peeps and not for others
|
I don't understand how you got that from my post. I'm saying put the feature in and let people implement it in their own DBs as they will. It will "work" for anybody who takes the time to go through the zones and put the grids in. All I was saying was simply that if you use a custom DB, such as guildwars, that you would need to do it yourself.
I don't see how this is any different than pathing in it's current form, which must be done by hand for each DB, and I don't see anyone getting angry over that. If anything, actually, it might even be possible to port Big Grid info between DBs, because, unlike pathing currently, it wouldn't be tied to spawn group ID#'s (or NPC ID#'s, not sure which), which are DB dependent, but rather to zones themselves. This would mean that only people who have actually made custom zones would need to do it for themselves. But this is all just speculation on my part. I'm sorry if you took my post to be selfish; that's not how it was meant at all and I hope I've cleared up what I was trying to say.
Quote:
I find it odd that i have no problems with guk/solb ect for mobs aggroing through walls. you use drawde's db then your problem might be that you dont have aggroradius set correctly and its too large so they attach through walls.
|
I don't think this is the problem, as aggro radius as it's currently set on Drawde's actually seems like it's on the low side, if anything. If you want a good example in sol b, go into the tunnel above the stone spider room and turn your gm status off. If you are KoS to LDCs you will have the entire room below on you in a couple of seconds. There are numerous other instances that you'll find if you go through the zone with gm status off and KoS to mobs. We haven't redone lguk yet so I can't speak for it, but several places stick out in my mind as spots where through-wall aggro would almost definitely occur.
Quote:
I think there has to be a better way. NOT db dependant.
|
It's quite possible that there is. Like I said in my first post, this is simply something I'm putting out there for consideration; a fix to a problem that has bothered me for awhile. I'm not a programmer and therefore can't assess whether or not other options are available or even if this could be done.