Celtic Heroes

Who cares why it wasn’t addressed before. Would you rather them continue to not address it? Kudos to OTM for finally doing something.

Who cares why it wasn’t addressed before. Would you rather them continue to not address it? Kudos to OTM for finally doing something.

Who cares? Obviously me. The point of my post is to point out how negligent OTM is when it comes to fixing issues, it doesn’t really seem like it was an issue back when it was happening as OTM obviously did nothing to stop it from happening. Yes I guess we can say kudos for finally doing something, it only took a few years after the original incident that seemed to be ignored.

So to answer your question, no I would not prefer them to be negligent of things that need to be fixed, I would rather it just get fixed to begin with rather than waiting for it to happen again.

Who cares why it wasn’t addressed before. Would you rather them continue to not address it? Kudos to OTM for finally doing something.

Who cares? Obviously me. The point of my post is to point out how negligent OTM is when it comes to fixing issues, it doesn’t really seem like it was an issue back when it was happening as OTM obviously did nothing to stop it from happening. Yes I guess we can say kudos for finally doing something, it only took a few years after the original incident that seemed to be ignored.

So to answer your question, no I would not prefer them to be negligent of things that need to be fixed, I would rather it just get fixed to begin with rather than waiting for it to happen again.

Because previously the exploit was very rarely used for resetting bosses.

Its recent resurgence in popularity as a griefing technique against other clans was cause for review.

Who cares why it wasn’t addressed before. Would you rather them continue to not address it? Kudos to OTM for finally doing something.

Who cares? Obviously me. The point of my post is to point out how negligent OTM is when it comes to fixing issues, it doesn’t really seem like it was an issue back when it was happening as OTM obviously did nothing to stop it from happening. Yes I guess we can say kudos for finally doing something, it only took a few years after the original incident that seemed to be ignored.

So to answer your question, no I would not prefer them to be negligent of things that need to be fixed, I would rather it just get fixed to begin with rather than waiting for it to happen again.

Then set up your own small independent games software house, then you can feel free to fix every issue with your own MMORPG the instant that they are reported.
Just be happy that it's finally being resolved.

Who cares why it wasn’t addressed before. Would you rather them continue to not address it? Kudos to OTM for finally doing something.

Who cares? Obviously me. The point of my post is to point out how negligent OTM is when it comes to fixing issues, it doesn’t really seem like it was an issue back when it was happening as OTM obviously did nothing to stop it from happening. Yes I guess we can say kudos for finally doing something, it only took a few years after the original incident that seemed to be ignored.

So to answer your question, no I would not prefer them to be negligent of things that need to be fixed, I would rather it just get fixed to begin with rather than waiting for it to happen again.

Because previously the exploit was very rarely used for resetting bosses.

Its recent resurgence in popularity as a griefing technique against other clans was cause for review.

So when it was used in the past, on some servers it actually happened quite a lot, it wasn't a problem but now that its being used again its a problem. Thanks for the clarification.

Who cares why it wasn’t addressed before. Would you rather them continue to not address it? Kudos to OTM for finally doing something.

Who cares? Obviously me. The point of my post is to point out how negligent OTM is when it comes to fixing issues, it doesn’t really seem like it was an issue back when it was happening as OTM obviously did nothing to stop it from happening. Yes I guess we can say kudos for finally doing something, it only took a few years after the original incident that seemed to be ignored.

So to answer your question, no I would not prefer them to be negligent of things that need to be fixed, I would rather it just get fixed to begin with rather than waiting for it to happen again.

Then set up your own small independent games software house, then you can feel free to fix every issue with your own MMORPG the instant that they are reported.
Just be happy that it's finally being resolved.

With that logic then we should be happy that it takes a company years to resolve an issue, sorry but that's not something I expect from a company. This isn't obviously isn't just an "every issue" type issue.

So when it was used in the past, on some servers it actually happened quite a lot, it wasn't a problem but now that its being used again its a problem. Thanks for the clarification.

