New message scan works for Babble>, not for Dexter> (probably more errata, also)
dgets opened this issue · 2 comments
dgets commented
Though I am now able to execute a new scan, and have it start reading the new messages in the correct direction, the scan is failing to find new messages (1 or more than one, so it's not a < vs. <= error or anything of the sort) in random subs. For now it's managing to pick up on new messages in Babble> without a problem, but when I've added a new message to Dexter> it'll fly right by it. Need to do more testing and see where this issue might be at.
dgets commented
As can be seen in the following output:
Room not zapped scan_ptr: 13 total: 6
1: false
Opened: topegrpbabble allegedly . . .
Room not zapped scan_ptr: 21 total: 21
2: false
Opened: topegrpneutrons allegedly . . .
Room not zapped scan_ptr: 15 total: 13
3: false
Opened: topegrpnewsandw allegedly . . .
Room not zapped scan_ptr: 2082147520 total: 2
4: false
Opened: topegrpcurrenta allegedly . . .
Room not zapped scan_ptr: 2155535360 total: 1
5: false
Opened: topegrpdextersl allegedly . . .
Room not zapped scan_ptr: 2078032576 total: 3
6: false
Opened: topegrpskeptica allegedly . . .
Room not zapped scan_ptr: 2198280576 total: 0
7: false
Opened: topegrpspecialr allegedly . . .
Room not zapped scan_ptr: 2072424640 total: 0
Got topegrplobby in user.cursub
Lobby>
it looks like this might actually not be a bug in the code, but some sort of bullshit going on where the message scan pointers got horked somehow. I'll have to post on DOVE-Net and try to get more details on that. :P