I'm sorry if this has come up before or if this is not the right place to mention it but I think I've found a bug related to removing macros. This is in 3.0.9b.
Short Story:
When you remove a macro it just creates a new macro of the key bound to that key. This causes problems when you remove a macro from 'p' and/or 'g' and visit your home/a shop.
Long Story:
So I was looking for a key to bind my auto-shoot macro to and chose 'g'. This was going swimingly until I surfaced and realised I couldn't sell things from slot g in my bag anymore. So I just removed the macro from 'g' and re-created it on 'G'. So far so good. Much later I returned to my home where I had 2 scrolls of identify, I tried to pick them up 'g' -> Quantity (0-2, *=all): -> 2 -> Quantity (0-0, *=all): .... Argh I'm stuck! No input would work, my inventory has the 2 scrolls but so does my house ... Only way out of this situation was to kill the process. After much head scratching trying to figure out what was causing this I discovered in my .prf file that there is a macro bound to 'g' of 'g', and this causes this bad behaviour. To fix it I just removed the macro from my prf file (which is what I assumed the remove macro function would do).
Yay for long stories
Short Story:
When you remove a macro it just creates a new macro of the key bound to that key. This causes problems when you remove a macro from 'p' and/or 'g' and visit your home/a shop.
Long Story:
So I was looking for a key to bind my auto-shoot macro to and chose 'g'. This was going swimingly until I surfaced and realised I couldn't sell things from slot g in my bag anymore. So I just removed the macro from 'g' and re-created it on 'G'. So far so good. Much later I returned to my home where I had 2 scrolls of identify, I tried to pick them up 'g' -> Quantity (0-2, *=all): -> 2 -> Quantity (0-0, *=all): .... Argh I'm stuck! No input would work, my inventory has the 2 scrolls but so does my house ... Only way out of this situation was to kill the process. After much head scratching trying to figure out what was causing this I discovered in my .prf file that there is a macro bound to 'g' of 'g', and this causes this bad behaviour. To fix it I just removed the macro from my prf file (which is what I assumed the remove macro function would do).
Yay for long stories
Comment