Thread: Petition to fix Scytode Brood, aka the ranged hatchling!

It is bugged since it has been created. The trait looks sweet on paper and I've been looking forward to using it. It stays range so doesnt die to aoe and gives a bit of tactical mitigation which is more useful than physicals who we mostly kite anyway.

And the issue (in case dear Turbine doesnt know) is as follows:

Hatchling attacks very infreuently, stops attacking and just stands doing nothing, refusing to accept the "Attack!" command. I know he has a root which will stop him from dpsing but after the root breaks, the npc goes back to dpsing the hatchling and im bashing the "Attack!" command, the pet just stands still. Eventually it will unbug and return to attack...before it buggs again.

That makes pretty much every spider trait for Strong Brood as that one doesnt bug at all. We are deprived of a trait that most spiders would consider better than the Strong Brood.

Its been update after an update, patch after patch and somehow Turbine failed to fix it. I believe its just a misunderstanding and you guys will look into this skill in no time the same way you try to fix other bugs. I do not expect a buff or anything like that, I just want a skill to be unbugged.

PS: As we're here talking about hatchlings, also I believe there is some issue with the Devour skill. Often the pet just refuses to sacrifice, usually that happens in a more intense fight with freeps. Even when the targetted npc is next to me and the pet is attacking it, he Devour doesnt work. I go out of combat, enter another fight and poof, my hatchling sacirifices itself at the very beginning of the fight with me fully healthy and not even touching the Devour skill.
But this bug would be just a bonus one.

So...please, fix the Scytode Brood.

Thank you!

/signed
Also, I will note that Scytode Brood is fixed on Bullroarer, and maybe Turbine doesn't look beyond the testing server to see if things like Scytode Brood function live for creeps.

It is rather unprofessional to work on the spiders most recent overhaul and not fix a bug that was present since the Scytode Brood has been added. It was also talked on forums about it being bugged so I don't really see the excuse.

Originally Posted by Whotookallnames

Hatchling attacks very infreuently, stops attacking and just stands doing nothing, refusing to accept the "Attack!" command. I know he has a root which will stop him from dpsing but after the root breaks, the npc goes back to dpsing the hatchling and im bashing the "Attack!" command, the pet just stands still.

Maybe it just respects 1v1s.

they should fix it, really. it's ridiculous.

/signed

It's a joke that this is fixed on BR and the recent update to weaver has done nothing to get this fixed on live.


YOU WANTED TO MAKE THE WEAVER A "PET CLASS" SO FIX THE DAMN PETS!!

/signed (of course)

Yes, I've mentioned the pet issue in my own thread, it definitely needs to be fixed.

Apparently, the stuff we see on BR is separate from the stuff we see on the Live servers. I don't think there is any interaction that occurs between BR and the Live servers in terms of coding, so (in other words) they aren't copying anything directly over from BR according to our feedback. But for players, at least, what we see on BR is exactly what we'd like to find on Live once the updates occur, so this really is something that needs to be impressed upon the developers who do the server translations over from the alpha/beta server and their playtesters.

/signed

I would love to trait the ranged pet. I tested it after U6, on live, and it only did it's skill attacks. It absolutely did no auto attack at all. I'm really disappointed.

Devour is working for me, so I don't know on that one.

/signed ...yes.it needs to be fixed. I would lvoe to be able to use the ranged pet..but right now its just a liability.

About devour: the only problems I have is when the hatchling is stunned, that's when it doesn't run over an sacrifice itself. However, the skill is named "devour"..meaning your the one eating it. Therefore it should not matter if your hatchling is stunned or not..as long as your close enough to eat it.

You catch a burglar, you both fight, burglar hipses and you know theres a big surprise strike coming on you. Want to eat a hatchling to heal up as you saved him all the time but...you cant cause you gotta target someone...yet you are in the open and the burg just hipsed. You die, pet doesn't. Fix please, edible without targeting stuff.

The problem is server latency related (the pet works brilliantly on bullroarer when its up and only struggles on a fully loaded down server).

They're well aware of it, it's likely just a very difficult thing to fix.

Originally Posted by Sezneg

The problem is server latency related (the pet works brilliantly on bullroarer when its up and only struggles on a fully loaded down server).

They're well aware of it, it's likely just a very difficult thing to fix.

Are they aware of it? Has it been recognised in any bug lists? Has any dev commented on it? Hard to fix? Doubt it, because it works on BR and never works on live even if you log in the second the servers come up. Seriously doubt it has anything to do with latency. The major problem is that it isn't a Warden bug, which would require a rushed hotfix to be issued. It's just a creep pet bug... you know that pet we forced on them against most existing Weaver's wishes. Meh...

I am becoming increasingly suspicious that Turbine does not read Creep forums, at least not very often. My suggestion is to have a good chunk of the weaver population report this bug every few days in-game until Turbine has to notice it. Be detailed in your reports.

/signed...so glad turbine fixes those typos instead of something useful.

Originally Posted by Sezneg

The problem is server latency related (the pet works brilliantly on bullroarer when its up and only struggles on a fully loaded down server).

