+- SphereCommunity (https://forum.spherecommunity.net)
+-- Forum: Sphere 0.56d (/Forum-Sphere-0-56d)
+--- Forum: General Help (/Forum-General-Help)
+--- Thread: EC basic support (/Thread-EC-basic-support)
EC basic support - karma - 01-12-2014 06:35 AM
Hi all, i'm giving a look to the Enhanced Client and found those issues:
1) Can't show names by single-clicking items or npcs. If i do .xMESSAGE *somewhat* to an equipped item it doesn't show *somewhat*, but in the system messages zone appears [itemname] *somewhat*.
If i enable AOS tooltips in sphere.ini they work, showing the name and other stuff, but that is not what i wanted, the feature above still lacks.
2) If i summon a monster, his name is shown only if i click him (which sets him also as target, as for the new EC targeting system). Name is shown only if i click him soon to his summoning and after a while it fades. Time before name fades is longer the sooner i click at the monster after his summoning.
If AOS tooltips are enabled, on spawn monster name appears and fades regularly, clicking on it don't show the name but upon passing the mouse the tooltip with the name shows, so the behaviour is correct.
This is to describe in depth the issue: monster names not showing (without AOS tooltips).
3) MESSAGE and SYSMESSAGE coloured texts don't work. Official shards have it, so i think is sphere that currently doesn't handle it (i'm using "SYSMESSAGE @color message" syntax, i think it isn't changed over time).
4) Monster status gump (that one with monster portrait and health) closes with ESC key, not by right-clicking it. Maybe it is a client issue, but i write it here anyway.
5) Equipping an item on ground results in equipping the item but leaving it on ground. If i move the item on ground to another tile, this unequips. If i unequip the item moving it in the backpack, that one on the ground disappears.
Thanks for the answers (and i hope for the support
)!
RE: EC basic support - Khaos - 01-13-2014 08:59 AM
1 and 2) EC is not the older client. I don't think fixing @Click would be ideal for it at the moment. Though it could be considered. I would assume this is more packet handling possibly and we would have to look into that. EC uses new packets that I believe CC does not. Really, EC would assume all clients are using AoS+ Tooltips anyway... I don't see the harm but it can be put on a list to look at and try to make it backwards compatible with older functionality.
3) Odd. Have you tried using messageloc and sysmessageloc and sysmessagelocex; etc?! Those could be a possible way to deal with color issues. You could just use a blank cliloc to parse the messages. Again, if this works; it would be something we would optionally fix.
4) Sounds about right when it comes to the client. We will look into it though.
5) I never suggest an equip with dclick; but that is me. Since some items can do other things via DClick. Which is what I am assuming you are doing in this case. Items generally should be equipped from a pack; though I see the reasoning you could argue with. Still test this without a dclick and just drag and drop and tell me if it is still an issue.
RE: EC basic support - karma - 01-14-2014 07:47 AM
Thanks for your reply Khaos, it makes me really happy seeing such a fast and kind support!
1) I have seen screens of a guy playing with EC (on a presumably official server, so with tooltips) and he could click on a corpse to show its name. Honestly i don't know if he uses an assistant because he was showing all corpses names, like on CC, so maybe tooltips were concomitantly enabled. I'm saying this because it may be helpful, never know. Anyway, many shards use old behaviour, it would be nice to have @Click fixed.
3) Nope, neither messageloc and sysmessageloc works. Messageloc does not show coloured text not even if used on a item placed on ground.
I noticed another issue: with AOS tooltips enabled items in backpack highlight in yellow correctly, but without tooltips this won't happen, items won't highlight.
5) Maybe you are right, but i prefer equipping with dclick, points of view
Anyway, dragging an item from ground to pack and then dclicking or dragging it on char works, tell me if i can help you with other tests.EDIT: dragging the item from ground to char works, it equips and removes item from ground.
Also skill-raise text is shown with a default, gray-white color, not the normal cyan one.
I think this http://ruosi.org/packetguide/index.xml is the most updated packet guide on the net, maybe it can be useful
RE: EC basic support - karma - 01-19-2014 07:28 AM
Time ago i have edited the post above with new infos.
Anyway, i found a new issue: when suiciding, screen doesn't fade to gray but remains coloured. I have seen videos of players dying on official servers, so this feature has been preserved, maybe it's just the packet that may have been changed.
EDIT: into Graphics settings there is an "enable hardware death effect" tick. Both enabled and disabled show the problem.
There is also, under Options tab, a "show names" entry, with "none", "approaching", "all" options. With AOS tooltips disabled:
- None: shows no names, always.
- Approaching: behaviour in first post.
- All: after clicking, name is shown and never disappears, even if clicking another monster (his name will be showed too). Item names still not shown after single-click.
Maybe fixing @Click is the way, and i bet "approaching" is the right option to obtain default behaviour.
RE: EC basic support - karma - 01-26-2014 11:53 PM
New infos:
"sayu hello", instead of showing "hello" on the char, shows a violet "hello" sysmessage.
EDIT:
found an interesting issue: neither EFFECT generates hued effects (only standard colour), so may the problem lie in the whole hues management?
Also, i tried these commands to do some experiments on player speech but i got anything:
sendpacket 03 W(10) 00 W(0130) W(00) 061 00
(tried with and without tailing 00 (null value, '\0' string terminator in C) in text char array; 061 is the hex ascii code for 'a')
Packet description:
Send ascii speech to the server.
byteID (03)
word Size of Packet
byte Mode (0x00 = say, 0x01 = system, 0x02 = emote, 0x06 = label, 0x07 = focus, 0x08 = whipser, 0x09 = yell, 0x10 = spell, 0x13 = guild, 0x14 = alliance, 0x15 = GM, 0x20 = special, 0xC0 = encoded commands)
word Text Color
word Font
char[*] Text
sendpacket 0ad W(13) 00 W(0123) W(01) 065 06e 075 00 065
Packet description:
Unicode Speech Packet.
byteID (AD)
word Packet Size
byte Mode (0x00 = say, 0x01 = system, 0x02 = emote, 0x06 = label, 0x07 = focus, 0x08 = whipser, 0x09 = yell, 0x10 = spell, 0x13 = guild, 0x14 = alliance, 0x15 = GM, 0xC0 = encoded commands)
word Text Color
word Font
char[4] Language
byte[*] Keywords (only if Mode == 0xC0)
uchar[*]Text
RE: EC basic support - Ben - 01-27-2014 12:57 AM
Of course you get nothing from those 2 packets, they are client --> server packets. Not the other way around.
RE: EC basic support - karma - 01-27-2014 01:00 AM
Ok, those were my first sendpacket tries, it seems i used the wrong packets and in general the wrong method, thanks
Are there any tries i can do to help you find out the problem(s)?
RE: EC basic support - karma - 02-13-2014 11:56 PM
Any news?
Only new thing i noticed: even equipping from ground an item with .xequip shows the same problem, which is not resolved by a .update
RE: EC basic support - karma - 03-16-2014 05:32 AM
I'm sorry to re-up the thread, but fixing those bugs is fundamental to make Enhanced Client playable.. At least, can you tell me if fixing them is possible, or you don't have time, need more elements, help, or so
RE: EC basic support - Ben - 03-16-2014 06:47 AM
"Fixing" the enhanced client is not as simple as a few tweaks... for a lot of things, the enhanced client uses new packets.
Supporting the entire classic client is, in my opinion, more important, and this is what we are working on.