What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Inevitable discussion thread for Tripwire event on 30-Jun-2016

Status
Not open for further replies.
Blizzard could definitely look at these forums, see the time of the tripwire, find a peak 5 second period of logouts, then investigate all those accounts. But honestly that's about as threatening as player reports, which we deal with every day.
 
Blizzard could definitely look at these forums, see the time of the tripwire, find a peak 5 second period of logouts, then investigate all those accounts. But honestly that's about as threatening as player reports, which we deal with every day.

It'd be easy for them to catch me, I'm using my real name. Haha!
 
HB will shutdown your Wow client and honorbuddy just to save you from getting caught.
 
You really need to stop talking about the tripwire like you know what you're talking about....

Yes, in fact, every user that had HB running at the time the event occurred was kicked and logged off from wow.

You seriously need an education...and get your head out of your rear!

The following error, is not Tripwire...
Code:
Session with specified sid does not exist in NorthAmerica region.
Shutting down in 20 seconds

It may have been related but as Tony has recently stated multiple times the error is server and/or network related. It does and did not kick users off from an active WOW connection. I and other accounts were still online.

So, lets quote what I stated:
What exactly is that going to prove or cause a red flag? Just because HB Tripwire activated doesn't mean users were kicked or logged off from World of Warcraft. Apples to Oranges.

Interesting to note and reiteration, I had a WOW account still online and never kicked or logged off when the sid error displayed. The only issue I had is HB wasn't able to stay online, since there was obviously an AUTH issue. So, I posted the issue within support, then went back to the arena in WOW. Then 20+ minutes later peons screaming Tripwire, sad to say I was STILL online in the arena, was HB active on my end? No, because of the issue with the sid server network issue disallowing a connection. So, does that mean every single user who in fact were affected by the sid server network issue were kicked or forced log-off from WOW via Tripwire activating? Absolutely not.

Users that were kicked off from WOW via Tripwire is a different story, but does NOT prove anything to Blizzard that those particular users are using HB.
 
Last edited:
Don't spread lies...tripwire saved us recently and I'm still not banned :D

The buddy developers are doing an incredible job to keep us safe!! Very difficult against blizzard corporate machine than can afford to hire the best of the best, the buddy team are smart cookies! :)

my 2 accounts have survived the last 2 tripwire events, before that they werent active yet :P so Yeah I'd say things are looking good :)
 
So far the ban thread is quiet and i have 3/3 still active. so hopefully it was stopped in time this time.
 
You seriously need an education...and get your head out of your rear!

The following error, is not Tripwire...
Code:
Session with specified sid does not exist in NorthAmerica region.
Shutting down in 20 seconds

Go ahead and show me a log when the tripwire occurred that you stayed connected to the bot and wow...I'd love to see it.

And go ahead and go back and look at threads started when other tripwire events occurred...Guess what you'll see? A whole bunch of threads showing sid errors at the same time tripwire events occur...So yes, they are related.

I'm sure Raphus (an actual programmer, not a forum mod) would be happy to come into this thread and verify that the 2 are related.
 
Last edited:
So any news? I don't see any update on what it is about or the estimated downtime..


Well , Raphus He did tell it was Blizzard´s Warden that tried to scan for Honorbuddy.

No est time when HB is up yet though.

- Caper
 
Go ahead and show me a log when the tripwire occurred that you stayed connected to the bot and wow...I'd love to see it.

And go ahead and go back and look at threads started when other tripwire events occurred...Guess what you'll see? A whole bunch of threads showing sid errors at the same time tripwire events occur...So yes, they are related.

I'm sure Raphus (an actual programmer, not a forum mod) would be happy to come into this thread and verify that the 2 are related.

You clearly can't comprehend plain English.

Do you need me to come over to your home, hold your hand and explain to you the issue like a child?! Clearly over your head. lol. Pathetic really.
 
Last edited:
You clearly can't comprehend plain English.

Do you need me to come over to your home, hold your hand and explain to you the issue like a child?! Clearly over your head. lol. Pathetic really.

I'm gonna go ahead and provide you a snippet of a log proving that both you and Tony are wrong...Go ahead and read it carefully:

[00:09:56.141 N] Tripwire activated. Shutting down honorbuddy
[00:09:56.165 N] Wow exited, Honorbuddy stopped!
[00:09:56.165 Q] Bot stopping! Reason: Wow exited, Honorbuddy stopped!
[00:09:56.165 N] Honorbuddy terminating in 20 seconds.
[00:10:00.231 Q] Session with specified sid does not exist in NorthAmerica region.
[00:10:00.372 Q] Shutting down in 20 seconds

This is the exact second that the tripwire event occurred. Go ahead and look what that those first lines say. The second tripwire occurred, all wow sessions were closed. Oh look what that is the 4 seconds later....A sid error...

The network error occurred because tripwire activated...Anyone with any knowledge of networking can understand that.

Your condescension isn't needed here. Maybe get some knowledge on these issues before you keep making yourself look like a fool.
 
Lmfao @ your extremely failed attempt at log proof.

