Heh, OK then.
Changing BBS User-ID / Account Names?
Re: Changing BBS User-ID / Account Names?
Any way you do this is going to be wonky with modules, but if you are looking to rename someone without the care of modules then you can use ADV Rename, not sure if there are WGDOS and MBBS versions but I know I have a working WG3 version.
From the NFO:
From the NFO:
Code: Select all
Allow's Sysops to change a user's handle without creating a new
account. Also allows users to change their own handles, with the
option of charging them for the priviledge, either credits or
days. Rename ends the hassle of having to create a new account
and then switch class, give keys, access and credits and then
delete the old account. Now you can do everything in one easy
step. It can also copy your users Email and Registry entry to
their new account also.
C/S user interface.
Re: Changing BBS User-ID / Account Names?
Thanks Kyau. It wasn't until I started working on the systems-side of WG and MajorMUD that I realized that the BBS user-IDs are the real identifiers and not an id code number (like is standard today). You're right that I would have to change all the names in all the extra modules that I have running. I'll see if I can find that add-on for WG/MBBS.
Re: Changing BBS User-ID / Account Names?
I found the WG version on major.butt.care . Gonna try it out later.
Re: Changing BBS User-ID / Account Names?
OK I have a registered copy of ADV Renamer for WG2 that works.
It doesn't change module names. Just the core WG stuff.
I did test editing WCCUSERS.DAT after with the new name. Seems to work fine.
I should note that this module will tag the old user ID for kill when a user logs in on the old ID *AFTER* the change has happened.
Kinda weird. I guess if you wanted to protect the old account from deletion, you could flag it as protected.
It doesn't change module names. Just the core WG stuff.
I did test editing WCCUSERS.DAT after with the new name. Seems to work fine.
I should note that this module will tag the old user ID for kill when a user logs in on the old ID *AFTER* the change has happened.
Kinda weird. I guess if you wanted to protect the old account from deletion, you could flag it as protected.