We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
created skeleton
explained bit about methods being bogus & in the process of rewritten
added some details on modifications that have taken place
changed title
added links to 'new proposed scan method' which I'm going to use when gutting and rewriting the message base in a way I can understand better
started describing the new message scan control flow; to be continued
added reportOnlineTime()
explained moar
added more about enclosing structure that wasn't referenced
changed name of a routine for clarity; remove superfluous shit
updated documentation for current; need to have a look at the UX structure, though, I think I duplicated pointlessly
added documentation for new less-monolithic functionality (and more modular for use in other text areas)
added infoCreationDate
created with a dump of the current JSON records' structure
changed to reflect location of where the new schema is going
well this is definitely up to date now
moved snagUserZappedRooms() to where it is now reflected in the source
brought up to current; created most of this file for the first time
brought up to current; not much work in it for this one to do so, though the code is in definite need of refactoring which will change this again
updated documentation for current; note that a huge amount of the content in this area is now due to @ntwitch
minor updates to everything here; most of it was still legit
made a small start
ouah
updated documentation for the current date
added more information; link to new code segment
fixed user.name which was supposed to be user.alias
changed complex methods to links to detail what's going on there; brought shit up to current, added new methods
changed the format just a bit
changing the format of the record structure
changed format of some of the hash table in order to simplify the code that'll pull values