Could you link me to the previous posts and video evidence of this issue?

Just for clarification, as you appear to be misinterpreting my posts.

So when it was used in the past, on some servers it actually happened quite a lot, it wasn't a problem but now that its being used again its a problem. Thanks for the clarification.

Could you link me to the previous posts and video evidence of this issue?

Just for clarification, as you appear to be misinterpreting my posts.

Because previously the exploit was very rarely used for resetting bosses.

Its recent resurgence in popularity as a griefing technique against other clans was cause for review.

I said it happened in the past, not that there was people taking videos of it happening in the past. You said it yourself that it was used in the past, I just clarified that some servers actually used it quite a bit to grief each other. As I interpret your quote you said that its little use in the past didn't quite make it suitable for taking action, even though its still an exploit. Now since its being used again its grounds for review and taking action against those who do. Like I said I'm fine with this I just find no reason to why an exploit that can be used to reset just about any boss at any stage of the fight was overlooked when the developers had knowledge of it, other than the fact that it was "rarely used for resetting bosses".

So when it was used in the past, on some servers it actually happened quite a lot, it wasn't a problem but now that its being used again its a problem. Thanks for the clarification.

Could you link me to the previous posts and video evidence of this issue?

Just for clarification, as you appear to be misinterpreting my posts.

TBH it may have been before your time, but this was very commonplace during the Carrowmore expansion update. In fact it was so commonplace I was pretty sure it was intentionally in there. It could sometimes take 1 hour+ to Kill just a 165 or 170 because of constant resetting from all clans.

I’ll try and link you some topics later. The main reason I thought it was intentional on OTMs part was that a simple solution to fix it if no other, would be to remove the pillars and rocks on the boss rooms but this was never done.

I said it happened in the past, not that there was people taking videos of it happening in the past. You said it yourself that it was used in the past, I just clarified that some servers actually used it quite a bit to grief each other. As I interpret your quote you said that its little use in the past didn't quite make it suitable for taking action, even though its still an exploit. Now since its being used again its grounds for review and taking action against those who do. Like I said I'm fine with this I just find no reason to why an exploit that can be used to reset just about any boss at any stage of the fight was overlooked when the developers had knowledge of it, other than the fact that it was "rarely used for resetting bosses".

I never said "its little use in the past didn't quite make it suitable for taking action, even though its still an exploit" you have misinterpreted my post.

We have taken action against players for using it in the past, it however was not as prevalent an issue as it is currently. Hence the recent need to remind players that we will take action if caught doing so and reassuring those affected.

We have always planned to fix the issue, it's more recent usage has just called for it to be bumped up the priority list.

So when it was used in the past, on some servers it actually happened quite a lot, it wasn't a problem but now that its being used again its a problem. Thanks for the clarification.

Could you link me to the previous posts and video evidence of this issue?

Just for clarification, as you appear to be misinterpreting my posts.

TBH it may have been before your time, but this was very commonplace during the Carrowmore expansion update. In fact it was so commonplace I was pretty sure it was intentionally in there. It could sometimes take 1 hour+ to Kill just a 165 or 170 because of constant resetting from all clans.

I’ll try and link you some topics later. The main reason I thought it was intentional on OTMs part was that a simple solution to fix it if no other, would be to remove the pillars and rocks on the boss rooms but this was never done.

I linked SEVERAL topics before this post was created.

I’m not even gunna deny that I reset garanak 100+ Times On ResUrgeNs in summer of 2014 without a peep from OTM about abuse even though they replied to several forum topics about it saying they’ll look into it. It was 100x as common in 2013/2014 to reset a boss than it is Today.

Look at Mahon, I taught just a few players how to reset garanak and the entire server flipped from Elite being top dog into Wolfgang due.

Hell now I think I’m going to video target lock as a bug, while it is in the game it’s not being fair that I can do 80% of a bosses health as damage and still not get the kill. Obviously keeping a rogue at lvl 190 to outlock troll is mechanic abuse since you’re purposefully trying to get around target lock behavior???