Still need the new AB's for CrowCaw, DustStorm, and FamiliarBerserk/FamiliarSting. If folk could PM me these, that'd be wonderful for my little OCD baby!

Duststorm's AB did not change.

No, the issue raised was not that crow users had to travel back to the nest to refill carrion. The issue was that the amount of carrion that one could carry was just too small and the useful skills (ex. Belch) used carrion too quickly. The solution you (or whomever) have given crow users is total garbage. No offense, but I will explain.

For three power, a crow user can "hibernate" which means they can pause their system and do absolutely nothing (no tells, says, look...anything) and drain the 100 carrion from their nest into their personal supply. From what I can tell, nests lose 5 carrion per every tic of hiberation and the crow user gains 4 carrion.

This makes no sense at all. For 5 power (two power more than hibernate) you can just nest call and "crowsnest feed' from the carrion you have stored without the huge loss, as well as gaining the benefits from nest call (25% over max health and mana). I mean, I don't understand why this skill was created. It's essentially a crappy version of nest call, that does nothing to address the issue that was raised. Belch, regurgitate, and all carrion involved skills require the same amount of carrion and are drained at the exact same rate. All that is changed is that you have given us an option of pausing our system and wasting a large amount of carrion to hibernate, or spending two more power to nestcall and refill on carrion far more efficiently and quickly.

In summary, hibernate does absolutely nothing that crow users didn't already have access too via nest call, and nest call is a crappy skill to begin with. It's just a poorly designed solution to the problem that was raised.

I also don't understand why carrying around corpses is considered "trivial."



I TRIED to tell you both the hibernate and familiar stuff, but I'm snubbed (which I didn't know until I tried to message you). I hope telling you this isn't against the rules.....

edit: And to be blunt, who the hell has time to sit down and hibernate for carrion during group fights. I mean honestly, what the hell was the logic behind this pile of crap skill.

Now we get to spend report slots trying to make hibernate useful. Wooo.

Uh, sure sounded like that was the issue. For the problem suggested, I think it is pretty neat and well designed! Anyway, let's see how hibernate works--I don't mind considering tweaking it.

Okay, yes. I was wrong. That was the issue raised.

The solution still does not solve the problem with carrion and nests in an effective way, explained in my last post.

My main issue with it is the power cost at this point. I think that, with no power cost, it would be a good alternative-- depending on situation, it would be useful. For Blacktalon there's no point to the skill at all (for a small bit more power one can just summon the nest and suffer no carrion exchange loss). Without power, though... they have a choice of taking carrion-exchange-rate losses to refill, along with being unable to move while meditating... or making trees and calling the nest for the ability to avoid meditation.

For Ebonguard, having to spend 3p every time one breaks the meditation is still a bit rough. I'd just like to see the power cost go, as it has other balancing factors to it.

I actually don't follow your post at all. Nestcall is better, but costs more. Hibernate is for times when you can't nestcall (which is often for warriors), or if you only need 4-8 carrion. The carrion loss isn't bigger because nestcall itself takes carrion. Feeding is likewise not instant. From what I see, you're all worked up because the new skill isn't an upgrade so much as an alternative.

The 2 power cost difference is, in my opinion, irrelevant. The loss is bigger. Nestcall takes 5 carrion once.

When can you not return to the nest to fill up on carrion? When do you only ever use carrion in large quantities? Combat. How is a skill that requires you to completely pause everything and wait for 4 carrion every 10 seconds useful in that situation? Carrion mechanic is pretty limiting as it is, so placing a hugely limited band aid over it is not a good solution, IMO.

I'm "upset" because the suggestions that would have made carrion skills more viable were tossed out in favor of another shiny new skill that serves no purpose for one guild, and might be kind of okay in some situations for another.

As opposed to the speed of feed and nestcall?

Nestcall and feed aren't really slow, and you don't have to pause for them either.

I'll have to rebuild a nest to check, but if I remember correctly, nestcall is slow as . Feed is fast, but you aren't going to efficiently get 20 carrion in the middle of a battle.

Nestcall is a good deal faster than teleport when used on Prime. On cosmic it takes about twenty seconds. Elemental is somewhere in between, and astral is foreeeever.

That's nest return

Since no one else has...:



Are Squirrels and Spiders' ABs supposed to reflect this change or are they just getting around to it still. -twiddle-


Edit: Though, I must admit, I wonder why it is they chose Spiders instead of Murder to take down flying people. Leaping spiders make me giggle.

That actually kinda is a reasonable option now, I'd think, considering that the lack of malus to the target on a seize while the user suffers a 4s balance loss means that druids have no conceivable active way to get someone in the trees if they're size 25. Treelife being passive and needing protection to be stripped kinda is iffy since having to wait 10s in the hopes that you can get the sap to lock someone means you get to spam...vines for 10s and hope the druid doesn't get eaten in that 10s.

BUT, since I know people are gonna cry 'ohpea, you're only a droodle of course you're biased', fat chance of an actual discussion for that happening anytime soon.

There's actually and envoy report up right now to reduce the effect of size on summoning resitance.

If that doesn't help the situation then it would be a good idea to re-envoy if it is still causing trouble.

Arr. Increase the power to like 7-8p to make it fair.

Edit: This also solves certain classes being immune to sapping, more or less.

7 - 8 power = no sap lock

It is 9 power right now for a non trans stag user to sap lock, 7 for a trans stag user. I don't knowwhat is involved in the BT sap lock so can't give numbers there. But sap with no lock follow through is just a waste of power.

Well, I won't pretend to know what is fair, but I just figure it'd be safe to assume you're going to have to add some sort of extra penalty to allow people to accept groundsap.