Printable View
Anyone else got the feeling that after the very latest update (carapaces implementation of that 1.5 secs delay) glowsticks and nilbogs dot aa does not work as intended anymore, ie. you can get cursed and die with both aa's up and running now ?
Spoke to some ppl who run m5/6 like me and they have got the same feeling. Have been told that a loot of ppl complaining about glow and nilbog in guildchats now.
What's your opinion ?
My Glowstik is working just fine.
** Edit **
(while the below post is waiting for approval, I added updated info below to the post)
This morning I put together a party to test nilbog and glow's aa. I think the aas' are woking fine. Some players who are new to using glowstik dont realize there is an 8 secs cool down between using a second glowstik's aa. Similar to nekro, players can't stack their aa. Glowstik's pools have nothing to do with giving curse immunity, same with nilbog's aa pools.
At one point we had 4 mages in a mob, zero issues with aa not properly working. We all had nilbog equipped. I had nilbog's aa slotted in Nekro. We tested many different ways, the only time we died was when the second glow's aa for the immunity on dot was used too soon, leaving party vulnerable to curse.
I also tested nilbog's aa in elite southern gates, the aa seemed to be working properly against stuns. Nilbog's aa also removed the cocoon from the spider in graveyard.
The other day when I was having issues with curse and aa, I really feel now, it was due to a graphic lag issue I was having. After swiping shut my ap, I have had zero issues.
Big thanks to Sakurab, Siner, Hellsminion, and Aisanz for helping test this.
previously...I do agree, something is off with Glow's and Nil's aa. Hit nilbog's aa when I agrro'd mage, then died from curse. Also was in party when entire party was wiped put from curse, glow's aa was active.
Had a same situation with nilbog and hes AA seems dont work properly...Quote:
Originally Posted by Avaree
I don't know much about Nilbog, but I ran with someone today and it wasn't doing much for the pt against the curse mages, my glow has been working fine today, I think it might just be getting used to the new timing after the update and lag as far as glow goes but Nilbog does seem different
Didn't try Nilbog but I saw same situation yesterday too. I used glow but whole team died twice. I thought my glow got stuck somewhere and was too far or speed set issue. Maybe there is some glitch on them.
Don't use Nilbog AA if Glowstick AA is on.. Nilbog's pool thingy seems to cancel the Glowsticks' pools :D
I don't think so. But if u r right it was not the case before the update. Did a huge amount of runs with both, glow and nilbog in party. Dot Immunityis not related to the pools anyway as far as I remember.
Funny you should mention this, but yes, I find that the 1.5 seconds has actually made things worse with glowstick. It's less time to react. Moreover, the shield still doesn't last 6 seconds. It's more like 4.
U gave me great idea.Quote:
Originally Posted by Elichka
Ill use stampy when someone using glowstik! :@
Btw we talking about pve not pvp (:
gg arcane glowstik, heroic pets are the new dawn with legendary AA ?? o.o"
I did some additional runs in the meantime and I think I figured out one of the problems/bugs.
Lets see if i can put it in understandable english.
Once u fire up glows or nilbogs aas before u attack a mage to avoid being cursed for 5/6 secs (dot immunity) everything works fine if u are fast enough to kill the mage.
Now: Before the update it was possible to "break" the curse once the warning popped up by pressing glows or nilbogs aa.
In 95% of the cases now that does not work anymore. Now, once the warning pops u get cursed anyway regardless if u press aa.
Looks to me as if under certain conditions the responsible subroutine for the check "pressed aa ?"is skipped.
This morning I put together a party together to test nilbog and glow's aa. I think the aas' are woking fine. Some players who are new to using glowstik dont realize there is an 8 secs cool down between using a second glowstik's aa. Similar to nekro, players can't stack their aa. Glowstik's pools have nothing to do with giving curse immunity, same with nilbog's aa pools.
At one point we had 4 mages in a mob, zero issues with aa not properly working. We all had nilbog equipped. I had nilbog's aa slotted in Nekro. We tested many different ways, the only time we died was when the second glow's aa for the immunity on dot was used too soon, leaving party vounerable to curse.
I also tested nilbog's aa in elite southern gates, the aa seemed to be working properly against stuns. Nilbog's aa also removed the cocoon from the spider in grave yard.
The other day when I was having issues with curse and aa, I really feel now, it was due to a graphic lag issue I was having. After swiping shut my ap, I have had zero issues.
Big thanks to Sakurab, Siner, Hellsminion, and Aisanz for helping test this.
(I will edit my above post from yesterday)
Ava
This morning I put together a party together to test nilbog and glow's aa. I think the aas' are woking fine. Some players who are new to using glowstik dont realize there is an 8 secs cool down between using a second glowstik's aa. Similar to nekro, players can't stack their aa. Glowstik's pools have nothing to do with giving curse immunity, same with nilbog's aa pools.
At one point we had 4 mages in a mob, zero issues with aa not properly working. We all had nilbog equipped. I had nilbog's aa slotted in Nekro. We tested many different ways, the only time we died was when the second glow's aa for the immunity on dot was used too soon, leaving party vounerable to curse.
I also tested nilbog's aa in elite southern gates, the aa seemed to be working properly against stuns. Nilbog's aa also removed the cocoon from the spider in grave yard.
The other day when I was having issues with curse and aa, I really feel now, it was due to a graphic lag issue I was having. After swiping shut my ap, I have had zero issues.
Big thanks to Sakurab, Siner, Hellsminion, and Aisanz for helping test this.
(I will edit my above post)
Ava
Well, after reading Avarees additions to his post I asked myself why things seem to work for him but not for me.
In another thread I found some info what device he's playing on and it turns out he's using Apple with iOS and I myself use different android devices. Could this be the problem ? Turns out it seems so.
Mainly i am playing AL on a modern Android 7.X 64-bit device with more th enough horsepower and ram to handle AL.
So, why are these problems then ?
Tested with an old Android 6 32-bit yesterday and had no problems at all.
Strange.
It turns out that STS seems to use a rather old developers kit witch does not optimize the code for newer androids, ie. the client can't coop very well with 64-bit and all the additional functionality Google implemented when it comes to improve battery life.
What I have to do now, after the update, is to go to application level and to switch of all these automatic functions for AL giving me a huge improvement in gameplay. Why this is necessary now, after the very latest al update but wasn't before is a question for the devs. I don't know.
Perhaps timing problems in a multi threaded environment ?
I don't think that is the case. It will probably not effect a gameplay issue if you have 64 bit or 32 bit device as long as they are both Androids. But, if you speak about performance, yes, iOS has never slow downs, because its locked at 60fps and it runs smooth. As of Android, no matter what device you use, no matter how powerful it is, the game will have slow downs all the time, because Android OS is locked at 30fps.Quote:
Originally Posted by Minisalami
PssstQuote:
Originally Posted by Minisalami
(Avaree is a she)
There is no frame limit on newer android versions but some developers give u the advice to limit frames to 30 especially when using GL.
And: There must be differences between the 64bit and the 32bit Versions of Android when it comes to AL. Crosschecked with an even more piwerfull friends tablet running Google's latest stock rom with the very latest patches. Shows the same issues compared to 32bit now. I.e. u have to switch off all the options regarding background services and optimizing of screen resolution und frames per second.
Not necessary for the 32bit Versions we tested on.
Another strange behaviour occurs now when it comes to ending offers in auction and to collect ur gold. U now get that "An Error has ....." message all the time unless u wait in between the keypressing for sevarel seconds now. Gone with background service optimization disabled and doesn't happening on 32bit Androids at all.
P.S. Noted that "He" is a "She" ;)
P.P.S: With that Background Optimization thingy switched off AL is a real battery drainer now.
AL was always battery drainer.
Android bothers me because it haves little lag, slow down on every device, while iOS runs the game so much better, so smooth, the difference is huge.
And btw, that Error that you get while retrieving gold from selled items in auction, i had the problem at old 32 bit device, 64 bit Nexus, and i still have it at iOS.
Glow AA shield failed few times for me if someone uses nekro AA.. I was told few of them encounter this problem running on Mol map too
When I see warning from the mages,I click on nilbog aa to avoid to be cursed.
In 4/10 times aa doesn't work properly,or seems mage curse a lot faster than the warning...
Rogues trap doesn't pull every time too...
In 3/10 cases trap pull enemies,otherwise don't work...
If any dev can take a look,would be appreciated.
You tested it wrong. Nilbog only grants 1 second immunity now while the description says 5s. This is a bug that should be patched during the coming weekly update. Hope that devs are aware of this.Quote:
Originally Posted by Avaree
Could devs look into mages gale cancelling trap pulls please?Quote:
Originally Posted by johnycageee
Traps only have a 20% chance to pull with the "net retraction" upgrade, unless using glintstone set, which is 100% pull and in order for that to properly work you must have that upgrade selected too.Quote:
Originally Posted by johnycageee
:) I am only stating what I see and experienced for myself. Remember I am not a dev, nor do I have their tools to run all the data. There are many variables that come in to play, e.g. how far away glow/nilbog is from party when his aa is used (party needs to stay in range of aa), pet(s) cd, aa timing as 2 glows' aa dont stack, ping, and the d.o.t. skills/damage a player puts out prior to receiving aa immunity on d.o.t. from curse. Also not to forget is a player affected with the mage's other spell that creats d.o.t., that appear to stack.Quote:
Originally Posted by Abuze
I too am waiting to hear what the devs discovered :) As with anything, if its broke it needs to be fixed.
I run mausoleum with glint set and have 5/5 trap upgrades and still at times my trap pulls are cancelled. I suspect this might be from Mages gale skill but I could be wrong. When I mention that it might have to do with the gale skill I don't mean that traps don't work when the gales knock back is in effect but rather after the knock back duration.
@Ava I know but just adding that since it seemed to work "fine" according to you.
the mages should have 2 secs warning not 1.5. My nilbog's aa is always late if I activate the AA after I saw the warning sign
Mentioned that to carapace some time ago because of maus terrible lagging even with a green ping. 2.5 would be even better.
Lag has nothing to do with the servers. Its all you.Quote:
Originally Posted by Minisalami
That is wrong.
I have this problem after update too. And is not due to lag. Not due to glowstik or nekro aa cooldown. Just purely dont work sometimes.
I'm not saying anything concerning the thread's topic itself, but about this post: If the servers are overloaded (I don't know if they are), then they can start "to react more slowly" - which may be seen as lag, from the client devices. Lag from network connection is a separate thing, yes - it's another(,additional) delay.Quote:
Originally Posted by Abuze
Sorry I worded that incorrectly. At this moment there's nothing causing wrong with the server that might cause lag.Quote:
Originally Posted by voidPtr
Minisalami was on about newer devices having more lag compared to the older ones which is false too. I'm using Samsung Tab S and no lag issues at all, if there is lag it's my own faulty internet connection.