Stupid question but need smart answers
like the topic said I know its a stupid answer most ppl will say search or google... I have tried googling.. way too much in fact... im using mr killers v80 files on VMware... well im getting matrixpasswrd is NOT usbbind user 48... which I know the id of the user is 48 and I just started this server from scratch.. I know that the charcters ave to start with 1024.. ive read that somewhere on here along time ago.. cant seem to find that post on how to fix that... but I also wondering is that the cause of that? or is it the register scripts... I have used 3 reg.phps even the pwadmin one of the devs got working for 1.4.5, and even iweb still wont give me the id... yeah I know I can physically change it in the database... but im also wondering on how to fix or what I need to replace.
Re: Stupid question but need smart answers
matrixpasswrd is NOT usbbind
I use my own authd and register script with every release and never have this issue. :wink:
Re: Stupid question but need smart answers
yeah I had my own a long time ago so im starting new now and cant find a working copy that works and hate to have to download every server file to see
Re: Stupid question but need smart answers
SQL is the problem, if you're talking about wanting to get the account and character numbers to match (1024/1024)
you're going to want to change the procedure ADDUSER to the following:
Code:
DROP PROCEDURE IF EXISTS `adduser`$$
CREATE DEFINER=`root`@`localhost` PROCEDURE `adduser`(
in name1 VARCHAR(64),
in passwd1 VARCHAR(64),
in prompt1 VARCHAR(32),
in answer1 VARCHAR(32),
in truename1 VARCHAR(32),
in idnumber1 VARCHAR(32),
in email1 VARCHAR(32),
in mobilenumber1 VARCHAR(32),
in province1 VARCHAR(32),
in city1 VARCHAR(32),
in phonenumber1 VARCHAR(32),
in address1 VARCHAR(64),
in postalcode1 VARCHAR(8),
in gender1 INTEGER,
in birthday1 VARCHAR(32),
in qq1 VARCHAR(32),
in passwd21 VARCHAR(64)
)
BEGIN
DECLARE idtemp INTEGER;
SELECT IFNULL(MAX(id), 1008) + 16 INTO idtemp FROM users;
INSERT INTO users (id,name,passwd,prompt,answer,truename,idnumber,email,mobilenumber,province,city,phonenumber,address,postalcode,gender,birthday,creatime,qq,passwd2) VALUES( idtemp, name1, passwd1, prompt1, answer1, truename1, idnumber1, email1, mobilenumber1, province1, city1, phonenumber1, address1, postalcode1, gender1, birthday1, now(), qq1, passwd21 );
END$$
Note the KEY change is highlighted below (the rest should be the same as whatever DB you have):
DROP PROCEDURE IF EXISTS `adduser`$$
CREATE DEFINER=`root`@`localhost` PROCEDURE `adduser`(
in name1 VARCHAR(64),
in passwd1 VARCHAR(64),
in prompt1 VARCHAR(32),
in answer1 VARCHAR(32),
in truename1 VARCHAR(32),
in idnumber1 VARCHAR(32),
in email1 VARCHAR(32),
in mobilenumber1 VARCHAR(32),
in province1 VARCHAR(32),
in city1 VARCHAR(32),
in phonenumber1 VARCHAR(32),
in address1 VARCHAR(64),
in postalcode1 VARCHAR(8),
in gender1 INTEGER,
in birthday1 VARCHAR(32),
in qq1 VARCHAR(32),
in passwd21 VARCHAR(64)
)
BEGIN
DECLARE idtemp INTEGER;
SELECT IFNULL(MAX(id), 1008) + 16 INTO idtemp FROM users;
INSERT INTO users (id,name,passwd,prompt,answer,truename,idnumber,email,mobilenumber,province,city,phonenumber,address,postalcode,gender,birthday,creatime,qq,passwd2) VALUES( idtemp, name1, passwd1, prompt1, answer1, truename1, idnumber1, email1, mobilenumber1, province1, city1, phonenumber1, address1, postalcode1, gender1, birthday1, now(), qq1, passwd21 );
END$$
Also, changing this will obviously NOT change an existing server, IE: if you already have a server with 1000 accounts (or even just 1), changing this will make it so that the FIRST account starts @ 1024, so that account and first toon will properly match @ 1024/1024...
Re: Stupid question but need smart answers
thanks I fixed this issue... what I did was put the new auth in I downloaded from here to fix the blackskys database.. and used that sql it had with it... and it worked but all in all it was in the database as not reading the players id or starting id of 1024... instead of it going to the 1.3.6 where it starts out at 16, but I got it fixed so this can be closed.... but for all those that do have this problem this might help them.
Re: Stupid question but need smart answers