Tested similar steps (not with GM char) and saw:
.get succeeded - Fredrikstad (5297) life is 6243 (1 base + 1656 mod + 0 trickle + 4586 custom).
Fredrikstad (5297)
health 4830
.ge…
@Oatbag, @Hayedid, @faffywaffle or someone else feel free to validate the steps when you have time. :)
So, I don't agree that this issue is "verified", sure - I've seen lag happen in scheol, but I've also seen it happen serverwide. If we want to have this focused on, players need to make more of an…
Based on the level of detail of this report I'm going to mark this as unrefined as it's not enough details to reproduce and it's not enough to set a proper priority. it feels like a prio 4. Please…
Thanks for reporting this Klex, but as we see it we're not able to reproduce what you're saying on live so we're struggling to understand the issue based on your description. Next time, could you…
Did a quick comparison on live - there's only one nano running there. and it cycles "hidden" if so, as there's no changes in programs running between the periods where attacks are partially…
This is a bit of a fun one. Attempted as my doc. Equipped a nano targeting helper ( .item 269184 269184 25 ) on it, while the Nano Targeting helper is equipped, for each tick of the DoT I cast.…
Obviously not the solution for this, but wanted to report that doing .set currentncu 0 "took", also after zoning. Will be interesting to discover what initiates this. Sync issue between character…
Cool catch by @Oatbag .. it's obviously in the npc's cashable nano's list:
Wings of the Phoenix
Wind Slicer
Wilderness Protection
Vengeance of Nature
…
@Neph : nice reproducible steps. I attempted this a couple of times myself and just hadn't written up a ticket about it. thank you!
I might be wrong on this one @benutztername - but the Redeemed at 1814.4 594.2 y 64.5 4312 no longer turns into birds upon death. As I'm not sure if you experienced this while they were alive or…
Coords in bytebin was not for location of Hwall. I checked that:)
I... can't get this reproduced 100% either, unfortunately.
We're aware that there is an issue but without concrete steps to reproduce it's impossible for us to fix this.
with the steps provided, I'm not able to reproduce. feel free to re-open if steps to reproduce can be improved so that we get a consistent occurrence. as this can be chalked up to server-client…