Author Topic: Blockland locks up when starting an Internet Server  (Read 802 times)

Well this is very strange. Sometimes when I start a internet server it loads right up with no problems at all. Now however, I can barely start an internet game. Blockland will quit responding and the console will list a bunch of UPnP desc:'s. Here is the console log.

The only thing that sticks out to me is UPnP initialization.

Code: [Select]
      Initializing UPnP...
      --------------------
      List of UPNP devices found on the network :

       desc: http://10.11.2.23:2869/upnphost/udhisapi.dll?content=uuid:1e074e3d-fd58-46dd-8002-855e8f751bfa
 st: upnp:rootdevice


       desc: http://10.11.2.174:2869/upnphost/udhisapi.dll?content=uuid:ba82cd10-d267-4c13-9380-8620e1a9ead4
 st: upnp:rootdevice


       desc: http://10.11.2.135:2869/upnphost/udhisapi.dll?content=uuid:e5c290c1-c503-4e8d-8a11-284561211791
 st: upnp:rootdevice


       desc: http://10.11.2.141:2869/upnphost/udhisapi.dll?content=uuid:e915a865-9773-440b-abda-289024bb7e45
 st: upnp:rootdevice


       desc: http://10.11.2.135:50688/
 st: upnp:rootdevice


       desc: http://10.11.2.135:50688/
 st: upnp:rootdevice


       desc: http://10.11.2.135:50688/
 st: upnp:rootdevice

When I boot, the console only prints one. What's even more disturbing is that it lists the same device three times at the end. When the program quits, does it stop responding and then pop open the "Blockland.exe is not responding", or does the dialog appear very quickly?

My personal suggestion would be to set up a proper router or, at the very least, try changing ports. I think you're on a college campus so it's very probable the network routing configuration is causing an infinite loop or is just outright incompatible with whatever Blockland is using for its UPnP.

Blockland will just remain inactive until I click within the window and only then does it grey out and quit responding. If it's incompatible then why does it work once every twenty tries? Perhaps some sort of fluke I guess, either way I have no access to the router so maybe I'm s.o.l

Blockland will just remain inactive until I click within the window and only then does it grey out and quit responding. If it's incompatible then why does it work once every twenty tries? Perhaps some sort of fluke I guess, either way I have no access to the router so maybe I'm s.o.l
Yeah, if it takes a long time to respond that means the program is stuck in an infinite loop. That's why it's printing out the last entry a few times in the console.log -- it cannot resolve that UPnP device for whatever reason and is testing it hundreds of times over, until (by clicking on it) Windows discovers it's not working.

Unless Badspot can psychically resolve the problem (perhaps by getting the engine to catalogue which devices it's discovered and skipping paths it's already taken?), you likely will not be able to host while on campus.