Enable Console on OS X. not achieved yet

Talk about creating Grimrock 1 levels and mods here. Warning: forum contains spoilers!
Post Reply
User avatar
sparky
Posts: 2
Joined: Wed Feb 20, 2013 9:29 am

Enable Console on OS X. not achieved yet

Post by sparky »

Hello Almost Human, hello community.

First of all, thanks for the great game, which takes me back (as many others)
to the wonderful dungeon crawling and puzzle solving experiences.

Secondly I try to fire up the console in the dungeon editor:
I modified './Library/Application\ Support/Almost\ Human/Legend\ of\ Grimrock/grimrock.cfg':
set console=true and consolekey=220 for the tilde
then fire up dungeneditor, load a smal testdungen and press the play button. so far so good.
the I press <alt>-n : nothing...

tried different consolekey values ('§'-244, 'h'-104, 'l'-108) based on ascii-table, but failed also.

I think I'm missing something...
User avatar
petri
Posts: 1917
Joined: Thu Mar 01, 2012 4:58 pm
Location: Finland

Re: Enable Console on OS X. not achieved yet

Post by petri »

The key values are not ascii. You could try to bind, for example, move forward to a key in the Options dialog, and look up its code in the config file and copy the value to consoleKey.

Hope this helps!
User avatar
Numberouane
Posts: 283
Joined: Fri Mar 02, 2012 6:11 pm
Location: Sunny Place south Of France

Re: Enable Console on OS X. not achieved yet

Post by Numberouane »

Some info here even if not OS X. based for enabling the console...

viewtopic.php?f=14&t=1982
User avatar
sparky
Posts: 2
Joined: Wed Feb 20, 2013 9:29 am

Re: Enable Console on OS X. not achieved yet

Post by sparky »

Thanx Numberouane, I had that thread already spotted :-)

@ Petri, good idea to get the keycodes.
After some testing I experienced following:

assigning keys to the editor are working, no matter what optional key was used:

Code: Select all

<opt>-n     16462    0x404e   ~   (stop preview)    ok
<shift>-n    4174    0x104e   N   (kill monster)    ok
<ctrl>-n     8270    0x204e       (heal party)      ok
<cmd>-n     32846    0x804e       (open door)       ok
n              78    0x004e       (start preview)   ok
But using those decimal values for the "consoleKey" worked only for the plain 'n'

Code: Select all

<opt>-n        16462    fail
<shift>-n       4174    fail
<ctrl>-n        8270    fail
<cmd>-n        32846    fail
n                 78    ok (even double assignment)
It seems to me, that the function(?) checking for the console key
only honors the lower byte and ignores the higher byte which holds the key modifier flags.
At least for OS X.

For now I will determine a plain key which is not needed for console input :-)

BTW: I use the latest version of LOG: 1.3.7

Edit: typo
Post Reply