Everything aggro's

[Angelox]

I've actually went through a lot of the newbee zones and done just that , bats assist bats, wolves assist wolves, etc. Also the guards are properly associated with these newbee mob factions. So my newbee zones work fine - but honestly, this is wasted time: most of the work done in these zones will never be seen or used by anyone for a few reasons other than faction. One reason is, the rate at which experience is dealt out. Nobody wants to level slow in these areas. Even on the most strict of servers, I could probaly get ten levels in a few hours, level 60+ in a day or two.
I've given all this a lot of thought (all I can do at work), fast-leveling like this affects many things. For example, loots: I used to harp on how loots were too many and too easy. But, if you think about it, on a 1x - 8x exp server, then loots have to come faster accordingly, else the player never sees the loots and reaches 65 first (an 8x server probably should have extremly common loots, or even #summon command available). Same goes for faction; unless you plan to play in *just* these classic zones at a slow experience rate, then this will not be of any use to any players. Now, I'm not against fast-leveling simply because I have no right to be. But even the default rate that comes with the source is already faster than normal, so everything else should probably be adjusted too.

[cavedude]

Yes, you could put all the creatures on their own faction so that they would just assist each other. But the problem with that is two-fold. One, that's a lot of factions, and there is no need for them if the system works. That's purely from an optimization standpoint. And two, it isn't live like. I know in Misty as an example the only creatures that were ever social (excluding KOS, gobbys, orcs, bixies) were those damn beetles. The bats, rats, snakes, and spiders would never assist each other. Though in gfay you are right on, there were a lot more npcs that would assist. It's also a much larger zone with a lot more room to breathe.

But this problem isn't just limited to noob mobs, that is just the best example. Smaller dungeons are another good example. If aggro range and assist range are the same, then it's silly to have same faction NPC's assist assuming they already are KOS. Assisting uses a bit more CPU power than straight out aggro and on larger servers reducing it in favor of regular old aggro could make as big an impact as your non-pet spell tables did which I am still thankful for.

[John Adams]

I'm glad we're discussing this. I created a few new NPCs in a dungeon the other day, 2 side by side (defending a doorway for instance). I set their aggro radius up, dropped my GM and attacked one. The other stood there like a statue. I even ran up under his dress, dragging his buddy who I was killing with me. No aggro.

So I went to check the database entries for those two. Noticed I forgot to make a Faction. So using PEQEditor, I setup a single faction, assigned it to both NPCs, having them Assist. Repopped, then attacked one of them again. Still, the other would not aggro.

Is that not how this system works?

[cavedude]

Faction is in shared mem so you need a reboot to take effect.

[John Adams]

Ahh, ok that makes sense. I didn't think of that. :(

[cavedude]

Sorry to bump, but after talking with FNW and KLS last night about this, the newest build has a solution:

KLS: Added a field that allows you to override a factions innate desire to assist their own faction in battle to the npc_faction table

Required SQL:
alter table npc_faction add column ignore_primary_assist tinyint(3) not null default 0;

Setting ignore_primary_assist to 1 will prevent NPCs from assisting their own on that faction, leaving at the default 0 will leave things as is

[ChaosSlayer]

I am realy glad to see this was finaly addressed while I was away from EMU

I don't mean to be a dick.. but wasn't it more logical to code in "-1" value in npc_value colum to force a faction NOT to assist each other? =)