Bug Runeblade broken

[spiralz]

I noticed after the patch, as a Runeblade, that the runes I apply to my sword are no longer showing in chat the way they used to. It shows which rune I am applying as I do it, but not which runes I had previously applied to the sword to show the current state of applied runes. Along with AbsorbRunes being gone, I can't be sure which runes I have applied unless I go out of my way to hit something a few times in order to clear them.

 

[Pugglez_]

Try unsneaking. Sneaking causes your skill cast messages to be invis.

 

[spiralz]

Try unsneaking. Sneaking causes your skill cast messages to be invis.

I hadn't been sneaking at all. I was leveling Runewraith during the boost and took damage often so sneaking wasn't really necessary. The cast messages showed up, it was the private messages showing the chain-of-runes that didn't

 

[Irishman81]

@Naxet91 also informed me that the runes weren't even activating on hit...

 

[peterpunx]

So the runes are not working at all. Think its because they dont get charged into the weapon, so you dont apply them on hit.
When you use any rune skill, the msg appears, the mana is wasted and everything, but the advise saying what runes your weapon has, doesnt appear anymore.


It used to be:
[Skill] Naxet91 imbues his blade with rune of Fire.
Your sword is charged with: Ice, Void, Fire. (something like that, showing all the charges that u had)
Every 1sec you hit, apply one rune in order.


How it is:
[Skill] Naxet91 imbues his blade with rune of Fire.
When you hit, you do your normal left click damage, no silence from voidrune, no extra damage from anything, no toxic apply, no slow from icerune,...

 

[spiralz]

Yeah I guess I hadn't even realized the runes themselves weren't activating since I don't see the damage indicators anymore.

 

[Delfofthebla]

Uh oh.

Man I hope it's some silly issue that doesn't require much work to be fixed.

If the Runeblade code has to be altered much to accomodate a change to spigot or something, that class is probably bricked. That is unless Kainzo has someone who actually knows how to code on his team right now (Hint: not NuclearCouch). The skill code for Runeblade is a bit...different than the rest. Unfortunately it was not an easy concept that could be put together in a few simple skills, and it required a bit extra work to get everything working properly.

In the past, if one skill for Runeblade broke, they all broke. And unfortunately, Runeblade without Runes aint much of a class

EDIT : I heard they removed AbsorbRunes.

AbsorbRunes is the "Rune Controller" skill. Without it, Runeblade will not work. At all. If they want to fix this bug, they must put that skill back in the game. There is no way around this. One skill must be the "controller" for rune skills. They can move the code around if they know how, but the easiest fix is to just put absorb runes back into the game.

 

[MunchlaxHero]

Uh oh.

Man I hope it's some silly issue that doesn't require much work to be fixed.

If the Runeblade code has to be altered much to accomodate a change to spigot or something, that class is probably bricked. That is unless Kainzo has someone who actually knows how to code on his team right now (Hint: not NuclearCouch). The skill code for Runeblade is a bit...different than the rest. Unfortunately it was not an easy concept that could be put together in a few simple skills, and it required a bit extra work to get everything working properly.

In the past, if one skill for Runeblade broke, they all broke. And unfortunately, Runeblade without Runes aint much of a class

EDIT : I heard they removed AbsorbRunes.

AbsorbRunes is the "Rune Controller" skill. Without it, Runeblade will not work. At all. If they want to fix this bug, they must put that skill back in the game. There is no way around this. One skill must be the "controller" for rune skills. They can move the code around if they know how, but the easiest fix is to just put absorb runes back into the game.

No one knew this the only reason we removed it was because the actual skill is useless, the controller is not and was unknown to us @malikdanab

 

[spiralz]

No one knew this the only reason we removed it was because the actual skill is useless, the controller is not and was unknown to us @malikdanab

How is that skill useless? What if I no longer want to have IceRune, VoidRune, IceRune on my sword and change it to something else? Was I supposed to go out of my way to find some creature to use it on in order to clear the chain?

EDIT : I heard they removed AbsorbRunes.

AbsorbRunes is the "Rune Controller" skill. Without it, Runeblade will not work. At all. If they want to fix this bug, they must put that skill back in the game. There is no way around this. One skill must be the "controller" for rune skills. They can move the code around if they know how, but the easiest fix is to just put absorb runes back into the game.

Whew, sure glad you passed through to grace us with useful knowledge. Now maybe I can leave my base again sometime soon.

 

[WitchOnaRampage]

AbsorbRunes is the "Rune Controller" skill. Without it, Runeblade will not work. At all. If they want to fix this bug, they must put that skill back in the game. There is no way around this. One skill must be the "controller" for rune skills. They can move the code around if they know how, but the easiest fix is to just put absorb runes back into the game.

Thanks, Delf.

@malikdanab

 

[Trazil]

plz come back @Delfofthebla

 

[Delfofthebla]

plz come back @Delfofthebla

Sorry, no can do.

No one knew this the only reason we removed it was because the actual skill is useless, the controller is not and was unknown to us @malikdanab

As an old Runeblade player, and as, you know, the guy who made it--I reject this statement.

There are times when your entire rune queue is...not suited to your current situation. In such event, the ONLY way to get the rune you need on your very next attack, is to clear the entire list and pop the rune you need.

The most common desire to do this is for VoidRune.

Assuming your RuneQueue is as follows:
<ToxicRune|FireRune|IceRune>
Or
<ToxicRune|FireRune|VoidRune>
Or even
<ToxicRune|VoidRune|IceRune>

And you see a wizard casting Bolt, or ArcaneBlast.
If you are a filthy casual, you will simply keep spamming left click in hopes that you will kill him.
If you are not a filthy casual, you will pop AbsorbRunes, followed by VoidRune, and then silence him before he is able to get his bolt off.

I did this aaaallll the time in teamfights. I mean, don't get me wrong, it's a specific use case to a not entirely common situation, but the fact of the matter is, it happens.

In most situations your RuneQueue is empty mid fight, but if there is any amount of downtime at all you should be refilling it with runes. And sometimes, Void just isn't going to be the first thing on the list. Maybe it was on cooldown, maybe you didn't think you'd be fighting a caster in the next 20 seconds, or maybe you just fat fingered the wrong Rune. But if you need a specific rune at a specific moment, the only way to make it so, is to clear the queue.

AbsorbRunes is useful.

 

[JacobBurkey]

No one knew this the only reason we removed it was because the actual skill is useless, the controller is not and was unknown to us @malikdanab

Pretty sure you've never played runeblade and you're calling the skill useless. lol. Absorbrunes is such a useful skill, as Delf stated.

 

[Kainzo]

I pushed a hotfix to re-add AbsorbRunes, give it a shot now.

 

[MunchlaxHero]

Nvm