item.sdata cheat can be fixed?

well i have seen and heard about the easy lvl 15 and lvl 30 pvp can be killed easy with just using a tool to fix the lvl on lapis from 31 to 15 and use that in 15 gear..

is there a fix for this in any way?

well if they aren't matching the database they still can not cheat as long as you have the lapis set of the level above level 15 and 30 as you have wrote and if you recently updated lapis and they had been linked before that's the issue that you would have
but they can not unless the database matches there clients ;)

There is no possible way to damage hack through an sdata file.
Sdata files are purely visual while the database is the data side that makes the effects truly happen.
While a player may edit their sdata files to show they have 10k to each stat off a edited lapis in reality the data in the database is what they truly have.
So no there is no way to mess with the item.sdata to improve your damage unless it is edited in the database as well.

@ Snuggle
He's talking about linking LV7 Lapis in 15 or 30 PvP Gear. I read here that you can link them in 1-30 gear although. You just have to edit required level in Item.SData.

@ThreadStarter

I'm sorry but i don't know any way. Maybe you can try to use a script which removes the linked lapis from 1-30 gear, and run this script every 2 hours or day.

So long

Dan

i was talking about this stuff: [Only registered and activated users can see links. Click Here To Register...]

so this don't work?

no clue try it :P

Quote:

Originally Posted by Svinseladden i was talking about this stuff: [Only registered and activated users can see links. Click Here To Register...] so this don't work?

You can change lapis levels as i just have replied before i have made my own customized for pvp maps 15-30 pvp and they can be linked only for those pvps lvl maps so yeah it works and is true :)

just tested it. this works.. and it even goes in the db when you loggout. so this works like perfect. now we just need a perfect anti tool:-P

i made a sql like this:

Quote:

