this is the screen, when I start Pokefarmer first: https://snag.gy/xCP3VE.jpg ; the same failure comes, when I only start the tool but without opening Pokefarmer GUI
works, but produces after reaching the limit (pokestops) again the popo-ups:https://snag.gy/2BMvt0.jpg but Pokefarmer was running till end of time and closes then. Then this Microsoft Net Framework failure comes: nformationen über das Aufrufen von JIT-Debuggen anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung. ************** Ausnahmetext ************** System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt. bei PokefarmerTimer.Form1.timer1_Tick(Object sender, EventArgs e) bei System.Windows.Forms.Timer.OnTick(EventArgs e) bei System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m) bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Geladene Assemblys ************** mscorlib Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1076.0 built by: NETFXREL3STAGE. CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll. ---------------------------------------- PokefarmerTimer Assembly-Version: 1.0.0.0. Win32-Version: 1.0.0.0. CodeBase: file:///C:/Users/Home/Downloads/PokeFarmer%201.0.106/PokefarmerTimer.exe. ---------------------------------------- System.Windows.Forms Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1055.0 built by: NETFXREL2. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll. ---------------------------------------- System Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1075.0 built by: NETFXREL3STAGE. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll. ---------------------------------------- System.Drawing Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1068.2 built by: NETFXREL3STAGE. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll. ---------------------------------------- System.Configuration Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1055.0 built by: NETFXREL2. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll. ---------------------------------------- System.Core Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1055.0 built by: NETFXREL2. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll. ---------------------------------------- System.Xml Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1067.0 built by: NETFXREL3STAGE. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll. ---------------------------------------- mscorlib.resources Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1055.0 built by: NETFXREL2. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll. ---------------------------------------- System.Windows.Forms.resources Assembly-Version: 4.0.0.0. Win32-Version: 4.6.1055.0 built by: NETFXREL2. CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll. ---------------------------------------- ************** JIT-Debuggen ************** Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der Konfigurationsdatei der Anwendung oder des Computers (machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden. Die Anwendung muss mit aktiviertem Debuggen kompiliert werden. Zum Beispiel: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten Ausnahmen an den JIT-Debugger gesendet, der auf dem Computer registriert ist, und nicht in diesem Dialogfeld behandelt.
What I don't understand are the looted pokestops & pokemons. they are starting not at zero. Looks the tool with the api how many pokestops looted today in summary (also without the tool?)
Now it's working nearls 100% ;-) Maximum limits working (pokestops/pokemons) => Pokefarmer shutting down. But the time limit doesn't work. The clock runs through the limit and is counting "up" and the "time to run" is running positive not counting down
great, running the bot at the moment... Time stop works ) Thank you man. Now professional botting can start!!
There are some problems with the session and it often turns back to the standard settings, which makes me angry Next thing, that then then active session has to be "killed" online. Also when I start Pokefarmer Timer the bot is not starting automatically and I have to push the button. However the big problem is now only the settings thing... Every time by a new start I'm getting the notices like starting a new fresh download/build of pokefarmer with all the infos in the GUI.
I shut the bot down with .CloseWindow() this means its does everything it normally would when its shutdown
by the way spotted another simple idea for looping in another forum with a simple bat file: Maybe you can implement the feature, if time limit is reached the first, make a break of X min and then go further to reach the limit with pokestops or pokemons. So the user can start the timer in the morning and come back in the evening with maximum efficiency