• 💀 Happy Halloween! 💀 It's time to vote for the best terrain! Check out the entries to Hive's HD Terrain Contest #2 - Vampire Folklore.❗️Poll closes on November 14, 2023. 🔗Click here to cast your vote!
  • 🏆 Texturing Contest #33 is OPEN! Contestants must re-texture a SD unit model found in-game (Warcraft 3 Classic), recreating the unit into a peaceful NPC version. 🔗Click here to enter!
  • 🏆 HD Level Design Contest #1 is OPEN! Contestants must create a maze with at least one entry point, and at least one exit point. The map should be made in HD mode, and should not be openable in SD. Only custom models from Hive's HD model and texture sections are allowed. The only exceptions are DNC models and omnilights. This is mainly a visual and design oriented contest, not technical. The UI and video walkthrough rules are there to give everyone an equal shot at victory by standardizing how viewers see the terrain. 🔗Click here to enter!

Request about resource overwrite

Status
Not open for further replies.
Hi there!

While seeing some footage of my campaign being played with Quenching Mod, I noticed that you are overwriting some of my custom models.
Specifically, if I import a custom model at a default path (I usually do this to expand on units animation) you overwrite my imported model, removing the animations I need.

My request is simple: is possible for you to avoid overwriting with your models my custom models when my custom models are imported at the default model path for that unit (for example, replacing the default grunt)?

Ideally, the import priority should be MAP -> QUENCHING -> BASE GAME and not QUENCHING -> MAP -> BASE GAME

Let me know ;)
 

Zorrot

Hosted Project: QM
Level 16
Joined
May 16, 2010
Messages
157
Hi there!

While seeing some footage of my campaign being played with Quenching Mod, I noticed that you are overwriting some of my custom models.
Specifically, if I import a custom model at a default path (I usually do this to expand on units animation) you overwrite my imported model, removing the animations I need.

My request is simple: is possible for you to avoid overwriting with your models my custom models when my custom models are imported at the default model path for that unit (for example, replacing the default grunt)?

Ideally, the import priority should be MAP -> QUENCHING -> BASE GAME and not QUENCHING -> MAP -> BASE GAME

Let me know ;)
Yes, in the newest version, unitskin, terrain, doodas is switchable and can be turn on/off
And we removed most of units replacment.
But the reading order is unchangeable for now, that's hardcoded in warcraft III game client
 
Status
Not open for further replies.
Top