Ledybot
Ledybot copied to clipboard
bot is crashing if it takes some time to trade a new pokemon
I'm having a strange issue with the bot while I'm connect if ledysync, if the bot don't stop to trade it doesn't crash but if it stops for like 30 minutes because it couldn't find a pokemon to trade when it finds again a pokemon to trade it crashes I don't think it's a problem if my configurations because my port is open and my firewall isn't blocking it
u dont need to open the Ports, ure using it only Local.
a log from the crash will help us more to identify the Problem.
I'm not using local that is why I needed to open a port edit:ops my bad for the bold text
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
Exception Text
System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host em System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) em System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
Loaded Assemblies
mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.7.2558.0 built by: NET471REL1 CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
Ledybot Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Users/Shiro/Downloads/Release%20(1)/Ledybot.exe
System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.7.2558.0 built by: NET471REL1 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.7.2558.0 built by: NET471REL1 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.7.2558.0 built by: NET471REL1 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.7.2558.0 built by: NET471REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.7.2558.0 built by: NET471REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
Accessibility Assembly Version: 4.0.0.0 Win32 Version: 4.7.2558.0 built by: NET471REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
System.Data Assembly Version: 4.0.0.0 Win32 Version: 4.7.2558.0 built by: NET471REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
System.Windows.Forms.resources Assembly Version: 4.0.0.0 Win32 Version: 4.7.2558.0 built by: NET471REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_pt-BR_b77a5c561934e089/System.Windows.Forms.resources.dll
System.Numerics Assembly Version: 4.0.0.0 Win32 Version: 4.7.2558.0 built by: NET471REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.7.2558.0 built by: NET471REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
mscorlib.resources Assembly Version: 4.0.0.0 Win32 Version: 4.7.2558.0 built by: NET471REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_pt-BR_b77a5c561934e089/mscorlib.resources.dll
System.resources Assembly Version: 4.0.0.0 Win32 Version: 4.7.2558.0 built by: NET471REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.resources/v4.0_4.0.0.0_pt-BR_b77a5c561934e089/System.resources.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:
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
I see no point why ure using it foreign, its designed to be local.
It just closed the connection from the remote host.
Its not a Issue from Ledybot/Ledysync.
since I don't have 2 3ds I was asking for help for a friend that is why I wasn't doing local, thanks for the help
Who is hosting the ledy sync? They need a public and static IP address and you’ll both probably need port forwarding set up in your routers