Sentinel's Fate Client Bump

[ZexisStryfe]

The update is tomorrow but I figured I would pre-empt it-

Usual request after a new Game Update/Expansion...

client bump!

This is a big one with Sentinel's Fate being released tomorrow. It is going to give us access to tons of new zones and models. As battlegrounds!

[John Adams]

Recommend backing up your current client, since LE is too busy to bump the client support immediately, if this is anything bigger than Zcoretri or I can handle.

[ZexisStryfe]

La lalala la la...

[l333]

+1

[John Adams]

Sorry guys, but unless you can disassemble the client and map all the opcodes that have changed during this major upgrade, you're just going to have to wait til we figure it out. There is no LE to whip out an expansion in an afternoon, and the process was never documented.

Nothing we can do.

[ZexisStryfe]

I thought Secrets posted all that info...

Shows what I know.

[Zcoretri]

At this point opcodes are fine, I pretty much have them figured them out. I have logged in to my own local server with SF client, but there are still issues in regards to structs that need to be addressed.
I think I've got the character sheet figured out, gonna start work on the quest structs now. I was gonna do item structs, but then realized why I stopped work on them in the first place.

The item struct is really gonna be the key for the new client. I will try to explain the problem.
With the new items, SoE has consolidated a lot of the 'Blue Stats'...along with that, they made the values of the blue stats floats, but here's the rub, and the current problem. Here is the current stat array...

Code: Select all

<Data ElementName="stat_count" Type="int8" />
<Data ElementName="stat_array" Type="Array" ArraySizeVariable="stat_count">
	<Data ElementName="stat_type" Type="int16" OversizedValue="127" OversizedByte="127" Size="1" />
	<Data ElementName="stat_subtype" Type="sint16" OversizedValue="127" OversizedByte="127" Size="1" />
	<Data ElementName="value" Type="sint16" OversizedValue="127" OversizedByte="127" Size="1" />
	<Data ElementName="stat_name" Type="EQ2_8Bit_String" Size="1" />
</Data>

The way this currently works is, if the value for the element starts with 7F, then the value is 2 bytes (int16) otherwise it's 1 byte (int8)
The problem now is, if "stat_type" = 6, then the "value" element needs to be a 4 bytes (float).

[ZexisStryfe]

I have no idea what you are talking about, but I have faith in you!

[John Adams]

Opcodes, structs, floats, green monkeys. It all reads the same to me.