Jump to content

Chucksta

getMaNGOS Retired Staff
  • Posts

    552
  • Joined

  • Last visited

  • Days Won

    1
  • Donations

    0.00 GBP 

Everything posted by Chucksta

  1. [B][SIZE=4]THIS IS FIXED IN WOTLK (fix author: XENITHAR - for all releases)[/SIZE][/B] I logged onto Solar Flare, and the Taurens were the correct height :-) Presumably, what was done there, can be done for Zero :D
  2. Bluffwatcher NPCs in TB are also affected by this issue. All are at scale 1.35, no matter the gender. Creature_template table Entry: 3084 Name: Bluffwatcher ------------------------------------- I think there may be an issue with the way the modelid's are used/assigned/associated. There are 2 model IDs per race, as far as Horde Guard is concerned (not checked Bluffwatcher, yet). I reckon they should be associated with gender, but right now both genders use both model IDs. 2 model IDs, 2 genders, makes sense that have a 1 to 1 association, but I could be wrong. e.g. I noticed that with the modelid (in the creature table) set to 4262 (Tauren model) for one of the Horde Guard, would sometimes be male and sometimes female (very 21st century). It looks like the modelid1 and modelid2 fields in the creature_template table has no baring on what model is actually put into the world. This table's records do have the scale field that is in use when placing the NPCs in the world. So, so far, as far as I can see, we need: 2 more records for the Horde Guard, one for male Tauren, and one for female Tauren, thus giving us 3 Horde Guard records in the creature_template table. - the original table can be used for all other races, as all others are of the same scale 1 more record for the Bluffwatcher, that being for the female Tauren. The original would be used for the male Tauren. Then, of course, update the records in the creature table to reflect this change, so that the Taurens are correctly scaled. ------------- So far I have create and tested SQL scripts to generate the required tables for the Horde Guard issue, so will continue with that. I'll post them here once I have done and tested everything that will be required to fix this issue. Not sure about the [B]gender thing[/B], though. That [B]could be the difference between requiring extra table entries or not[/B]. I probably ought to check the program code that is involved in placing these NPCs into the world. -------------- [B]EDIT:[/B] Eek! the system picks at random the gender of the model to display, so the previous idea for a fix would not work (on its own). I need to find out how the gender choice is occurring... searchy, searchy, searchy ... learny, learny, learny :D - or go insane :P
  3. I've just joined Coveanant-WoW, and created a toon (Bowjob, the Tauren Hunter) on Cosmic Ray (Vanilla WoW). Checking out Camp Taurajo and the scale of the Tauren models issue is there, so no fix applied on that server, as yet. The only fix I can think to do, is to create 2 more Horde Guard database entries. One for the Tauren males (scale 1.35) and one for the Tauren females (scale 1.25), seeing as their scale is the only ones that are unique to the others. The current database entry (creature_template id 3501) can be used for all other models (scale 0). There does not appear to be a way to identify a model's gender (my meagre knowledge of the database), otherwise this could be done with one database entry and program code. For a while, I thought the gender could be found by the modelid, but it turns out the genders for each race share the modelid's, going by what I have seen in the database.
  4. Horde Guard coordinates place it in the void - not in the game world FIX - See proposed fix just above the images MaNGOS: Zero CORE: Rel20 DATABASE: Rel20 DETAILS OF ISSUE The coordinates of one of the Horde Guards, places it outside of the game world. I teleported to its coordinates and found my toon in Nowhere Land, a void, outside of the world. After a short while my toon was sent to the graveyard. To locate where this guard should go: - I sorted the Horde Guards (listing generated by Horde Guard ID 3501 on the mangos.creature table) into numeric order based on the X coordinate, then seeing the coordinates of the closest Horde Guards in the list, and that their X and Y coordinates were VERY close, I then teleported to one of them, and landed my toon in Camp Taurajo. - I then acquired a Z coordinate there, and changed the lost Horde Guard's Z coord to that value. - Restarting the database and game server, I found the (ex) lost Horde Guard outside of the Inn. Some way towards the back, right hand side as you look at the Inn. Looking online for for images of the Camp Taurajo Inn, it looks like the guard should be positioned on right hand side and closer to the front, although it's hard to tell from those images, and it's hard to tell if what I see is even an NPC. Looking at other buildings in Camp Taurajo, they all have 2 Horde Guards either side of the building or its main entrance, so I reckon it's safe to say our AWOL Horde Guard should do the same, and be positioned on the right side of the building as you face it (SEE BELOW IMAGES). Or you could just changed the Z coord, as I did originally, but the NPC does look a little out of place. Current Coordinates (nowhere bound, or say hello to the void): X: -2517.043946 Y: -1972.524902 Z: 91.783798 Recommended Coordinates X: -2376.782227 Y: 1962.498413 Z: 96.087646 SQL Script Fix (this will place our AWOL Horde Guard back on guard duty) UPDATE creature SET position_x = -2376.782227, position_y = -1962.498413, position_z = 96.087646, orientation = 0.773024 WHERE guid = 19382; [IMG]http://chuckyworld.co.uk/MaNGOS/Issues/Database/HordeGuardOnBioBreak/HordeGuardBiobreak.jpg[/IMG] [IMG]http://chuckyworld.co.uk/MaNGOS/Issues/Database/HordeGuardOnBioBreak/HordeHuardBackFromBio.jpg[/IMG]
  5. Yep, he's right. 3 that I can see, one of which is patrolling. They appear to be set to the same height as the Orcs. I'll see if I can make this my first fix :-) EDIT: The database entry for the "Horde Guard" (ID 3501 - Entry field) is used for both the Orcs and the Taurens, at least, as proven by the following image, where I changed the Scale field from 0 to 10: [IMG]http://s27.postimg.org/qojegbfkz/Giant_Tauren.jpg[/IMG]
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use