此站点大量使用JavaScript。
请在您的浏览器中启用JavaScript。
正式服
PTR
小知识
屏幕截图
视频
评论
评论来自
haveeatenyourgra
it can repair?
评论来自
328729
Dam murlocs, with a spy on Kirin tor and top shoulder enchants is not surprise they can one shot a 1 lvl player
评论来自
icritmypants
This is bad. Murlocs that can sell rep items? I can just see killing your own faction to farm rep. The horror! (Ignore this if your actually looking for somthing that has a point)
评论来自
336831
Apparently he is skinnable and drops northrend level skins.
评论来自
devilboy1324
I smell private server interaction
评论来自
Velasco
The problem with this little fella is due to a change of the GUID string, which was implemented with 3.3
2 Hex-Code Digits were shifted in this change and as Wowhead didn't adapt to that change yet the Murloc Tidehunter currently incorporates Unit IDs of several Northrend Mobs including Vendors.
For those who are interested how this happened read on:
First a little background information, which I have taken from
WoWWiki
A GUID can be thought of as being composed of multiple pieces of data. Consider "
0xAABCCCDDDDEEEEEE
", where:
AA
unknown.
B
unit type, mask with 0x7 to get: 0 for players, 1 for world objects, 3 for NPCs, 4 for pets, 5 for vehicles.
CCC
If the unit is a pet, CCCDDDD forms a unique ID for the pet based on creation order; if a world object, CCCDDDD is the object ID; otherwise unknown.
DDDD
If the unit is an NPC, this is the hexadecimal representation of the NPC id.
EEEEEEE
If the unit is a player, this is a unique identifier based on creation order. Otherwise, this is a spawn counter based on spawn order.
Now based on that let's analyze our little murloc friend here.
His decimal ID is 127 (look at the URL). When we convert that to HEX Code it is 0x7F
128 would be 0x80 (I'll come to that later)
The whole GUID would be 0xF130
00
007F
000001
With the change in 3.3 the GUID now looks like 0xF130
007F
00
000001
The IDs of all NPCs
remain
the same, the Hex digits were merely shifted to the left by two.
If we now take this new GUID post-3.3 and would apply the pre-3.3 rule there would be an entire different NPC we would be looking at.
But how do we explain that Wohead lists this murloc with more items than any single mob would ever carry or sell?
Well this can be explained with the two trailing
0
after 0x7F, which haven't been there before the API change, so they are undefined.
I mentioned 128 above. This would be the next NPC ID (even though there is no NPC defined) in Decimal format. The Hex format 0x80 now also has two trailing
0
, due to the new system.
So in order to get from 0x7F
00
to 0x80
00
, every mob, every vendor etc. inbetween is allocated to the murloc.
Check those links:
List of affected mobs (and thus their spells)
List of affected vendors
评论来自
guisadop
looks like wowhead fixed it
评论来自
Ionite
Murloc Tidehunter used Splash!
But it failed!
3D查看
链接
潮行鱼人
这个 NPC 能在这些地区找到:
西部荒野
(15).
相关
贡献
在发表评论前,请留心以下提示:
您的评论必须为简体中文,否则将会被删除。
不知道如何发评论?参考我们的
格式指南
!
发表前最好先自行校对一次。
有问题可以访问我们的
论坛
来寻求帮助。
发表评论
你没有登录。
请登录
或者
注册账号
来添加你的评论。
使用下面的表格浏览您的截屏。
[Screenshots containing UI elements are generally declined on sight, the same goes for screenshots from the modelviewer or character selection screen.]
质量越高越好!
[Please review our
Screenshot Guidelines
before submitting!]
您没有登录。请
登录
后提交截屏。
将视频URL输入下列表格即可。
URL:
支持:仅限 YouTube
说明:您的视频需通过审核才能在站点上显示。
我们用
Wowhead 客户端
保证数据库的及时更新,向您提供额外的有趣的功能!
两大目的:
它还维护WoW的一个插件
Wowhead Looter
, 在您游戏时采集数据!
它将
采集所得数据
上传至Wowhead,保证数据库时刻掌握最新信息!
您可以用它追踪完成的任务、配方、坐骑、伙伴宠物以及头衔!
您还在等什么?立即
下载客户端
整装待发吧。
我们用 Wowhead 客户端保证数据库的及时更新,向您提供额外的有趣的功能!
两大目的:
您可以用它追踪完成的任务、配方、坐骑、伙伴宠物以及头衔!
您还在等什么?立即 下载客户端 整装待发吧。