Tripwire Event on 21 Jan 2016 12:12 UTC

[raphus]

We are aware of the Tripwire event that occurred on recently

If you are seeing this...

Logging in...
Tripwire Active, shutting down Honorbuddy!​

Here's what you need to know...

1. Don't Panic.
2. If you have other copies of Honorbuddy running that are not disconnected by Tripwire (not possible unless you're doing naughty things), disconnect them as soon as possible.
3. This Tripwire event is unrelated to any previous Tripwire activation. All this means is the game client was updated in a fashion that requires immediate investigation

If this is your first Tripwire event:

You can find more information about Tripwire here:

BosslandGmbH:HelpDesk:What is Tripwire?​

​

What happens now?

We are looking into the situation, and updates will be provided as soon information becomes available.​

What can you do?

• Don't make new threads regarding the Tripwire event.
• Don't spread false information, and don't speculate on things you can't possibly know.
• Please be patient—these things take time.

 

[raphus]

Status Update as of 21 Jan 2016 13:41 UTC

The event was raised by the new heuristics of Tripwire automatically. All we can say for now is that this event is not a false positive and investigation is still ongoing.

 

[Hawker]

It is going to be a day or so before we can re-open auth. Sorry but we can't say any more than this for obvious reasons.

 

[raphus]

Status Update as of 22 Jan 2016 18:39 UTC

We have gathered certain information on how we were detected in previous banwaves thanks to the recent data found by new Tripwire heuristics.

We would like to amicably warn everybody that the detection built-in to WoW client might catch any bot in the market that does injection.

Right now, we are working on a fix to avoid future detections and unfortunately we don't have any ETA as of now.

 

[raphus]

Status Update as of 23 Jan 2016 02:32 UTC

An internal build is currently being tested by Community Developers. We are hoping to do a release tomorrow if everything goes as planned.

 

[raphus]

Status Update as of 23 Jan 2016 11:22 UTC

We will be doing a new release shortly which will be avoiding the new detection mechanics.

We cannot know exactly when the new detection was rolled out for each WoW account. As the tripwire event indicated, it was found at 21 Jan 2016 12:12 UTC. It is possible that accounts running shortly prior to this time may be flagged, but from previous events we expect to see no bans on accounts that were inactive in the 12 hours prior to the tripwire event. Accounts active closer to the tripwire time are at a higher risk of being flagged.

It is safe to say that the detection was recently activated and accounts running before given time frames are not affected.

 

[raphus]

Honorbuddy v2.5.14790.811

 

[chinajade]

Issues with .811 known by the senior staff

Southeast Asia region is problematic as of 23-Jan-2016 00:22 UTC

The Southeast Asia region is having some problems. We've informed the senior staff.

In the meantime, as a work-around, please try the North America or Europe region. Don't use BestLatency. Also, be aware that a region switch can take up to 30 minutes to effect on busy days. More info here:

BosslandGmbH:HelpDesk:About Regional Infrastructure​

DX11/DX9 is not working for some

This is the normal troubleshooting tree for the causes (please try it first):

BosslandGmbH:HelpDesk:Video driver problem​

If the above article doesn't sort the issue, Raphus has made a Beta available that address the problem for some:

[post=2139871]Honorbuddy Beta for DX problem[/post]​

But, we're finding that even the Beta doesn't work for everyone.

So, if you still have problems after trying all of the above, please report the issue to the Support forum with a log from the Beta that illustrates the problem.

Ref: [post=378165][Guide] How to attach your log[/post]​

The issues are being actively investigated. Sorry for the inconvenience.

 

[chinajade]

Southeast Asia issue is fixed / DX issue still under investigation

Southeast Asia region repaired as of 24-Jan-2016 05:23 UTC

The senior staff is reporting that the issues with the Southeast Asia region have now been addressed.
It should be safe to switch back to that region, if it offers you lower latency.​

DX11/DX9 is not working for some

This issue is still under investigation.

Raphus has made an Honorbuddy Beta available that addresses the issue for most. Please give it a try, and if it does not work for you, please open a new thread in the Support forum, and attach the full log of the Beta.

Ref: [post=378165][Guide] How to attach your log[/post]​