Traits/Achievements Info

[John Adams]

Something I just noticed, when you first mouse-over some of these achievements, it's like a secondary query is being run before displaying the final achievement info. I barely caught it, but thought it might be worth mentioning for when we get to implementing these suckers.

First split second of the mouse over:

popping.jpg

After a second, the final data:

popped.jpg

Maybe all ability mouse-overs do this, and I have just never noticed?


Also, here is a difference in what is displayed in the mouse-over vs the Examine in this case, specifically layout, ranks, and requirements:

more-data.jpg

And finally, when an achievement has a current point assigned, and another point that _could be_ assigned, the examine behaves differently by popping the current + next rank at the same time:

dual-examines.jpg

[ZexisStryfe]

Hey John,

This does not only occur on traits/achievements but on all tooltips (spells, armor etc). You only really notice it on those things that have quite afew functions however. the Traits/achievements just seem slower to populate than the others.

[John Adams]

Ahh ok, then we must just me more efficient in our data presentation

Thanks

[JCL]

Spells, achievements, etc do. Like when your stats change (such as intelligence), damage will update to reflect that.

[John Adams]

Hmm? This I have never seen in any of the data. So you are telling me that an App1 spell that does 5-10 damage, I increase my intelligence, and now that same App1 will do 6-11?

[Zcoretri]

Hmm? This I have never seen in any of the data. So you are telling me that an App1 spell that does 5-10 damage, I increase my intelligence, and now that same App1 will do 6-11?

Yep, damage values increase.

I know what you mean, I have been looking for this myself.

I know for a fact that when I remove/add heal mod gear on my templar, I can see the heal range dynamically change when you examine the spell.

The packets I have been looking at do have 2 sets of values, I'll dig one up to show.

[John Adams]

As long as we know the base values, and that is what we're plugging into our spells data, I think we'll be ok.

I am not sure of World currently considers stats when determining spell examine displays - or cast effects even. LE may have to answer to that. If not, just another thing to add to the list.

[Zcoretri]

An example of what I was describing...

Code: Select all

-- OP_ClientCmdMsg::OP_EqInstructionWindowGoalCmd --
2/19/2009 10:51:13
199.108.13.72 -> 192.168.0.100
0000:	01 37 EA 01 00 00 FF 29 02 01 00 00 00 FE 25 83 .7.....)......%.
0010:	E6 5C 2A 0D 14 01 FF FF 39 01 EC 01 A8 01 02 00 .\*.....9.......
0020:	00 00 00 00 00 00 00 00 03 00 00 00 00 01 00 00 ................
0030:	6C 00 00 00 7F A9 00 32 00 00 F0 42 00 00 20 41 l......2...B.. A
0040:	04 00 00 00 01 00 3B 00 49 6E 66 6C 69 63 74 73 ......;.Inflicts
0050:	20 34 36 37 20 2D 20 36 37 32 20 68 65 61 74 20  467 - 672 heat 
0060:	64 61 6D 61 67 65 20 6F 6E 20 74 61 72 67 65 74 damage on target
0070:	73 20 69 6E 20 41 72 65 61 20 6F 66 20 45 66 66 s in Area of Eff
0080:	65 63 74 64 00 00 00 00 00 00 00 20 41 00 00 00 ectd....... A...
0090:	00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C2 ................
00A0:	F5 28 3F 00 00 00 00 00 00 00 00 00 00 00 0B 46 .(?............F
00B0:	6F 72 65 73 74 20 46 69 72 65 44 00 54 68 65 20 orest FireD.The 
00C0:	77 6F 6F 64 20 65 6C 66 20 65 6E 76 65 6C 6F 70 wood elf envelop
00D0:	73 20 74 68 65 69 72 20 73 75 72 72 6F 75 6E 64 s their surround
00E0:	69 6E 67 20 65 6E 65 6D 69 65 73 20 69 6E 20 61 ing enemies in a
00F0:	20 77 61 76 65 20 6F 66 20 66 6C 61 6D 65 73 2E  wave of flames.
0100:	E6 5C 2A 0D 14 01 FF FF 39 01 EC 01 A8 01 02 00 .\*.....9.......
0110:	00 00 00 00 00 00 00 00 03 00 00 00 00 01 00 00 ................
0120:	6C 00 00 00 7F A9 00 32 00 00 F0 42 00 00 20 41 l......2...B.. A
0130:	04 00 00 00 01 00 3B 00 49 6E 66 6C 69 63 74 73 ......;.Inflicts
0140:	20 34 32 30 20 2D 20 36 30 35 20 68 65 61 74 20  420 - 605 heat 
0150:	64 61 6D 61 67 65 20 6F 6E 20 74 61 72 67 65 74 damage on target
0160:	73 20 69 6E 20 41 72 65 61 20 6F 66 20 45 66 66 s in Area of Eff
0170:	65 63 74 64 00 00 00 00 00 00 00 20 41 00 00 00 ectd....... A...
0180:	00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C2 ................
0190:	F5 28 3F 00 00 00 00 00 00 00 00 00 00 00 0B 46 .(?............F
01A0:	6F 72 65 73 74 20 46 69 72 65 44 00 54 68 65 20 orest FireD.The 
01B0:	77 6F 6F 64 20 65 6C 66 20 65 6E 76 65 6C 6F 70 wood elf envelop
01C0:	73 20 74 68 65 69 72 20 73 75 72 72 6F 75 6E 64 s their surround
01D0:	69 6E 67 20 65 6E 65 6D 69 65 73 20 69 6E 20 61 ing enemies in a
01E0:	20 77 61 76 65 20 6F 66 20 66 6C 61 6D 65 73 2E  wave of flames.

[John Adams]

Ahh! My mistake. We have seen that in the data, I just didn't understand it til now. Odd that I would never have noticed that on my character(s), though my chars are fairly gimpy.

So the second set of stats is the "base", would you think? First being "current"?

[Zcoretri]

That's what I'm thinking. I might run some tests this weekend and try to figure it out.

[LethalEncounter]

The last set is likely the base while the first set is probably generated by the server based on your character's stats. Unfortunately for both the development and the content team this makes it much harder whenever it is fully implemented.