if you open the newest wowmodelviewer and go to 2handed swords, there should be a sword called demonblade, if ANYONE could get me that display ID or the additem id, i will +rep if i can!
if you open the newest wowmodelviewer and go to 2handed swords, there should be a sword called demonblade, if ANYONE could get me that display ID or the additem id, i will +rep if i can!
orly? ya rly,
NO WAI!
Display ID = 20299
Is that the one?
ill check tomorrow, if you saw the noggaholic vid its that huge one that he was usin on his rogue with BF armor, its absolutely HUGE
im goin to bed, ill check if thats the one tomorrow
orly? ya rly,
NO WAI!
I found a pretty useful way to get item display IDs, in SQLyog (the same thing you use to make and manage accts.) go to the items table (which is under your server, mine's Antrix) then click show all and it will lag a sec, give it a few moments to load all the data. Next sort by name (alphabetical order), scroll down to the D section and find Demonblade, then scroll (right if you're not used to navigating these), and look for the column named display ID (column names are at the top of the display) and there's your ID.
I often look things up in model viewer then look up their ID this way. Had worked fantastically for me.
And your weapon in question's ID is 20299 I believe.
if anything is unclear let me know, dunno if it's different in navicat as I have no experience with that.
new server, and that isnt the item, thats a lil tiny dagger, in the noggaholic movie, the undead rogue while he was running through caverns of time, i saw that model
Last edited by Spritemaster300; 10-15-2007 at 06:17 PM.
orly? ya rly,
NO WAI!
heres a pic of the unskinned model:
![]()
orly? ya rly,
NO WAI!
well, ionno about any of that, lol, but if you could make a display id for it (ionno how) i will love you in a non gay way
orly? ya rly,
NO WAI!
Thats what i was trying to do. You can create your own Display Id's by adding new lines into ItemDisplayInfo.dbc, but when you enter the game. Wow gives you an error. the only way to fix it is to use a ME fix. Which there currently isnt one for 2.2.3 :<