How about on titles?

So_1337 · #1 01-23-2008, 04:44 AM

How can the 'blob' data in profile be read and/or edited? I'm wishing I had the knowledge to work on this, as I'd love to see it happen.

**AndMetal** · #2 01-23-2008, 07:10 AM

Here is how I read it using PHP: Convert profile blob to useful data (Wiki).

A more up-to-date version of this can be found on Sourceforge: profile & functions. The same idea (substr()) can be used in pretty much any computer language.

Putting it back is basically the reverse, by putting all of the data back into one lump, then updating it into the database.

I haven't tried this yet, although I did create a PHP utility to directly view the contents of the blob (not on Sourceforge yet, but will eventually be located here) with the intent of eventually being able to edit it directly from the same utility (like a hex editor), then moving to a more user friendly interface. My only concern about updating directly into the profile is that there is a Checksum field at the very beginning, and I'm not sure if it would cause any problems if you do modify it.

The hard work of breaking down what's where has been done, so all of the information you need should be there. From there, you'll just need to figure out the best way to inject the changes.

Arex · #3 01-30-2008, 08:41 PM

perhaps it is more difficult that i thought and we will have to wait years before to see AA titles in eqemu

**AndMetal** · #4 01-30-2008, 10:13 PM

Something else to contribute...

I found this in the Wiki: $client->SetAATitle(txt).

When I executed it in a quest:

Code:

sub EVENT_SAY {
	if ($text=~/aa title/i) {
		my $aatitle = "Baron";
		quest::say("Setting AA Title to $aatitle.");
		$client->SetAATitle("$aatitle");
		quest::say("AA Title set to $aatitle.");
	}
}

It went through the script ok, but I didn't see the title on the client, even after relogging. However, when I checked the profile blob, it did set title field to "Baron":

Code:

02384 42 61 72 6F 6E 00 00 00 00 00 00 00 00 00 00 00 B a r o n

So, it looks like the code is even there to set the title, but it isn't being sent to the client, or the client isn't seeing it.

Arex · #5 02-04-2008, 03:30 AM

it is nice to see any advancement, perhaps we need to do any opcodes research??

**TheLieka** · #6 02-04-2008, 09:55 AM

client_packet.cpp

Code:

void Client::Handle_OP_SetTitle(const EQApplicationPacket *app) {
//	m_pp.title[0] = '\0';
	//TODO: send some sort of update struct to everybody.
}

void Client::Handle_OP_RequestTitles(const EQApplicationPacket *app) {
	//zero length request
	//TODO: get the titles from somewhere, and ship em off
	
}

and

titles.cpp

Code:

TitleManager::TitleManager() {
}

I don't think the server's side is done. I'm more of a code tweaker, I don't have a clue where to start with something like this. Also when you open your titles window you get

Code:

[Debug] Unable to convert EQ opcode 0x5eba to an Application opcode.
[Debug] [CLIENT__NET_ERR] Death: Unhandled incoming opcode: [OpCode OP_Unknown (
0x5eba) Size=0]

Dax

**TheLieka** · #7 02-04-2008, 10:04 AM

To clarify: that's the current code that's in place - I didn't write any of it.

According to the comments in the code, you're supposed to use this table for the merit based titles.

Code:

create table titles (
	id int UNSIGNED primary key AUTO_INCREMENT,
	skill_id tinyint UNSIGNED NOT NULL,
	skill_value mediumint UNSIGNED NOT NULL,
	aa_points TINYINT UNSIGNED NOT NULL,
	title varchar(32) NOT NULL
);

Dax