Request Change Name Scroll "Fixed"

01/09/2019 00:54 devdash#1

i have tried many Change Name Scrolls and all looks same to me, but all of em used diffrent codes from each other, and all the topics write "the fixed one" or "after fix" or "without bugs"

my request is what is the one should i use ? i dont want to suffer later, since i don't have the required skills to fix problems that may pop up later as people warrned

thanks in advance...

01/09/2019 01:43 #HB#2

As much as I remember, this one was working:

_TimedJob: [Only registered and activated users can see links. Click Here To Register...].

Proc: [Only registered and activated users can see links. Click Here To Register...].

01/09/2019 12:03 Leodoom#3

Spoiler

01/09/2019 12:30 devdash#4

i really apprecaite your both answers i mean it, but that's what iam exactly suffering from :), in charname scroll there's thousands of producer, which one should i use,i think the addlogitem one is better which Leodoom is, but i still don't know if should i use it or it will may be the reason of any bugs later, i dont want to stuck later, excuse my fears, i'm just a begginer and in the begginer world everything scary till someone explain it...

please replay back if you can...
thanks in advance

01/09/2019 14:34 #HB#5

Each has its usage, the _AddLogItem is possible for any type of scrolls, _TimeJob can be used too if you're using a skill, all you need is to add "@" at the beginning of the name, so when he logs into the account, he should pick up a new name for his character.

By the way, this code of the guy above:

Code:

Declare #newcharName varchar (64) = (select CharName16 from SRO_VT_SHARD.._Char where CharID = #ChariD and Charname16 not like '%@%')
update SRO_VT_SHARD.._CharNameList set Charname16 = #newcharName
update SRO_VT_SHARD.._Friend set FriendCharname = #newcharName where FriendCharName = #charname16 
Update SRO_VT_SHARD.._GuildMember set CharName = #newcharName where CharName = #charname16

That's wrong, _RenameCharNameByID should be handling this. Also, that's not the new name, he didn't pick up his new name yet, so your variable (#newcharName) would end up like, "@ + current charname".

01/09/2019 18:46 devdash#6

Quote:
Originally Posted by #HB
Each has its usage, the _AddLogItem is possible for any type of scrolls, _TimeJob can be used too if you're using a skill, all you need is to add "@" at the beginning of the name, so when he logs into the account, he should pick up a new name for his character.

By the way, this code of the guy above:
Code:
Declare #newcharName varchar (64) = (select CharName16 from SRO_VT_SHARD.._Char where CharID = #ChariD and Charname16 not like '%@%')
update SRO_VT_SHARD.._CharNameList set Charname16 = #newcharName
update SRO_VT_SHARD.._Friend set FriendCharname = #newcharName where FriendCharName = #charname16 
Update SRO_VT_SHARD.._GuildMember set CharName = #newcharName where CharName = #charname16
That's wrong, _RenameCharNameByID should be handling this. Also, that's not the new name, he didn't pick up his new name yet, so your variable (#newcharName) would end up like, "@ + current charname".

then at the next relogin he will have to change he's name from @+current to he's new name before he can log, is that will effect any problems?

01/09/2019 19:39 #HB#7

Quote:

Originally Posted by alydandy

then at the next relogin he will have to change he's name from @+current to he's new name before he can log, is that will effect any problems?

AFAIR, "@" tells the server files to force him to change his name before he opens his character. So, he has to get disconnected then add the "@" and server files will continue the work.

01/09/2019 19:56 devdash#8

Quote:

Originally Posted by #HB

AFAIR, "@" tells the server files to force him to change his name before he opens his character. So, he has to get disconnected then add the "@" and server files will continue the work.

so what u want to say, is that the both will work fine, but 1# will force him to instant rename wish means dc then rename, and the 2# will force him to rename in he's next login, so basically i can choose anyone ? no problems at all ? up to me ? or there's a one that better than one ?

01/09/2019 20:56 #HB#9

Yeah, but don't do this:

Code:

Declare #newcharName varchar (64) = (select CharName16 from SRO_VT_SHARD.._Char where CharID = #ChariD and Charname16 not like '%@%')
update SRO_VT_SHARD.._CharNameList set Charname16 = #newcharName
update SRO_VT_SHARD.._Friend set FriendCharname = #newcharName where FriendCharName = #charname16 
Update SRO_VT_SHARD.._GuildMember set CharName = #newcharName where CharName = #charname16

It's not required. This only enough:

Code:

Update _Char Set CharName16 = '@'+ CharName16 Where CharID = #CharID
return -3 // DC

And then its up to you to use _AddLogItem or _TimedJob. Also, I am not sure if _AddLogItem can DC.

01/09/2019 21:34 devdash#10

Quote:

Originally Posted by #HB

Yeah, but don't do this:

Code:

Declare #newcharName varchar (64) = (select CharName16 from SRO_VT_SHARD.._Char where CharID = #ChariD and Charname16 not like '%@%')
update SRO_VT_SHARD.._CharNameList set Charname16 = #newcharName
update SRO_VT_SHARD.._Friend set FriendCharname = #newcharName where FriendCharName = #charname16 
Update SRO_VT_SHARD.._GuildMember set CharName = #newcharName where CharName = #charname16

It's not required. This only enough:

Code:

Update _Char Set CharName16 = '@'+ CharName16 Where CharID = #CharID
return -3 // DC

And then its up to you to use _AddLogItem or _TimedJob. Also, I am not sure if _AddLogItem can DC.

you gave to me all the answers i wanted <3, thanks #HB i really appreciate ur help <3 , best wishes in your life bro deserve it

close topic please

01/10/2019 01:43 Leodoom#11

Thank you for explaining this thing that you missed