TomeNET Forums

SOMETIMES... my keys stop working. I have to push the same key _several_ times (in most cases twice) to make it work. It 'beeps' 1st time and do not do nothing, and then after I push second (or third & etc) time - it works. You could see this in my streams; even in my today's stream I had it, while I was in house:
https://www.youtube.com/watch?v=aktJkN6tz7Y&t=2498s

It's how I died with my mage last time - pushed teleport scrolls macro but it just #$%^&ing BEEPS to me :E~~
https://www.youtube.com/watch?v=07kMhEn-ohM&t=2315s
http://angband.oook.cz/ladder-show.php?id=20814



@ tavern

Thanks for the report. There seems to be no indication in the code of such a bug (and it is not currently known or has been reported).
Beeping on key input in general means that either a wrong key (unavailable choice) is pressed or -usually- that an 'ingredient' (item) for a key is not available (the latter one could result from missing inscriptions too).
If anyone knows additional details or anyone else can confirm a particularly beep-related key input problem, please answer in this thread.

Thanks!

In 'house' https://www.youtube.com/watch?v=aktJkN6tz7Y&t=2498s
I had macro for pick up:

# Macro '19'

A:g
H:^_x52\r

For my death @ istar https://www.youtube.com/watch?v=07kMhEn-ohM&t=2315s
Macro for teleport:

# Macro '89'

A:\e)r@Teleportation\r
C:-

Num lock turned off (and blocked).
---

Beeping on key input in general means that either a wrong key (unavailable choice) is pressed

it's not my case cause it works after second try

that an 'ingredient' (item) for a key is not available (the latter one could result from missing inscriptions too).

I had plenty of scrolls - http://angband.oook.cz/ladder-show.php?id=20814
p) 21 Scrolls "bucon reafid" of Teleportation {+,1} {@S3k}

I've tried to reproduce it but for now didn't get it. Maybe you have to do some special actions before it, donno.

No news yet? I had to stop playing until this bug would be solved.. Not fun to die cause of a bug. Actually it's the first time in TomeNET when I died not because of my mistake, but because of external cause. Sad D:

Awww... I miss TomeNET. Hope it would be fixed one day

Tangar,maybe , its all because ahk (autohotkey) macro is conflicting with TomeNET macro?
just make sure you are dont using any keyboard interception Programs.
By the way , i dont have any issue with TomeNET macro

Nope, it's not the issue, cause I played 1+ year with my ahk addon and didn't had any problem like this. This issue (as some others) appeared after recent updates.

Raised an RFE for you.

Basically, I suggested that whenever a keyboard beep is done, a failure message is sent to your game messages window first.

eg.

"Unable to read item c"
*Beep*

or

"Unable to aim item j"
*Beep*

"Unable to quaff item @q1"

etc.

Note that your macro is vulnerable if a trap makes you lose memories - because you won't remember what your teleportation scroll looks like "@Teleportation". It is safer to inscribe your scroll so you don't forget what it looks like. eg. scroll of teleportation {@Flee} and have a macro that uses @Flee.