[hmm? question] removing item lock, client side.

07/21/2009 02:33 TasteofChaos#1
any idea where i'd have to do this? and also how? I hate this, it mainly takes all fun out of pking anymore.. TQ was stupid to implement it. I wanna revert to many older features.. beginning with this :D anyone gotsa idea on this?
07/21/2009 02:38 raidenx123#2
No it is source sided so you cant take it out of client =x
07/21/2009 02:41 TasteofChaos#3
what about as in.., taking it out of source? i mean like.. the use.. but, there HAS to be the item lock client thing. i mean.. just the box to lock your item.. i mean what you think?
07/21/2009 02:46 raidenx123#4
Yeah but if u remove from client it searches in data.wdf and you cant remove that or shit will happen.
07/21/2009 03:17 TasteofChaos#5
damn.. so wait, when you're item's locked, does any status change in the database? such as a 0 to 1? unlocked - locked? hmm.. if there is, i could remove that which would possibly remove the whole item lock effect?
07/21/2009 03:47 raidenx123#6
Yes i believe so...
07/21/2009 05:40 _tao4229_#7
theres a check in conquer.exe for locked items etc, if you're good at asm you can probably jump over the check
07/21/2009 06:00 f0am#8
Isn't this the wrong section, client edits isnt here.
07/21/2009 06:18 TasteofChaos#9
Quote:
Originally Posted by f0am View Post
Isn't this the wrong section, client edits isnt here.
not quite, i guess like halfway, we also were talking about what source sided affects it.
07/21/2009 06:47 andyd123#10
If you're talking about tq binaries(which you probably are) there is no "source side" are you only have the executable.
Removing the column in the database will just cause errors.
The only semi-easy way would be for you to ollydebug and jump over the call that sets locked/unlocked.
07/21/2009 20:55 TasteofChaos#11
Quote:
Originally Posted by andyd123 View Post
If you're talking about tq binaries(which you probably are) there is no "source side" are you only have the executable.
Removing the column in the database will just cause errors.
The only semi-easy way would be for you to ollydebug and jump over the call that sets locked/unlocked.

lmao dude, i am so stupid. I was referring to 5017, and didn't know that it wasnt on there.. wow. lol yea.. i already gave myself a neck.. you can close.

#request close