With the refactor to handle STATUS as a FIFO queue, in ProcessIncomingCharacter(), when 0xD was detected, it wasn't enqueuing a status of 3 unless the queue was empty. Because MajorMUD uses polling, the STATUS queue contained 192, meaning the input ready status of 3 wasn't being added.
I changed the logic to always enqueue status of 3 on 0xD input, after it does the BTUCHI input check. This is the correct action.
Fixing this re-enables input on MajorMUD
I also added a couple more friendly error messages/help when the MajorBBS/Worldgroup module isn't configured or installed properly.
With the refactor to handle
STATUSas a FIFO queue, inProcessIncomingCharacter(), when0xDwas detected, it wasn't enqueuing a status of3unless the queue was empty. Because MajorMUD uses polling, theSTATUSqueue contained192, meaning the input ready status of3wasn't being added.I changed the logic to always enqueue status of
3on0xDinput, after it does the BTUCHI input check. This is the correct action.Fixing this re-enables input on MajorMUD
I also added a couple more friendly error messages/help when the MajorBBS/Worldgroup module isn't configured or installed properly.