Autoprofessionbot V1.3.0 - Browserbot fürs Gateway

[b][color=red]
1. In case of errors 
2. Starting the Bot
3. Using the assets you would like to
4. Disabling the annoying accountguard
[/color][/b]


[b]1. In case of errors [/b]

1. Paste your config here (remember to remove char@acc)
2. Paste your log
3. Add anything else you think thats helpful

[b]2. Starting the Bot[/b]

When you entered all your information, loaded the settings, you can start the bot. After you hit "Start", the bot will wait until it recognizes the profession menu. So you either go to the professionmenu in the bot before or after you hit start (doesnt matter), then it should start automaticly

[b]3. Using the assets you would like to[/b]

The bot will detect the number of required and the number of optional slots for each profession you want to start. It will then read in the assets you wrote in the textbox (Has to be:  "asset:asset:asset"). It will then take those assets for the optional slots.

[b]4. Disabling the annoying accountguard[/b]
<<<@!1!@>>>

[b]V1.3.1[/b]

Major changes:
-Reduced the memory usage over all, still a problem though
-Reduced the cpu taken by the bot a lot 
 The new method will now let the whole program "sleep" for a while
 Pro: Very low cpu usage Con: The Interface will now sometimes seem to be a bit laggy while the bot runs 
 (I might work on that, but it runs very smoothly this way)

Minor changes:
-Fixed a crash that would occur if there were more optional slots than given assets
-Removed some things that were logged. There won´t be logspam anymore
-Added Leatherworking_Tier1_Leather_Shirt_1
-Added a simple check, so you do not forget to enter charname@account at the beginning

[b]V1.3.0[/b]

Major changes:
- Added Delays to everything. The bot will do everything a bit slower now, however
  this should give the gateway more time to react and reduce errors/bugs in general
  Furthermore now it will be easier for you to see what the bot does and therefore easier to
  recognize why something fails
- The normal log will now inform you about any step, very detailed. It should be easy for you to see
  what the bot does and therefore, if something fails, it should be very easy to find out why
- The bot will no longer select required workers. They get autofilled by the gateway, I see no reason
  to not use this feature. The assetslot of the bot will now be used for optional slots only
- The cpu/memory usage should be much better now - please report your experience with those

Minor changes:
- You can now edit the tasks/assets/jobs while the bot is running
- You can now only activate slots that follow after an activated slot (If you want to activate slot5, slot 1-4 
  have to be activated). Its not possible to start a job at a chosen slot (not possible in the gateway), 
  the job will start on the next open slot. Therefore if you only want to run slot 1 and 3 the bot will bug.

Removed stuff:
- Removed Shortcut for Workmode (was useless imo)
- Removed detailed log and error log

[b]V1.2.3[/b]

- Removed the anti-afk function for testing. Please report your experience:
  Do you disconnect?
  How is the memory leak now?
- The process should now correctly end it self when you click the "X" or hit the "End" button:
Please report your experience with that. Let me know if you still have processes of the bot running after you closed it

[b]V1.2.2[/b]

- Fixed the "bot is running since" - display: it should no longer show negative numbers
- Changed "Safe settings" to "Save settings"
- Added buttons to activate/deactivate the autoscrollfunction of the logs
- You should now be able to change professiondetails if the bot is interrupted
- The process should not run anymore if you press "End" (there were some reports that the task still runs)
- Time for "Anti-afk"-function has been increased by 400%
- Bot will now clear the slots at a new job, before selecting the assets:
This could fix the error that the bot sometimes cant find an asset - please report your experiences with that

[b]V1.2.1[/b]

- Trying to fix the bug that slot doesnt get restarted after reward was taken:
I have a function to remember already used slots to make sure they arent double found when selection goes fast
However if this is the reason of the bug, it should give you the error "The found asset should already be in use" in the detailed log
- Slots that couldnt get started will not be turned off anymore. Bot will try to start them again:
However, this can result in an endlessloop, please report if you get endlessloops with that
- Added shortcut Strg+W for workmode
- Changed the color of the main buttons
- Added some statistics in the "Information" tab like, total rewards taken, rewards per slot and time since program started
- Addes Ctrl+a function for all logs

[b]V1.2[/b]

- Detailed log added
- Changed the logincheck to check for professionsite, it will no longer search your char@acc in the html code. This should fix the error that the bot  sometimes doesnt start at all if it couldnt find your char@acc because of case-sensitive
- added "On Work"-Button (if klick, title changes, icon changes, program goes to tray instead of taskbar)
- Added a fix to the stuck after taking reward - the bot should no longer endlessloop if taking a task reward takes long
- Interrupt button added

[b]V1.1.2[/b]

- Fixed a little doublecheck for the characterdetection, bot should no longer end itself if you start it outside of the charactermenu

[b]V1.1[/b]

- Fixed a bug which would make the bot fail to start a slot if it didnt had optional slots