They're well aware of it, it's likely just a very difficult thing to fix.

Bullroarer has 10 times more people playing than my server ( including the people doing pve ) , and still works .

/signed

Originally Posted by Whotookallnames

It is bugged since it has been created. The trait looks sweet on paper and I've been looking forward to using it. It stays range so doesnt die to aoe and gives a bit of tactical mitigation which is more useful than physicals who we mostly kite anyway.

And the issue (in case dear Turbine doesnt know) is as follows:

Hatchling attacks very infreuently, stops attacking and just stands doing nothing, refusing to accept the "Attack!" command. I know he has a root which will stop him from dpsing but after the root breaks, the npc goes back to dpsing the hatchling and im bashing the "Attack!" command, the pet just stands still. Eventually it will unbug and return to attack...before it buggs again.

That makes pretty much every spider trait for Strong Brood as that one doesnt bug at all. We are deprived of a trait that most spiders would consider better than the Strong Brood.

Its been update after an update, patch after patch and somehow Turbine failed to fix it. I believe its just a misunderstanding and you guys will look into this skill in no time the same way you try to fix other bugs. I do not expect a buff or anything like that, I just want a skill to be unbugged.

PS: As we're here talking about hatchlings, also I believe there is some issue with the Devour skill. Often the pet just refuses to sacrifice, usually that happens in a more intense fight with freeps. Even when the targetted npc is next to me and the pet is attacking it, he Devour doesnt work. I go out of combat, enter another fight and poof, my hatchling sacirifices itself at the very beginning of the fight with me fully healthy and not even touching the Devour skill.
But this bug would be just a bonus one.

So...please, fix the Scytode Brood.

Thank you!

http://lorebook.lotro.com/wiki/Updat...fficial#Weaver

Turbine claiming to have possibly "fixed" the issue yet never revisited in future notes.

Originally Posted by tnak

http://lorebook.lotro.com/wiki/Updat...fficial#Weaver

Turbine claiming to have possibly "fixed" the issue yet never revisited in future notes.

This was the fix? -

Scytode Brood: Auto-attack cooldown reduced from 3s to 1s.

From what I see trying to use the ranged hatchling, it only auto-attacks once, right after I tell it to apply it's poison or start attacking. Then it just stands there looking angry until it's poison is off cd, when I then must tell it to use it again, since it won't auto-apply it's poison even with it toggled on auto.

Originally Posted by Moejo

This was the fix? - From what I see trying to use the ranged hatchling, it only auto-attacks once, right after I tell it to apply it's poison or start attacking. Then it just stands there looking angry until it's poison is off cd, when I then must tell it to use it again, since it won't auto-apply it's poison even with it toggled on auto.

This was them acknowledging that there is a problem with the scytode brood ranged pet...yet they never bothered to act on it.

No mention of this getting fixed in RoR?

./signed
Fix them both please

Do what you promised 8 months ago

/signed for the Scytode fix.

/signed for the Devour fix.

I heard that server lag thing somewhere as well. The best way to get it looked at will be to /bug it and talk it up in threads like this.

Devour has an animation. If you click another skill before the animation finishes it cancels the Devour. The pet also appears to have to be within a set distance to execute the Devour so hitting another skill before it is in range may also cancel it. I could be wrong on this but I've found hitting Devour and then waiting usually works. I agree this is a pain and the skill should be an instant fire.

/signed for fixing the ranged pet (mine was losing 1v1s vs eagles with me hammering its skill commands as soon as they were off cool down.

/devour My problem with devour is that if I try to use it near the end of a fight and drop out of combat before the skill goes off, the pet isn't eaten and if you don't dismiss and resummon it it will be eaten the next time you enter combat. The requirement for being in combat also means you can't use it to just top-off between fights.

Best possible fix would be to make it a non-targeted, anytime (in or out of combat) skill, just eat the hatchling anytime it was in range. Even if they left everything else, including the requirement that the pet not be stunned that would make it much better. That would fix the burgler hips situation listed above, my end-of-combat problem, and in general make it slightly less awkward to use.

Please fix my ranged pet!

/Signed

Originally Posted by morgoth315

I am becoming increasingly suspicious that Turbine does not read Creep forums, at least not very often. My suggestion is to have a good chunk of the weaver population report this bug every few days in-game until Turbine has to notice it. Be detailed in your reports.

Best bet is to head to a freep forum, start a thread titled "Festival Horse missing saddle strap" and then in that thread lay out your detailed explanation of the creep bug. You'll have 6 different devs reading your bug report in a matter of minutes.

You have to trick the devs into reading your creep related issues.

/signed. I'd much rather run with scytode brood if it was fixed.

i want it to be fixed tooo!

(i also want that melee pet is fixed so that he don't follow hips burg anymore. is simply cheating)

Originally Posted by Arlecchino79

i want it to be fixed tooo!

(i also want that melee pet is fixed so that he don't follow hips burg anymore. is simply cheating)

The pet dont follow burgs hipsing anymore, at least mine has not xD but a LM pet will still follow a dissapearing warg :/

Yep this has been bugged since FOREVER.

./signed