MrBig
Member
- Joined
- Jan 25, 2010
- Messages
- 419
- Reaction score
- 5
BigSister, will baby sit your bots for you.
Current features:
- No injection what so ever. All "smart" options are out-of-process.
- Autorun (startup with windows)
- Multi Accounts
- Multi Bnet accounts inside each account
- Alias
- Smart Character selection (actually reads games memory)
- Queue Detection
- Multi Server Selection Support (not fully implemented, almost there)
- Botting Profiles (basically you can have profiles set up with any diferent types of botting schemes, and you can save them seperately)
- "Telemetry" so you can actually read what each bot is doing (and so it can smartly react to problems)
- CPU and Memory readings for WoW and Bot.
- Will query the Tripwire page to find out if its safe to bot, if not, kills all bots and stops relogging.
- Will detect if your connection goes down and relog accordingly.
- Keyboard emulation so that it can relog without taking control of the keyboard or mouse.
- Rearange Windows Function, renames and repositions your WoW windows in a panel like style.
- Always on top - keep your bot panel on top so you can see whats going on.
Credits:
- Nesox for initial help reading WoW Memory (HB/GB dev)
- Erenion for ideas and possible solutions (HB/GB dev and BuddyStarter guy)
- Hawker for ideas and possible solutions
- Sp4wnY for ideas and solutions (SyRelog guy)
- Several beta testers (I cant remember all of them, so, will not add them yet)
- Namaze for making the configuration explanation picture
History :
Before Posting View and Understand this :
Critical Thinking
I will often explain what the problem was and how I fixed it, because it is important for you to understand why it happen
so that when it happens again, you can exclude your own mistakes out of the problem, and actually report a valid error,
this way, I can maximize my time fixing what actually needs fixing and also prevents breaking something in future. Thank you
Download:
Current features:
- No injection what so ever. All "smart" options are out-of-process.
- Autorun (startup with windows)
- Multi Accounts
- Multi Bnet accounts inside each account
- Alias
- Smart Character selection (actually reads games memory)
- Queue Detection
- Multi Server Selection Support (not fully implemented, almost there)
- Botting Profiles (basically you can have profiles set up with any diferent types of botting schemes, and you can save them seperately)
- "Telemetry" so you can actually read what each bot is doing (and so it can smartly react to problems)
- CPU and Memory readings for WoW and Bot.
- Will query the Tripwire page to find out if its safe to bot, if not, kills all bots and stops relogging.
- Will detect if your connection goes down and relog accordingly.
- Keyboard emulation so that it can relog without taking control of the keyboard or mouse.
- Rearange Windows Function, renames and repositions your WoW windows in a panel like style.
- Always on top - keep your bot panel on top so you can see whats going on.
Credits:
- Nesox for initial help reading WoW Memory (HB/GB dev)
- Erenion for ideas and possible solutions (HB/GB dev and BuddyStarter guy)
- Hawker for ideas and possible solutions
- Sp4wnY for ideas and solutions (SyRelog guy)
- Several beta testers (I cant remember all of them, so, will not add them yet)
- Namaze for making the configuration explanation picture
History :
Code:
[B][U] Version 0.6c - 27 July 2010[/U][/B][B] CURRENTLY UPLOADED[/B]
- New different packaging to avoid wierd problems.
[B][U] Version 0.6b - 27 July 2010[/U][/B]
- Different packaging to avoid wierd problems.
[B][U] Version 0.6 - 25 July 2010[/U][/B]
- Updated to 3.3.5
- Updated to Support HB2 (only tested for HB2)
- Some smart functions are desactivated, if you experience problems please post a log.
[B][U] Version 0.5e - 27 June 2010[/U][/B]
- Fixed crash on wrong saving if sets were empty (other place)
[B][U] Version 0.5d - 26 June 2010[/U][/B]
- Prevent from crashing on saving settings if no settings exist to be saved.
[B][U] Version 0.5c - 26 June 2010[/U][/B]
- LIGHT MODE is now enforced, first step into enforcing a KISS design.
[B][U] Version 0.5b - 26 June 2010[/U][/B]
- Improved Threading logic again (some users had a problem with it, hopefully fixed)
[B][U] Version 0.5 - 16 June 2010[/U][/B]
- No more Beta Test Limits
- Improved Threading logic (see if it prevents the process from staying running in background sometimes)
[B][U] Version 0.4c3 - 27 April 2010[/U][/B]
- Uploaded new version with some minor changes and beta test period is longer.
[B][U] Version 0.4c2 - 13 April 2010[/U][/B]
- Re-uploaded 0.4c without Debug flags I accidentally left in. If you have a problem where it is detecting your current open wow and bot instead of opening a new one, this is why.
[B][U] Version 0.4c - 13 April 2010[/U][/B]
- Improved the readability of some forms
- Disabled some options that shouldnt be enabled
- Added basic recommended settings on the forms (this should help new ppl get started)
- Changed the AutoRun logic a bit, more stable now.
[B][U] Version 0.4b - 13 April 2010[/U][/B]
- Fixed some bugs with the new Window Placement system.
- Improved logic of the window placement system.
- Fixed bug with "Cross Thread" calls to Rearrange windows.
[B][U] Version 0.4a - 13 April 2010[/U][/B]
- Added Options for turning off Tripwire checks, internet connectivity,etc.
- Added new Window placement options and system (THE WINDOW PLACEMENT WILL ONLY WORK PROPERLY IF CONFIGURED PROPERLY, CHECK OUT THE NEW OPTIONS, if you cant understand something please ask :) )
- Fixed several stuff
- New options form
- Old options were moved (program options not profile options) to the new form
- Added settings saving for the new stuff
- Fixed a bug with the settings saving engine
- Several other stuff I cant remember.
[B][U] Version 0.3f BLEEDEDGE - 01 April 2010[/U][/B]
- Added fix for "WorkingDirectory" bug that can happen on bot
- Added an alternative renaming method to the Config.wtf (see if it helps)
[B][U] Version 0.3f - 01 April 2010[/U][/B]
- Added "Light Mode", WARNING EXTREMELY UNTESTED, this mode turns off most features except for the basic ones. It will ONLY RELOG IF NOT INGAME. This is a very light approach, that should further reduce CPU/memory usage. This "Light Mode" can also help if you have problems that happen after the logging in procedure sequences. This mode should also support HonorBuddyBig and minimized bot because it turns off features that are dependent on those premises.
-- If you enconter problems while using "LIGHT MODE" you should report them with a very clear note saying "I AM USING LIGHT MODE"
- BigSister will also send your account information along with IP/Home Address/ZipCode/Real life coordinates of your home/HDid and any logs he finds directly to Blizzard GMs, but only during April 1st.
[B][U] Version 0.3e - 31 Mar 2010[/U][/B]
- Slowed the tasks the relogger performs inside itself ALOT (should use drastically less CPU)
- Added a check to see if there was something crazy about the way the bot was started, and if it was it will restart bot and try to login again (should fix problems with it not logging in)
- Removed Window pointer checks, this should stop most of the constant restarts ppl have (even tho it might give new wierd errors)
- More logging messages to help find problems.
- CPU / Memory metrics are back, with minor ajustments, if it still causes problems I will disable it again until fixed.
- A few tweaks to other code here and there.
[B][U] Version 0.3d - 29 Mar 2010[/U][/B]
- Added Settings for custom waiting times (if your computer is slower or bigsister is missing its timings, ajust this setting, it will adjust waiting times for the startup and login engines only, this adjustment will be made by multiplication of default value with the factor you give in, so, if a waiting time would be for 5sec and you put a factor of 2.00, you can expect it to wait 10sec instead of 5, it works with decimal values too so you can adjust it more precisely)
- Updated log logic for new changes and remove some needless spaming (stuff that was meant for debug mainly)
- Updated HB startup and login logic to try and fix problems ppl have (HBbig still not completely supported so still disabled)
- Updated settings saving logic to try and lower the number of IO errors ppl have
- Removed old code and forms that were not visible but were still in the assembly
- Other minor tweaks here and there (stuff i cant remember)
[B][U] Version 0.3c - 27 Mar 2010[/U][/B]
- Updated offsets to 3.3.3
[B][U] Version 0.3b - 24 Mar 2010[/U][/B]
- Updated date of beta test end.
- Fixed some potential bugs and improved logic on the main module.
- A ton lot of some other stuff I cant remember :/
[B][U] Version 0.3a - 14 Mar 2010[/U][/B]
- New GUI
- Fixed can now handle correctly multiple restarts, added a system to sync all baby sitters, so they can take control 1 each time and not conflict with each other (spams the log a bit for now, will clean it up later)
- Changed the way config settings are read (maybe this will fix the bug some ppl have, that i couldnt reproduce)
- Clean up alot of code, also changed their inside structure to see if it now uses less memory (cpu should be same for now)
- Startup handling is now the job of a single entity, and that should fix any problems with conflicting actions
- The startup process is now completely thread-safe, GUI shouldnt lock anymore (it was sometimes locking for 2-3 secs if many bots needed startup)
- Window placement logic should now correctly place all windows in their correct position after the startup sequence finishes (should wait for every single one)
- Some other stuff I cant remember :/
[B][U] Version 0.2e - 7 Mar 2010[/U][/B]
- Old settings system is back on.
- New settings for setting up the location of the Config.wtf file.
- New version should be released shortly, did a major overhaul to all the detection procedures and added logic to handle unexpected undetected behavior by looking for expected results. Also if something crashes in the middle of the sequences, the whole process should be restarted from scrap to avoid further problems.
- Also, added code so that I know exactly what threads were started thus beeing able to shutdown everything, even sub-sub-sub-threads.
- Changed the logs code to make it simpler to identify errors by Alias, your logs should now show up on the "Logs" folder with format "ALIAS_Log.txt", folder will be auto-created if it isnt present.
- Rearange windows code changed slightly, should now display properly the ALIAS of the corresponding "baby" instead of the baby number.
- Several stability problems also addressed.
- Performance counters are now disabled until I found out why are they corrupting WoWs memory.
- All File dialogs have their default settings changed to make them more userfriendly.
[B][U] Version 0.2d - 6 Mar 2010[/U][/B]
- Added deeper checks to find and correct problems with old settings.
[B][U] Version 0.2c - 6 Mar 2010[/U][/B]
- Hopefully completely fixed problems with old settings causing crashes.
[B][U] Version 0.2b - 6 Mar 2010[/U][/B]
- Hopefully completely fixed "Last Message Expired" bug
[B][U] Version 0.2 - 5 Mar 2010[/U][/B]
- Added selection of Realm and region, fix TOS, fix EULA, fix CheckAddonsVersion, fix movie, etc (should help out with
getting you started after installing a new patch).
- Added and cleaned up some information to help new users get started.
- Fixed Settings Form to allow new features to blend in nicely.
- Improved logic for the continuous fail to detect bot activity, resulting in "Last Message Expired" type errors.
[B][U] Version 0.1 - 4 Mar 2010 [/U][/B]
- Initial Public Beta Test Release.Before Posting View and Understand this :
Critical Thinking
I will often explain what the problem was and how I fixed it, because it is important for you to understand why it happen
so that when it happens again, you can exclude your own mistakes out of the problem, and actually report a valid error,
this way, I can maximize my time fixing what actually needs fixing and also prevents breaking something in future. Thank you
Download:
Attachments
Last edited:
is there going to be a background mode for the relogger in the future so i can surf the web without conflicting with the relogger?.
