Darl181 was testing Elimination for me, and he said that he has the following problems on his Ti-84+ BE:

"Walking right (XTΘn) doesn't work for me, however walking left does (ALPHA Key).  Mode brings up a map and fires when you press it again to hide the map (and that fire consumes 2 ammunition), and 2nd toggles the HUD whilst firing.
Pressing apps brings up the light saber as it's supposed to, but only after displaying the map."

In the game, 2nd and MODE are only supposed to fire, nothing else.  The map is supposed to be toggled with MATH, and the HUD is supposed to be toggled with x^-1.  I never have these problems on the Ti-83+ SE, is there something that might be causing these problems on this Ti-84+ BE?

Here's some things that Elimination does.  I don't know if it's causing the problem, but it doesn't hurt to list them.  Again, I don't have any of these problems on my Ti-83+ SE.
---------------------------------------------

* Elimination switches flash pages using ports
* Elimination uses crystal timers (for interrupts)
* Elimination uses page $83 for data storage in the $C000-$FFFF area
* Elimination uses ports for keypresses

It sounds to me like your key-reading routine doesn't have enough delay between writing to and reading from the key port. I'm not sure how much delay is safe enough for every calculator, but I know that Quigibo recently increased Axe's number of cycles between the port write and read for key input from 19 to 22 cycles because it turned out that 19 cycles isn't enough for some calculators running at 15MHz. Interestingly enough, Darl181 is the one who reported this problem for Axe as well.

Now that makes sense.  I'm so used to 8 cycles for 6 MHz, I forgot that 15 Mhz needs more time.  Thanks!

I'll say that I've had similar problems before, but it seems other people had those too (such as if some odd key were pressed in Devrays the player would move).

84pbe, 2.43, hardware rev. B.
Apps installed are zStart, and Omnicalc through zStart.

Technically, you should write $FF before writing the key group to check. Writing $FF after reading should work too, I guess, but not necessarily for the very first read.

I will say that I have had these kinds of problems before and I got frustrated and added a call 000Bh as the delay and that didn't work I have mentioned this before, but I was told it was a delay issue. Also, I was writing $FF to the port before each write, as well. I wonder if there is a hardware issue in some models? Mine was an 84+SE without the extra RAM and a 84+BE without the extra RAM. Here is what I could do:

Press left and the plus key. Then press Enter and the down key is registered.

It was always things like that, but I could just have coded something wrong or misunderstood the documentation. I will check again later comparing WabbitEmu to my actual calc and whatnot.