Grepolis bot (Now with attack option)

thx. good job ^^

Quote:

Originally Posted by Utharnl @Beastygirl Do you get that error everytime? Because I have the bot running atm and haven't any problems. And do you know when you got the error? As soon when you started the bot or when it was running for some time? ~Uthar

@:Utharnl

13.03.2010 08:28:09 Exception in setArmyReqSize(): Der Index lag außerhalb des Bereichs. Er muss nicht negativ und kleiner als die Auflistung sein.
Parametername: index

The Bot do correctly log in but when it says "counting army" the above error occures. Then the Bot stops and I have to close it.
This error comes everytime when i start the Bot.


Hope this will help you. thx.

the builduing queque doesn´t work on world hyperborea

@Beastygirl
That error should only happen when you go to View->Army before you have logged in.
Could you try it again? I'm sure it works fine if you login first.

@SlayerABC
Could you send me your debug.txt file. It should contain information why your building queue isn't working

~Uthar

12.03.2010 23:42:08 Exception in setMaxArmy(): Der Index lag außerhalb des Bereichs. Er muss nicht negativ und kleiner als die Auflistung sein.
Parametername: index
12.03.2010 23:42:11 Exception in setMaxArmy(): Der Index lag außerhalb des Bereichs. Er muss nicht negativ und kleiner als die Auflistung sein.
Parametername: index
12.03.2010 23:42:12 Exception in setArmyReqSize(): Der Index lag außerhalb des Bereichs. Er muss nicht negativ und kleiner als die Auflistung sein.
Parametername: index
12.03.2010 23:49:18 Checking attack timer event. Attack/Build timer status: True/True
12.03.2010 23:49:21 Building queue check done. Starting timer.
12.03.2010 23:55:21 Checking attack timer event. Attack/Build timer status: True/True
12.03.2010 23:55:23 Building queue check done. Starting timer.
13.03.2010 00:01:23 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 00:01:25 Building queue check done. Starting timer.
13.03.2010 00:07:25 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 00:07:27 Building queue check done. Starting timer.
13.03.2010 00:13:27 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 00:13:29 Building queue check done. Starting timer.
13.03.2010 00:19:29 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 00:19:33 Building queue check done. Starting timer.
13.03.2010 00:25:33 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 00:25:35 Building queue check done. Starting timer.
13.03.2010 00:31:35 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 00:31:37 Building queue check done. Starting timer.
13.03.2010 00:37:37 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 00:37:39 Building queue check done. Starting timer.
13.03.2010 00:43:39 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 00:43:42 Building queue check done. Starting timer.
13.03.2010 00:49:42 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 00:49:44 Building queue check done. Starting timer.
13.03.2010 00:55:44 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 00:55:46 Building queue check done. Starting timer.
13.03.2010 01:01:46 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 01:01:48 Building queue check done. Starting timer.
13.03.2010 01:07:48 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 01:07:51 Building queue check done. Starting timer.
13.03.2010 01:13:51 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 01:13:54 Building queue check done. Starting timer.
13.03.2010 01:19:54 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 01:19:56 Building queue check done. Starting timer.
13.03.2010 01:25:56 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 01:25:58 Building queue check done. Starting timer.
13.03.2010 01:31:58 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 01:32:00 Building queue check done. Starting timer.
13.03.2010 01:38:00 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 01:38:02 Building queue check done. Starting timer.
13.03.2010 01:44:02 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 01:44:05 Building queue check done. Starting timer.
13.03.2010 01:50:05 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 01:50:07 Building queue check done. Starting timer.
13.03.2010 01:56:07 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 01:56:09 Building queue check done. Starting timer.
13.03.2010 02:02:09 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 02:02:11 Building queue check done. Starting timer.
13.03.2010 02:08:11 Checking attack timer event. Attack/Build timer status: True/True
13.03.2010 02:08:13 Building queue check done. Starting timer.

It's starting the timer too soon (When it's still running)
"Building queue check done. Starting timer."

No idea if the timer restarts then when I do that, but it's not correct what it does now.
Your log file should contain "Checking Building timer event" when it's working.
Will upload a new version in a few minutes.

ps. Could you attach debug.txt the next time instead of copy/paste the whole file as text ^^

~Uthar

can you make a timer when the buildings are ready?
and can you instert army units too build?

Fixed your problem Slayer. The timer was restarted before it was finished.
Version 1.6.5 uploaded:
-Fixed issue with building queue timer

Think I will add a timer for the first building in the queue. But will first have to test a few things.
A queue for army units will probably follow later, but first want to be sure that all current features are working fine.

~Uthar

Quote:

Originally Posted by Utharnl @Beastygirl That error should only happen when you go to View->Army before you have logged in. Could you try it again? I'm sure it works fine if you login first. ~Uthar

with this procedure its now working :)

thx for your awesome Bot, keep up the good work.


ps.: Maybe its possible to show the time when the Bot will do the next attack/building ( like a counter in seconds maybe ).

getting a .net framework error, unhandled exception and frezzes the bot at counting troops.

Quote:

[Only registered and activated users can see links. Click Here To Register...]

figured out how to upload the debug.txt instead of a mediafire link.

@Psidawg
Could you try installing .NET framework 3.5 and try again?

[Only registered and activated users can see links. Click Here To Register...]

3.5 is not supported on windows 7

Quote:

Originally Posted by Psidawg 3.5 is not supported on windows 7

OT :
Thats why I dont like Net Framework :D

I have installed Microsoft SDK 7 with .NET 3.5 sp1. The SDK installed fine but it still shows me as having .NET 1.1, bot so far the bot has not had an error. Here is the details of the last error it had:

Quote:

See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Net.WebException: The request was aborted: The connection was closed unexpectedly. at System.Net.ConnectStream.EndReadWithoutValidation( Int32 bytesTransferred, Boolean zeroLengthRead) at System.Net.ConnectStream.EndRead(IAsyncResult asyncResult) at System.Net.WebClient.DownloadBitsReadCallbackState (DownloadBitsState state, IAsyncResult result) ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll ---------------------------------------- GrepolisBot Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Users/Psidawg/Downloads/GrepolisBot_v1.6.5/GrepolisBot.exe ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.