Transmogrification is possible on 3.3.5?

[doresain]

a new feature of the patch 4.3 http://eu.battle.net/wow/en/blog/2808997#blog
it's possible to recreate this feature on mangos/trinity 3.3.5? i'm not a good coder

[schlumpf]

Seeing as the thing is not even released yet, there is no information about how they are doing it.

They most likely added a new uint32_t in the data sent for each item from the server containing the displayID. If this is sent, the client overwrites the display ID found in the dbcs.

This kind of modification needs client side changes, therefore is not possible easily with 3.3.5a.

[Eluo]

Wasnt there a spell that alters the look of an worn item?

[doresain]

if exist a spell that overrides a weapon/armor modelid in 3.3.5 we may create a similar spell for every modelid in the game. it' insane XD
i think doesn't exist somethink like this in 3.x, only auras that overrider player modelid (in old mangos and old client you can override player model with .set value command or set player mounted but nothing similar to weapon swap)

[doresain]

i remember an old item, the benedict/anatema staff, that has a spella that morph the item in his dual
http://www.wowhead.com/spell=23041
http://www.wowhead.com/spell=23042

spell swaps item, not modelid, but it's quite similar

[schlumpf]

This requires to have all otems with all possible display ids in the client. It's of course possible to have the same item with different models, but that requires client side editing and is not possible with server scripts alone.

[doresain]

not a good idea to make a n*(n-1) items and spells

[schlumpf]

It may be done for a subset of combinations or for donors.

[schlumpf]

Oh wait, ItemTemplate has a displayInfo field. Not sure if one can force to delete stuff from the cached item data by the server. Else the client will have the data cached and won't update the display. I'm also not sure, if this does actually force the client to use the sent Id. I guess it does not.

[doresain]

i found a tutorial to swap item models with an hack program, i think it works on the cache of the client
http://desertdarky.deviantart.com/art/W ... -145045198
on my server i had a patch that "overrides" players models, if modelid are sent by server to client we should modify this to work with itemmodelid i think
this is the patch (very simple)

Code: [Select]

  //PERSONALIZZAZIONE TALECRAFT PER UTILIZZARE LE RAZZE CUSTOM NON PRESENTI NEL GIOCO
   QueryResult CustomRaceResult = CharacterDatabase.PQuery("SELECT modelOverride FROM character_overrides WHERE guid = %u", fields[0].GetUInt32());

   if(CustomRaceResult)
      {
         Field *fields2 = CustomRaceResult->Fetch();
         SetNativeDisplayId(fields2[0].GetUInt32());
         SetDisplayId(fields2[0].GetUInt32());
      }
   else
      InitDisplayIds();

[schlumpf]

The problem is not sending a different display ID but if its actually regarded by the client and not overwritten via local DBC files. Also, the client caches the data, as you can see in that tutorial editing the cached data, and therefore it might not be easily possible for the server to force the client using a different display id while the client still has the old one cached.

[doresain]

yes, but if the player clears the cache of his client it should work, no? exists a lot of launchers that clear the cache of the client before the launch of wow.exe

[schlumpf]

That would mean after changing the display ingame, you would have to restart the client through the launcher. great gameplay you have there.

[doresain]

in 2.x i used .set data command to edit the playerbytes (skin face hair facial feature),after players logout, cancel cache files and login with new hairstyles, and were happy, after blizzard created the barber shop...
i think player doesn't become enraged if after logout and login has a new item skin

[schlumpf]

I'd say, that's horrible. I want the item to switch directly, not only as soon as all people who ever saw that item (that's why it might be not doable as well) deleted their cache.

The cache contains one entry per item id.  Also, WoW most likely does not handle a packet per item on every player but on every item it sees. This will result in changing the display on one item for everyone. I don't think  this is the wanted behaviour.