Closed dgets closed 9 years ago
I may have been incorrect in my initial assumption of what was going on here. It looks like it might be a little simpler, at this point, because the code scans Lobby> twice, every time (see the other issue), and then it stops, at the end of every scan, at Babble> now, not just whatever the last room read was.
This appears to be a non-issue.
After jumping to a room, it doesn't matter how many different scans are made, after thoroughly searching the message base (except for the most recent 1 message issue that seems to be going on right now in a few places), the primary prompt always drops back to the last room jumped to. After a scan without anything being available, or after everything is read, the sub-group or room should be reset to Lobby> if restricted, or whatever is sub-group 0 if in a different message group in a non-restricted session (which is still awaiting a lot of work for full implementation).