Quote:
Originally Posted by mocdragon
I’m still trying to figure out how the tir teleport works. If I got an understanding of that I would be able to make much more happen.
|
How the "tir teleport" works:
->You send an OP Code
->Server Reacts to the OP Code
--->Server Reads the OP Code
--->Looks for the Function in their database associated with the heading
--->Server: "Oh hey, this OP Code belongs to: 'Change CharacterLocationID from XXXXX(Original) to YYYYYY(Tir Location) in dabatase under ZZZZZ(AccountID) WWWWW(CharacterID)"
---> Server looks for AccountID 'ZZZZZ' then for characterID 'WWWWW' then for the CharacterLocationID table, and changes the value XXXXX to YYYYYY.
->Your character is now in Tir.
In other words, the ONLY way you can modify the "tir teleport" OP code's function, consequently the reason why you won't make much more of anything(DC's excluded) happen, would be hacking the server database and directly altering the function of said OP Code.
I think that sums it up...
Cheers,
Nogi'le
EDIT: Forgot to mention, being that character ID's are supposed to be different under any circumstances, looking for the Account ID is unnecessary; depending on the programmer of the function he would have chosen one of two common roads: either search the database for the Character ID directly, or to decrease overall searching time, he would first look through Account IDs, then sort out the characters, since logically there are many more characters within the server than accounts(I assume the 2nd path to be shorter, thus I mentioned it only initially).
Edit 2: Never mind... This strongly depends on how the servers are built, since the packet sends only your character ID, the Account ID method would be inefficient and would likely actually increase searching time due to unnecessary steps.