Anything missing is probably garbage or padding. Though, if it's truly important, just parse an item you know the stats of, read every offset, and name the offsets that match certain values accordingly. That's how I learned to parse the magictype for 4xxx.
Anything missing is probably garbage or padding. Though, if it's truly important, just parse an item you know the stats of, read every offset, and name the offsets that match certain values accordingly. That's how I learned to parse the magictype for 4xxx.
well that will work with StaminaUse,ManaUse etc because inside the client it says how much it uses etc , but there is some values the client does not give any info about it , so I cant compare it with magictype.dat, that's why I asked if anyone got it.
well that will work with StaminaUse,ManaUse etc because inside the client it says how much it uses etc , but there is some values the client does not give any info about it , so I cant compare it with magictype.dat, that's why I asked if anyone got it.
True. But, as you loop through items and go from level to level (i.e. from level 1 ring to level 10 ring, to level 20, etc) you can easily figure out what the values correspond to.
True. But, as you loop through items and go from level to level (i.e. from level 1 ring to level 10 ring, to level 20, etc) you can easily figure out what the values correspond to.
How to structure your attack handler proper. 05/27/2011 - CO2 PServer Guides & Releases - 9 Replies Note: There is no calculations or codes really, but more a good way to structure your attack handler, so it's easy to edit in the future or add new things.
Note 2: It's the way I would do it, maybe you like to it do it different.
Note 3: It's all pseudo.
Let's say you have your main attack handler.
public static void Attack(Client client)
{
SQL-DB structure 05/29/2010 - Silkroad Online - 0 Replies Hey folks,
does anyone happen to have the structure of the official SRO SQL-DB? I need no more than the column names and their associated table names (usually located in the DB "INFORMATION_SCHEMA").