You do realize you shared something AFTER tripwire, correct?

Show your log DURING tripwire where you claim you were on for 10 minutes longer.

Or did that log get deleted?
 
The only fool here is you.

Code:
[00:17:16.234 D] Activity: Honorbuddy Startup Complete
[00:17:16.234 N] Honorbuddy Startup Complete
[00:17:35.741 Q] Session with specified sid does not exist in NorthAmerica region.
[00:17:35.845 Q] Shutting down in 20 seconds
[00:17:55.884 D] Removed hook [InGame_Check] 
[00:17:55.885 N] [ReleaseMe] Disabled v0.0.1
[00:17:55.885 N] [UltiBuffer]: disabled

Roughly 20+ minutes later

Code:
[00:42:28.291 N] Honorbuddy v2.5.15239.828 started.
[00:42:28.695 D] Reloading AssemblyLoader<BotBase> - Initializing bots
[00:42:28.695 D] Reloading AssemblyLoader<HBPlugin> - Initializing plugins
[00:42:28.695 D] Reloading AssemblyLoader<CombatRoutine> - Initializing routines
[00:42:29.737 N] Logging in...
[00:42:31.656 D] Logging in to NorthAmerica (192.99.20.72)
[00:42:31.820 N] Tripwire Active, shutting down Honorbuddy!
[00:42:34.620 N] Compiler Error: J:\Honorbuddy\Plugins\ClearTarget\ClearTarget.cs(23,30) : error CS0115: 'SupremeTargets.Initialize()': no suitable method found to override
[00:42:36.821 N] TRIPWIRE

Post the full log. Please. The full log where you were on. What you showed was two new honorbuddy sessions starting up. Please post the full unedited log.
 
This Is directly from http://wiki.thebuddyforum.com/index.php?title=BosslandGmbH:HelpDesk:Is_Botting_Safe?

Game owners tend to hand out infractions in 'waves'...
The important thing to note here is when your account is taken offline, the detection probably happened days, weeks, or months prior. What you were doing when the account actually went offline (or the couple of days before) is probably not the reason for the infraction. There are some notable exceptions to this—most of them involve player reports, or exploiting the game world.

The game owner issues infractions in 'waves' for several reasons:
-By far, the main reason is they do not wish to give the bot makers a clue as to what exactly is being detected.
This prevents the bot makers from taking decisive and immediate counter-measures.

-Has a measurable psychologic impact to the botting communities.
The technique is quite effective, and actually does scare people into ceasing to bot.

-Gives their non-botting playerbase much joy
These people savor the mass of bitter tears and "boo hoo"ing that occurs in the botting community after a ban.

-Creates a financial windfall for the game owner
Most botters immediately go out and buy fresh copies of the game—particularly if it is 'on sale'.

It is not uncommon for a game owner to penalize an account that has been idle or inactive for months. When you are detected, you are put on a list for future punishment. During each wave, the list is processed according to rules only known to the game owner. We have observed that some accounts remain on the list for future action. This is meant to create confusion in the botting Communities as to the specifics of how a botter got caught. Thus, if "they missed you in this ban wave", you are most likely still on the list and will be punished at a future date that will make no sense to you, whatsoever.


If any of you haven't read this, I implore you. It has great information that answers alot of these "Tripwire activated but I haven't been banned yet!" Mentalities.
Just because the event (That almost literally just happened) did not cause you to become immediately banned, does not mean you are free and clear.

As this section says, they have been known to put people on a list for future punishment. Read this next section carefully.

This post explains the 'official' reasoning for this. In reality, suspending an account instead of perma-banning has these benefits for the game owner:

-When pressed for subscriber numbers, the game owner can include the suspended accounts
Since the last account status was 'active', they can legitimately include them in the subscriber numbers when reporting financial health to shareholders, or trying to demonstrate 'leadership' in the industry.


-Owners of suspended accounts will frequently buy new accounts while they wait for the suspension to be lifted
This has the effect of artificially inflating the subscriber numbers.

Note the underlined text. Now if we think about it: what major event happened that would really benefit Bliz monetarily?....Thats right! The movie.
If we think logically about this, because of the strategic time placement for the Warcraft movie, Bliz subscriber count has sky-rocketed from the last 6 months in from hype of the movie, and in anticipation of Legion.
Also, Bliz has stopped posting their subscriber counts publicly due to poor numbers, but with this, now they have the ability to boast again.

So for the TL:DR form, Don't get cocky. Just because you haven't been banned less than 12 hours since the event, does not mean you are safe. Maybe when their numbers are at their highest, (Potentially after Legion release) Bliz will start culling the herd. Taking these lists they have been making and wiping the slate clean.


Sincerely,
Someone who just got their account back after the December 16th banwave.

P.S. READ THAT FORUM POST TO COMPLETION>
 
Because I posted a snippet, as he did, imbecile.

To fend of the masses of illiterate people.

Quite amazing how stupid you people really are!

Code:
Log attached

Hey can we keep it civil here? Calling of names is against the forum rules
 
Status
Not open for further replies.
Back
Top