How to disable mouseover tooltips?

Forum where anything UOX3-related goes - including, but not limited to: newbie-support, ideas, general questions, comments, etc and-so-forth.
Post Reply
Fish
UOX3 Newbie
Posts: 14
Joined: Sun Feb 20, 2005 8:42 pm
Has thanked: 0
Been thanked: 0

How to disable mouseover tooltips?

Post by Fish »

Recently, the team of UOX3 added mouseover tooltips for item description with AOS clients.
I really do not like this feature. Arms Lore become useless, because of the "Durability" information about the item. Moreover, the interface become more complexe, less realist and less pleasant to use.

I searched from scripts and source, and I do not found where the feature was added.
I would like to know where is the file that contain the function, and eventually how to remove it.
Currently, the only way to disable this feature is to use older clients (< 3.0.8z), but I would like to use new clients.

Thank you.
Last edited by Fish on Mon Jun 13, 2005 10:14 am, edited 1 time in total.
giwo
Developer
Posts: 1780
Joined: Fri Jun 18, 2004 4:17 pm
Location: California
Has thanked: 0
Been thanked: 0

Post by giwo »

OSI Added this as a part of AoS. We simply added support for it in UOX.

Disabling it at this point would not be a simple task unless you wanted to disable ALL AoS features in the client. We are considering a good way to allow for toggleable client features in the future, though.
Scott
Fish
UOX3 Newbie
Posts: 14
Joined: Sun Feb 20, 2005 8:42 pm
Has thanked: 0
Been thanked: 0

Post by Fish »

How to disable all AOS features?
giwo
Developer
Posts: 1780
Joined: Fri Jun 18, 2004 4:17 pm
Location: California
Has thanked: 0
Been thanked: 0

Post by giwo »

I'll have to have a look when I get home, it's in one of the login packets, I believe. As simple as switching off a bit, but don't recall offhand exactly where to look.
Scott
giwo
Developer
Posts: 1780
Joined: Fri Jun 18, 2004 4:17 pm
Location: California
Has thanked: 0
Been thanked: 0

Post by giwo »

You would be wanting to find this:

CPacketSend.cpp around line 2320

Code: Select all

CPEnableClientFeatures::CPEnableClientFeatures()
{
//Enable locked client features (3 bytes) 
//·        BYTE cmd 
//·        BYTE[2] feature#
//Bit# 1 T2A upgrade, enables chatbutton, 
//Bit# 2 enables LBR update.  (of course LBR installation is required)
//(plays MP3 instead of midis, 2D LBR client shows new LBR monsters,…)
//Bit# 3: unknown, never seen it set
//Bit# 4: unknown, set on OSI servers that have AOS code - no matter of account status (doesn’t seem to “unlock/lock” anything on client side)
//Bit# 5: enables AOS update (necro/paladin skills for all clients, malas map/AOS monsters if AOS installation present)
//Bit# 15: since client 4.0 this bit has to be set, otherwise bits 3..14 are ignored.
//Thus 0: neither T2A NOR LBR, equal to not sending it at all, 
//1 is T2A, chatbutton, 
//2 is LBR without chatbutton, 
//3 is LBR with chatbutton…
//8013, LBR + chatbutton + AOS enabled
//Note1: this message is send immediately after login.
//Note2: on OSI  servers this controls features OSI enables/disables via “upgrade codes.”
//Note3: a 3 doesn’t seem to “hurt” older (NON LBR) clients.

	internalBuffer.resize( 3 );
	internalBuffer[0] = 0xB9;
#if defined( _MSC_VER )
#pragma todo( "Currently all client support is hardcoded. Move this into the ini when possible." )
#endif
	internalBuffer[1] = 0x80;		// 0x00
	internalBuffer[2] = 0x3F;		// New chars enabled(shh they prolly wont work) and Enable 6th slot
}
the internalBuffer[1] and internalBuffer[2] need to be changed based on what features you want enabled and/or disabled.
Scott
Post Reply