Changes: Blood-Caked Blade

Revision as of 22:12, 12 February 2011

Retrieve info about network statistics.

bandwidthIn, bandwidthOut, latencyHome, latencyWorld = GetNetStats();

Returns

bandwidthIn: Current incoming bandwidth (download) usage, measured in KB/s.
bandwidthOut: Current outgoing bandwidth (upload) usage, measured in KB/s.
latencyHome: Average roundtrip latency to the home realm server (only updated every 30 seconds).
latencyWorld: Average roundtrip latency to the current world server (only updated every 30 seconds).

Example

local down, up, lagHome, lagWorld = GetNetStats();

message("LagWorld: "..lagWorld.." milliseconds.");

Result

Message box appears with amount of world latency in milliseconds.

Patches

Patch 4.0.6 (2011-02-08): Now returns both home and world latency, instead of just world latency.

Details

Home/World latency (updated) - 4.0.6 | 2011-02-11 19:54 | Gelmkar

In essence, Home refers to your connection to your realm server. This connection sends chat data, auction house stuff, guild chat and info, some addon data, and various other data. It is a pretty slim connection in terms of bandwidth requirements.

World is a reference to the connection to our servers that transmits all the other data... combat, data from the people around you (specs, gear, enchants, etc.), NPCs, mobs, casting, professions, etc. Going into a highly populated zone (like a capital city) will drastically increase the amount of data being sent over this connection and will raise the reported latency.

Prior to 4.0.6, the in-game latency monitor only showed 'World' latency, which caused a lot of confusion for people who had no lag while chatting, but couldn't cast or interact with NPCs and ended up getting kicked offline. We hoped that including the latency meters for both connections would assist in clarifying this for everyone.

As is probably obvious based upon this information, the two connections are not used equally. There is a much larger amount of data being sent over the World connection, which is a good reason you may see disparities between the two times. If there is a large chunk of data 'queued' up on the server and waiting to be sent to your client, that 'ping' to the server is going to have to wait its turn in line, and the actual number returned will be much higher than the 'Home' connection.

View original post

@@ Line 1: / Line 1: @@
+__NOTOC__
-{{deathknight}}
+{{wowapi}}
+Retrieve info about network statistics.
-{{Infobox talent
-|name=Blood-Caked Blade
-|image=Ability_CriticalStrike.png
-|description=Your autoattacks have a X% chance to cause a Blood-Caked Strike, which hits for 60% weapon damage times the number of your diseases on the target.
-|class=Death knight
-|location=Unholy, Tier 4
-|affects=Melee attacks
-|ranks=3
-|talent_req=None
-|points_req=15
-|buff_name=Blood-Caked Strike
-|buff_image=Ability_Creature_Poison_01.png
-|buff_type=
-|buff_desc=Randomly strikes the enemy, causing 60% weapon damage times the number of the death knight's diseases on the target.
-}}
+ bandwidthIn, bandwidthOut, latencyHome, latencyWorld = GetNetStats();
-'''Blood-Caked Blade''' is a [[Death knight]] talent located in the 4th tier of the [[Death knight talents#Unholy|Unholy Tree]].
-== Rank table ==
+== Returns ==
+:;bandwidthIn : Current incoming bandwidth (download) usage, measured in KB/s.
-{| class="darktable" style="text-align: center;"
+:;bandwidthOut : Current outgoing bandwidth (upload) usage, measured in KB/s.
-|-
+:;latencyHome : Average roundtrip latency to the home realm server (only updated every 30 seconds).
-! Rank !! % Increase
+:;latencyWorld : Average roundtrip latency to the current world server (only updated every 30 seconds).
-|-
-| 1 || 5
-|-class="alt"
-| 2 || 10
-|-
-| 3 || 15
-|}
+== Example ==
+ local down, up, lagHome, lagWorld = GetNetStats();<br>
+ message("LagWorld: "..lagWorld.." milliseconds.");
+<big>'''Result'''</big>
-{{classfooter|Death knight}}
+Message box appears with amount of world latency in milliseconds.
-[[Category:Death knight talents]]
+==Patches==
+* {{patch 4.0.6|note=Now returns both home and world latency, instead of just world latency.}}
+==Details==
+{{Bluepost|poster=Gelmkar|title=Home/World latency (updated) - 4.0.6|date= 02/11/2011 7:54:23 PM UTC|link=http://eu.battle.net/wow/en/forum/topic/1710231176|body=
+In essence, <u>Home</u> refers to your connection to your realm server. This connection sends chat data, auction house stuff, guild chat and info, some addon data, and various other data. It is a pretty slim connection in terms of bandwidth requirements.<br/><br/>
+<u>World</u> is a reference to the connection to our servers that transmits all the other data... combat, data from the people around you (specs, gear, enchants, etc.), NPCs, mobs, casting, professions, etc. Going into a highly populated zone (like a capital city) will drastically increase the amount of data being sent over this connection and will raise the reported latency.<br/><br/>
+Prior to 4.0.6, the in-game latency monitor only showed 'World' latency, which caused a lot of confusion for people who had no lag while chatting, but couldn't cast or interact with NPCs and ended up getting kicked offline. We hoped that including the latency meters for both connections would assist in clarifying this for everyone.<br/><br/>
+As is probably obvious based upon this information, the two connections are not used equally. There is a much larger amount of data being sent over the World connection, which is a good reason you may see disparities between the two times. If there is a large chunk of data 'queued' up on the server and waiting to be sent to your client, that 'ping' to the server is going to have to wait its turn in line, and the actual number returned will be much higher than the 'Home' connection.}}