BigSister - A Gatherbuddy / Honorbuddy Restarter and Relogger - Beta Phase

Soon

I even made an extra Thread about your ideas for window placement, check it out in the GB forum.

 

its a pity, that we cant get a short small update which let you decide to use "tripwire force shutdown" option or not...
since it?s the only point, which let the tool not run 24/7...

 

Its already implemented in my current dev version.

But I started work on the window positioning system (read improved), so i have to give it some extra hours to see if everything is properly working (many settings that need GUI/LOAD/SAVE/OVERRIDE checks).

You will probably have an update today tho

 

Can't wait! Also, do you still plan on incorporating "- Bot schedules, allowing you to place your characters on "cooldown", for example, bot from 2am to 6am.
- Schedule swapping, basically you can tell it to swap character X with character Y from (example) 6am to 12am." ? I am very interested in that, but more or less I would like you to hurry up and put in "- Workout for you, so you can lose weight while you bot. Wouldnt it be great if there was a program to workout for you the same way HB/GB levels/farms for you?". That sounds very nice!

 

Well my time is far from abundant at the moment. Been very busy. Probably next week even more :/

 

New version is out.

 

Great app, the window placement just isn't working for me though. No matter where I try to place them or how I try to size them it places them on my 1st monitor dead center and minimized then to about 1x75px. Also this thing uses almost 1/2 the amount of memory each one of my wow sessions use. I had to drop one instance of wow just to play with this app for a bit. Good start though, It's better than anything else out there right now.

 

does this program work yet ? with 0 bugs ?

 

for me it arrange all wow windows in the middle of the screenbehind each other not in a row, but in the correct size

:/

 

Did you configure the window placement properly?

 

As with all software, it will never work 100% for everyone, everytime.

I am doing what I can to improve it. But if you have errors and bugs and dont report them properly, dont expect them to get fixed by themselves.

 

Did you configure the window placement? There are new settings for them.

 

yes, but it put all windows just in the middle of the screen :/

 

Yup, thx for reporting, I found the problem, I put "Height" instead of "height" and "Width" instead of "width", so, I wasnt actually using my own variables but BigSisters main form properties... it was using an hidden this.Width and this.Height.

Kinda hard to spot, but I am updating it, will post new version up soon.

 

ok, n1 wait for it, then i go to sleep

 

New version is up.

 

The memory problem should had been fixed few versions ago. How much CPU/memory is BigSister using?

With 0 Monitorizations ?
With 1 Monitorizations ?
With 2 Monitorizations ?
With n Monitorizations ? (how much is it scaling?)

I am sorry, but I only have 1 account to test Bigsister on atm, and its using 1% of CPU and droping to 0% on sleeps.


Did you try "Light Mode" ? Does it change the amount of cpu/memory it uses?

 

hm..
i have 5 HB's and 2 GB's in the list...
everytime i push babysit all it start in a new range so
1 3 2 4 6 5 7
next time in another range so thats not the problem
but everytime after the 3rd wow start Bigsister crash... i never get it to start more then 2 bots... bot 1 and bot 2 start correct but after it bigsister crash
just got timeout.. so no direct crash... just hang up.... and get "no response" and cant klick anything more

 

when i try to start by hand
1st HB1 then HB2 it start correct to, but after i push start HB3 it crash again
i allready try to start 1st HB5 2nd HB6 3rd GB1 ... after load the 3rd bot it crash... ore "no response"

 

Try out the version i just uploaded, the other one had a mistake in it.

Also, can you read the Logs? In the logs folder for the 3rd bot only, see if it says anything wierd. (what you are saying sounds like the "Cross thread" error, fixed that already)