[http://sourceforge.net/p/ufoai/bugs/2206 Item 2206] imported from sourceforge.net tracker on 2013-01-28 19:26:38

for some time now there's a regression - it is not possible to exit in a normal way from a map loaded with 'map' command (neither esc, nor in-battlescape options menu work). as a workaround console command game_abort was attempted to use, which resulted in a crash :

game_abort
[STATS] 2009/11/03 03:34:26 - End of game - Team 7 is the winner
[STATS] 2009/11/03 03:34:26 - End of game - Team 7 is the winner
[Thread 0xa76a1b90 (LWP 6007) exited]
GAME_TeamIsKnown: Could not determine gamemode
Shutdown server: Server fatal crashed
==== ShutdownGame ====
Wrote keys.cfg
[Thread 0xb4b57b90 (LWP 5932) exited]
/space/games/ufoai/svn/trunk/ufo(Sys_Backtrace+0x1a)[0x8185dd8]
/space/games/ufoai/svn/trunk/ufo(Sys_Error+0xe)[0x8185144]
/space/games/ufoai/svn/trunk/ufo(Com_Drop+0x0)[0x8136a4a]
/space/games/ufoai/svn/trunk/ufo(GAME_TeamIsKnown+0x5b)[0x8067c77]
/space/games/ufoai/svn/trunk/ufo(CL_ActorAppear+0x4aa)[0x80954ae]
/space/games/ufoai/svn/trunk/ufo[0x809417b]
/space/games/ufoai/svn/trunk/ufo(Qcommon_Frame+0x82)[0x8138580]
/space/games/ufoai/svn/trunk/ufo(main+0x4f)[0x8184dc3]
/lib/libc.so.6(__libc_start_main+0xe5)[0xb7a266a5]
/space/games/ufoai/svn/trunk/ufo[0x8065e61]
Error: Shutdown

Program exited with code 01.

===== Comments Ported from Sourceforge =====

====== tlh2000 (2009-11-03 06:02:48) ======

yes - because the map command won't set any gametype - this won't be fixed.

The thing the no key is working when you start a map with the "map" command is indeed a bug and should be fixed
====== richlv (2009-11-03 11:42:28) ======

i'd disagree. it should not ever crash - if the command should not be working, it should output a sensible error message and just sit there.
(i'd say that this command or some other still should be a usable to quite the battlescape mode, but that's a less severe problem)
====== tlh2000 (2009-11-05 17:59:03) ======

and i disagree here again - a sys_error is a fatal error and it should exit the game - it's a controlled shutdown. so i see no problem here.
====== richlv (2009-11-05 18:07:34) ======

that's... a coder viewpoint :)
no, really, why should it exit ?
it should output a message (ideally it would also exit battlescape, but it could also just instruct to use some other command).
it is mighty annoying if software exits if, like in this case, there's a valid and sane path to continue, especially if the said software does not start up instantly. and ufoai for me starts up a quite long time.

it's actually similar to the usability regression with the map command - a thing that was extremely helpful in map, pathfinding etc testing was destroyed in the name of some technical superiority. but the thing is, it really makes many things very inconvenient, and user oriented approach would be to think about a solution to the created problem before breaking things... and these cases impact development as well, as now it is so extremely inconvenient to test many things. of course, this means that game gets less testing and/or fixes to the maps etc.
====== tlh2000 (2009-11-05 18:10:54) ======

a fatal error should always exit the application you are running - we can discuss whether this particular error is a fatal error. but a Sys_Error or ERR_FATAL will always exit the application.
====== richlv (2009-11-05 18:14:28) ======

hmm. that could be "lost in translation" between dev speak and user speak then ;)
i do not quite care how it's called, my goal is to have it not crash (because from the user perspective this is basically the same as crash) ever, and in this reproducible case there surely is no need for a crash (again, from user perspective there's no difference, this is even a bit worse as there's no backtrace :) )
====== tlh2000 (2009-11-29 06:40:41) ======

this should be fixed with the reworked map command support
====== sf-robot (2009-12-14 02:20:14) ======

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).