Closed dgets closed 9 years ago
This is another problem with utilizing properties from different parent objects (or even the same parent object at times). Not sure what's causing it, so at the expense of flexibility I'm going to just put constants inline here. This is barring a complete rewrite of the room info code within dperroom.js, which is now on the schedule, of course.
This has changed a bit since the original screenshot:
Node Status
----------------
1 Khelair at main menu via telnet (P)
[] Read your mail now? No
Executing ddoc2.js; trying to bring back the vDoc experience . . .
Looking for room info file: NaN
Flag: flow_control Value: false
Flag: message_posting Value: true
Flag: message_scan Value: true
Flag: instant_messaging Value: false
Flag: navigation Value: true
Flag: file_io Value: true
Flag: misc Value: true
Turning off Synchronet defaults for dDoc
Using node #: 2
Testing for existance of: /sbbs/data/user/durooms: true
Allegedly /sbbs/data/user/durooms exists, according to zappedFile.exists: true
Got back chunky: {"49":{"zRooms":[],"alias":"Ddoctest"},"1":{"zRooms":[2,1]}} in stripNRead()
Got back blob: {"49":{"zRooms":[],"alias":"Ddoctest"},"1":{"zRooms":[2,1]}}
Lobby>
Not sure what on earth is going on with this. I've attempted zapping some rooms to see if this had anything to do with the initial setup for the user zapped configuration. That didn't seem to help at all. Anyway this is probably indicative of a larger set of bugs going on that needs to be taken care of. Other issues to check into might be the room info data set. Track down where that File NaN is coming from for some more info on this.