THREAD error: attempt to call global 'incrementID' (a nil value)

[tarmo888]

Tried to run the Windows executable, but it hanged. Then installed LÖVE and downloaded trAInsported4.love, but this didn't do anything. Finally tried to run a server and got this error on the console. Running on Windows 8.1 Pro (Intel Core Duo 32bit x86)

[tarmo888]

On another Windows 8.1 Pro (Intel Core2 Duo 64bit x64) computer, the game starts fine, but the dedicated server still throws similar error, so maybe it's not an issue with trAInsported, but instead LÖVE issue:

Using port 5556.
Rounds will take 300 seconds.
Will start a new match after waiting for 10 seconds.
No database name given. Using default database: 'trAInsported' (Change with --mysqlDB).
Starting in dedicated Server mode!
Initialising Server
Loading language file: Languages/English.lua
Starting next match in -0.03 seconds.

Starting next match in 0.00 seconds.
Finding AIs
Searching:  C:/games/trAInsported4/AI/
dir returned:   TutorialAI1.lua
CHOSE AI:   C:/games/trAInsported4/AI/TutorialAI1.lua
Generating new map. Width: 8 Height: 7
found AIs:  1
scriptName  C:/games/trAInsported4/AI/TutorialAI1.lua
NAME:   TutorialAI1
OWNER:  AI
    Compiling code...
        Success! Code lines: 2 of 50000
    Running code:
        Success! Code lines: 8 of 50000
    AI loaded.
OWNER:  1   TutorialAI1 AI
Started server at: 5556 
THREAD error: [string "thisThread = love.thread.getThread()..."]:38: attempt to call global 'incrementID' (a nil value)
Generating done!
Finished Map:
- H - H - H H - - - 
H C H C H C C HOUSE_4_LARGE11 HOUSE_4_LARGE21 - 
H C C C C C C C C H 
- H C C H C H C C - 
- HOUSE_1_LARGE11 C H C C H C H - 
- HOUSE_1_LARGE12 C H C H C C C H 
- HOUSE_1_LARGE11 C C C HOUSE_3_LARGE11 HOUSE_3_LARGE21 C H - 
- HOUSE_1_LARGE12 C H C C C C C H 
- - H - - H H H - - 
Initialising AI:    ID: 1   Name:   TutorialAI1 C:/games/trAInsported4/AI/TutorialAI1.lua
Closing.

[Germanunkol]

Thanks, I will look into this in a while, I'm pretty busy for another 10 days or so.
I'm suspecting it has to do with the version of Löve and trAInsported, the github version should run on Löve 0.9, but the decitated server has not been fully ported.
An ugly workaround would be: Download trAInsported's version 4 (the .exe) and use that as a dedicated server, then run the github version using Löve 0.9 - that should work since the protocoll hasn't actually changed.

[tarmo888]

Good news, I messed around with WinDbg and figured out that the problem with game hanging on start-up was related to OpenGL Intel Graphics Driver (ig4dev32.dll). I re-installed it, even when the installer said that my current version is newer and it started to work.

This "THREAD error" is still on both (version 4 and the GitHub version) when trying to run the dedicated server. I am not sure if I even once were able to run the dedicated server successfully, but I am not so worried about that now after getting the game working on my laptop. Take your time.

[Germanunkol]

I was never able to reproduce this. Does it still happen with newer versions of the game (5.2 and Löve 0.9.1?)

[tarmo888]

I don't get that THREAD error anymore with the new version, so I guess this issue can be closed now.

But then again, maybe I don't get that error because I am unable to run a dedicated server now. I get this error, which I didn't get with previous version (see previous console output):

Started server at: 5556 
Server thread error:    Scripts/connectionThreadServer.lua:61: Failed to set up server. Maybe a connection is already running on this port?
Scripts/connectionThreadServer.lua:58: attempt to call field 'init' (a nil value)
Closing.

Also tried different ports, but same result. Tried executable and also latest git. Maybe it's Windows 10 thing now, I am not on 8.1 anymore.

[Germanunkol]

Ah, I've never tried running a server on windows.
It might be that Luasocket isn't found (might need to install it or place it in the same directory), I don't have experience with that on win. I might try it out one of these days, when I get back to a windows machine.

Thanks for testing again!

Edit: No scratch that. Luasocket must have been found if the client works...