Select ci.CharID ,ci.Type ,ci.TypeID ,i.ItemName ,i.ReqLevel ,ci.Bag ,ci.Slot ,ci.ItemUID ,ci.Craftname ,ci.Gem1 ,ci.Gem2 ,ci.Gem3 ,ci.Gem4 ,ci.Gem5 ,ci.Gem6 ,ci.Quality ,ci.Count ,ci.Del From PS_GameData.dbo.CharItems ci inner join PS_GameDefs.dbo.Items i on ci.Type=i.Type and ci.TypeID = i.TypeID Where i.ReqLevel < 31 and ci.Gem1='7' or i.ReqLevel < 31 and ci.Gem1='14' or i.ReqLevel < 31 and ci.Gem1='21' or i.ReqLevel < 31 and ci.Gem1='28' or i.ReqLevel < 31 and ci.Gem1='35' or i.ReqLevel < 31 and ci.Gem1='42' or i.ReqLevel < 31 and ci.Gem1='49' or i.ReqLevel < 31 and ci.Gem1='56' or i.ReqLevel < 31 and ci.Gem1='63' or i.ReqLevel < 31 and ci.Gem1='82' or i.ReqLevel < 31 and ci.Gem1='96' or i.ReqLevel < 31 and ci.Gem1='105' or i.ReqLevel < 31 and ci.Gem1='124' or i.ReqLevel < 31 and ci.Gem1='125' or i.ReqLevel < 31 and ci.Gem1='126' or i.ReqLevel < 31 and ci.Gem1='127' or i.ReqLevel < 31 and ci.Gem1='143' or i.ReqLevel < 31 and ci.Gem1='150' or i.ReqLevel < 31 and ci.Gem1='177' or i.ReqLevel < 31 and ci.Gem1='178' or i.ReqLevel < 31 and ci.Gem1='179' or i.ReqLevel < 31 and ci.Gem1='180' or i.ReqLevel < 31 and ci.Gem1='189' or i.ReqLevel < 31 and ci.Gem1='190' or i.ReqLevel < 31 and ci.Gem1='241' or i.ReqLevel < 31 and ci.Gem1='242' or i.ReqLevel < 31 and ci.Gem1='243' or i.ReqLevel < 31 and ci.Gem1='254' or i.ReqLevel < 31 and ci.Gem1='255' or i.ReqLevel < 31 and ci.Gem2='7' or i.ReqLevel < 31 and ci.Gem2='14' or i.ReqLevel < 31 and ci.Gem2='21' or i.ReqLevel < 31 and ci.Gem2='28' or i.ReqLevel < 31 and ci.Gem2='35' or i.ReqLevel < 31 and ci.Gem2='42' or i.ReqLevel < 31 and ci.Gem2='49' or i.ReqLevel < 31 and ci.Gem2='56' or i.ReqLevel < 31 and ci.Gem2='63' or i.ReqLevel < 31 and ci.Gem2='82' or i.ReqLevel < 31 and ci.Gem2='96' or i.ReqLevel < 31 and ci.Gem2='105' or i.ReqLevel < 31 and ci.Gem2='124' or i.ReqLevel < 31 and ci.Gem2='125' or i.ReqLevel < 31 and ci.Gem2='126' or i.ReqLevel < 31 and ci.Gem2='127' or i.ReqLevel < 31 and ci.Gem2='143' or i.ReqLevel < 31 and ci.Gem2='150' or i.ReqLevel < 31 and ci.Gem2='177' or i.ReqLevel < 31 and ci.Gem2='178' or i.ReqLevel < 31 and ci.Gem2='179' or i.ReqLevel < 31 and ci.Gem2='180' or i.ReqLevel < 31 and ci.Gem2='189' or i.ReqLevel < 31 and ci.Gem2='190' or i.ReqLevel < 31 and ci.Gem2='241' or i.ReqLevel < 31 and ci.Gem2='242' or i.ReqLevel < 31 and ci.Gem2='243' or i.ReqLevel < 31 and ci.Gem2='254' or i.ReqLevel < 31 and ci.Gem2='255' or i.ReqLevel < 31 and ci.Gem3='7' or i.ReqLevel < 31 and ci.Gem3='14' or i.ReqLevel < 31 and ci.Gem3='21' or i.ReqLevel < 31 and ci.Gem3='28' or i.ReqLevel < 31 and ci.Gem3='35' or i.ReqLevel < 31 and ci.Gem3='42' or i.ReqLevel < 31 and ci.Gem3='49' or i.ReqLevel < 31 and ci.Gem3='56' or i.ReqLevel < 31 and ci.Gem3='63' or i.ReqLevel < 31 and ci.Gem3='82' or i.ReqLevel < 31 and ci.Gem3='96' or i.ReqLevel < 31 and ci.Gem3='105' or i.ReqLevel < 31 and ci.Gem3='124' or i.ReqLevel < 31 and ci.Gem3='125' or i.ReqLevel < 31 and ci.Gem3='126' or i.ReqLevel < 31 and ci.Gem3='127' or i.ReqLevel < 31 and ci.Gem3='143' or i.ReqLevel < 31 and ci.Gem3='150' or i.ReqLevel < 31 and ci.Gem3='177' or i.ReqLevel < 31 and ci.Gem3='178' or i.ReqLevel < 31 and ci.Gem3='179' or i.ReqLevel < 31 and ci.Gem3='180' or i.ReqLevel < 31 and ci.Gem3='189' or i.ReqLevel < 31 and ci.Gem3='190' or i.ReqLevel < 31 and ci.Gem3='241' or i.ReqLevel < 31 and ci.Gem3='242' or i.ReqLevel < 31 and ci.Gem3='243' or i.ReqLevel < 31 and ci.Gem3='254' or i.ReqLevel < 31 and ci.Gem3='255' or i.ReqLevel < 31 and ci.Gem4='7' or i.ReqLevel < 31 and ci.Gem4='14' or i.ReqLevel < 31 and ci.Gem4='21' or i.ReqLevel < 31 and ci.Gem4='28' or i.ReqLevel < 31 and ci.Gem4='35' or i.ReqLevel < 31 and ci.Gem4='42' or i.ReqLevel < 31 and ci.Gem4='49' or i.ReqLevel < 31 and ci.Gem4='56' or i.ReqLevel < 31 and ci.Gem4='63' or i.ReqLevel < 31 and ci.Gem4='82' or i.ReqLevel < 31 and ci.Gem4='96' or i.ReqLevel < 31 and ci.Gem4='105' or i.ReqLevel < 31 and ci.Gem4='124' or i.ReqLevel < 31 and ci.Gem4='125' or i.ReqLevel < 31 and ci.Gem4='126' or i.ReqLevel < 31 and ci.Gem4='127' or i.ReqLevel < 31 and ci.Gem4='143' or i.ReqLevel < 31 and ci.Gem4='150' or i.ReqLevel < 31 and ci.Gem4='177' or i.ReqLevel < 31 and ci.Gem4='178' or i.ReqLevel < 31 and ci.Gem4='179' or i.ReqLevel < 31 and ci.Gem4='180' or i.ReqLevel < 31 and ci.Gem4='189' or i.ReqLevel < 31 and ci.Gem4='190' or i.ReqLevel < 31 and ci.Gem4='241' or i.ReqLevel < 31 and ci.Gem4='242' or i.ReqLevel < 31 and ci.Gem4='243' or i.ReqLevel < 31 and ci.Gem4='254' or i.ReqLevel < 31 and ci.Gem4='255' or i.ReqLevel < 31 and ci.Gem5='7' or i.ReqLevel < 31 and ci.Gem5='14' or i.ReqLevel < 31 and ci.Gem5='21' or i.ReqLevel < 31 and ci.Gem5='28' or i.ReqLevel < 31 and ci.Gem5='35' or i.ReqLevel < 31 and ci.Gem5='42' or i.ReqLevel < 31 and ci.Gem5='49' or i.ReqLevel < 31 and ci.Gem5='56' or i.ReqLevel < 31 and ci.Gem5='63' or i.ReqLevel < 31 and ci.Gem5='82' or i.ReqLevel < 31 and ci.Gem5='96' or i.ReqLevel < 31 and ci.Gem5='105' or i.ReqLevel < 31 and ci.Gem5='124' or i.ReqLevel < 31 and ci.Gem5='125' or i.ReqLevel < 31 and ci.Gem5='126' or i.ReqLevel < 31 and ci.Gem5='127' or i.ReqLevel < 31 and ci.Gem5='143' or i.ReqLevel < 31 and ci.Gem5='150' or i.ReqLevel < 31 and ci.Gem5='177' or i.ReqLevel < 31 and ci.Gem5='178' or i.ReqLevel < 31 and ci.Gem5='179' or i.ReqLevel < 31 and ci.Gem5='180' or i.ReqLevel < 31 and ci.Gem5='189' or i.ReqLevel < 31 and ci.Gem5='190' or i.ReqLevel < 31 and ci.Gem5='241' or i.ReqLevel < 31 and ci.Gem5='242' or i.ReqLevel < 31 and ci.Gem5='243' or i.ReqLevel < 31 and ci.Gem5='254' or i.ReqLevel < 31 and ci.Gem5='255'

