ZeroK-RTS / Zero-K-Infrastructure

Website, lobby launcher and server, steam deployment, .NET based tools and other vital parts of Zero-K infrastructure
GNU General Public License v3.0
53 stars 52 forks source link

Singleplayer in lobby can be run only once #893

Closed ioma8 closed 8 years ago

ioma8 commented 8 years ago

Situation: I run singleplayer game (chicken), finish the game and then another singleplayer games can't be played. Clicking on the "Play" button does nothing except playing the "click" sound. The only solution is to restart the lobby. So if I want to play 10 chicken single games in a row, I have to restart lobby 10 times.

This isssue had been there for me on two different computers over the last 1.5 years. Both Windows 7, but different HW configuration.

Licho1 commented 8 years ago

Hmm you heard click sound? What lobby program were you using Zero-K lobby?

ioma8 commented 8 years ago

Yes, traditional Zero-K lobby, using the button "PLAY NOW" in attached screen or in detail of the singleplayer game. I hear the click sound when I click, but no game starts, nothings happens. Works just the first time the lobby is run, than it has to be restarted to work again. image

knorker commented 8 years ago

in taskmanager, do you maybe still see the process of the previous game?

knorker commented 8 years ago

http://code.google.com/p/zero-k/issues/detail?id=1946 is the same bug reported in Aug 21, 2013

One message by msafwan had some details:

https://code.google.com/p/zero-k/source/detail?r=11690 : workaround this issue for ZKL using internal browser.

Usually it work like this: 1) user execute javascript (site_main.js, this file: https://code.google.com/p/zero-k/source/browse/trunk/other/Zero-K.info/Scripts/site_main.js ) 2) then server send a message: SAIDPRIVATE Nightwatch !JSON SiteToLobbyCommand {"SpringLink":"@start_mission:Tutorial - Running Start r205"} 3) ZKL will do stuff to start mission.

The problem is, the server never send 2nd message if you click the PLAY NOW 2nd time.

The workaround is: internal browser read the URL for the javascript before its executed and run independently. This won't fix for user attempting mission/replay using external browser.