Who's On
Moderator: Moderators
- solar
- Supporting Member 2020
- Posts: 541
- Joined: Sat Apr 03, 2004 17:30 pm
- Location: Kalajoki/Oulu, Finland
All fellow mudders unite!
If I remember correctly wizards said that they were useless or wouldn't be brought back. I might be mistaken of course. One thing I do know is that there is a chance that if enough people would agree with you (Very much like I do now, by posting this reply here for all to look at), they could change their heads... and eventually claim that it was their intent all along
So... if you agree with something... think about bringing it up somehow.
So... if you agree with something... think about bringing it up somehow.
Internet tough guy
Icesus is not just my life - it's the lack of it.
Icesus is not just my life - it's the lack of it.
I didn't have too much time to enjoy that feature since I was übernoob when it was removed. also the commands and other stuff was very useful before I got used to the commands and help files and all that. for a newbie like me it's very nice to just click the commands and help files instead of typing them.
that's just me being lazy, tho.
that's just me being lazy, tho.
The biggest reason for the removal is that they were "quite the kludge" to put mildly. Maybe someday someone will come up with a way that is less of a kludge and they will be reimplemented, but that day is not in the foreseeable future at the moment.
#define BITCOUNT(x) (((BX_(x)+(BX_(x)>>4)) & 0x0F0F0F0F) % 255)
#define BX_(x) ((x) - (((x)>>1)&0x77777777) - (((x)>>2)&0x33333333) - (((x)>>3)&0x11111111))
#define BX_(x) ((x) - (((x)>>1)&0x77777777) - (((x)>>2)&0x33333333) - (((x)>>3)&0x11111111))
The basic problem is, the data is in the mud-driver and it needs to get to the webserver, which is running in a separate process. The old superkludge solution was a minimal quickhack "webserver" built into the mud-driver which handled the gateway pages, but that didn't really understand HTTP protocol too well (so some browsers would not work too nicely with it) and it used a nonstandard port which meant people behind firewalls might or might not be able to use the gateway pages. (There's also the point of how, umm, interestingly the old implementation abused the "who" command but that's a side issue.)artic wrote:If you could descibe the problem more exactly than maybe we could help you come up with a solution?
Obvious solutions are to either write the data to a file every X seconds/minutes/whatever and let the webserver use that file, or to write a frontend page that uses php functions to do socket access to the mud-driver.
#define BITCOUNT(x) (((BX_(x)+(BX_(x)>>4)) & 0x0F0F0F0F) % 255)
#define BX_(x) ((x) - (((x)>>1)&0x77777777) - (((x)>>2)&0x33333333) - (((x)>>3)&0x11111111))
#define BX_(x) ((x) - (((x)>>1)&0x77777777) - (((x)>>2)&0x33333333) - (((x)>>3)&0x11111111))
- artic
- Supporting Member 2005
- Posts: 475
- Joined: Wed Apr 14, 2004 15:54 pm
- Location: Tallinn, Estonia
yes for the helpfiles and such a php could be written that lists the files in some /help directory in the mud and such. But for the 'who' and other gateways an exported data set is needed, wich then is updated every now and then. I dont know if such an updating would slow down our brand new server ?
Pages
I used to use the help section frequently, and still would if it was there. I have a rotten memory, particularly for syntax and used to keep several pages open in different tabs. It was also quite the best way of reading things like the adjectives or armour pages, you could scroll back and forth much more easily than in zmud.
I would also put in a vote for having the who/finger pages recoded when someone has the time.
I would also put in a vote for having the who/finger pages recoded when someone has the time.
You already do? As far as I know "who" command is usable for everyone...alaye wrote:maybe we could have a command in the mud, that shows who's currently online, instead?
#define BITCOUNT(x) (((BX_(x)+(BX_(x)>>4)) & 0x0F0F0F0F) % 255)
#define BX_(x) ((x) - (((x)>>1)&0x77777777) - (((x)>>2)&0x33333333) - (((x)>>3)&0x11111111))
#define BX_(x) ((x) - (((x)>>1)&0x77777777) - (((x)>>2)&0x33333333) - (((x)>>3)&0x11111111))