this is my item list so change it to your item list..

but this is only for checking. for now i'm going to give them 1 chance to get clean if not banning is the option:-P

but if some have a way to make this as a command please share:-)

i don't know why capes always end up in this lapis query's but they do.. LOL no capes are not normaly linked..even tho they say so in the db..

This is not a bug or something, it's jus lazy admins who are to lazy to check out. Just like people up from me said, just edit DB and they will fail to hack this. =)

I dont normally post, but I have had some experience with this in the past. For lapis, its not the ReqLevel field that determines its minimum level for linking. its the ReqInt field in the database. Set that to 30 for example, and the lapis will not be linkable into an item that is below level 30. I hope this helps

I know what he was asking. Adding lapis to a gear that not supposed to be linked with those levels would be considered a form of hack.
If you edit the levels within the database there is no possible way for this to be hacked.

Quote:

Originally Posted by stonebridge46 I dont normally post, but I have had some experience with this in the past. For lapis, its not the ReqLevel field that determines its minimum level for linking. its the ReqInt field in the database. Set that to 30 for example, and the lapis will not be linkable into an item that is below level 30. I hope this helps

well i jut tested it. i have lvl 9 lapis at 31 to take one. and it's 31 in ReqInt. i just changed the lvl in item.sdata iported it back in. and i could link.

it's linked now and don't even change when i loggout or anything. i can relogg and i still have that gear on..

all mine lvl is in Int 3rt colum level is set as 1.

Look at the stats of your character in the database and compare them with the ones you see on screen.
They should be different.
Like I said you can change the sdata files to give you 10k to each stat and hit 30k yet the database has the true stats.

i linked lvl 9 lapis and some lvl 8 on a 15 toon. and only linked not even gave him stats he kicked ass and one hitted everything in 15 pvp world (mobs)

not sure how that would be diff in db that show it has lvl 9 and lvl 8 lapis linked..

what do you want me to look at? dbo.chars?

That's odd..lol