• 🏆 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!
  • It's time for the first HD Modeling Contest of 2024. Join the theme discussion for Hive's HD Modeling Contest #6! Click here to post your idea!

Wc3 Image Viewer

This bundle is marked as useful / simple. Simplicity is bliss, low effort and/or may contain minor bugs.
Wc3 Image Viewer

During Wc3's development Blizzard had created a huge amount of content for the game but the map editor is very good at hiding it. This map tries to enable one to explore the icons/images (.blp files) part of that content. Because of the need to add a transparent 1 pixel border (in order for an image to be shown "properly" by the CreateImage native), the map needs to import the images, even though they are all stored in the game files.

PS: you can use the "cz <height>" to adjust the camera's height
Contents

Wc3 Image Viewer (Map)

Reviews
MyPad
This tool can help out a lot of users in finding out hidden game files within the main game. However, that reason alone is not sufficient for approval or update. For all intents and purposes, one which I have deduced, this would best suit the Lab as...
This tool can help out a lot of users in finding out hidden game files within the main game. However, that reason alone is not sufficient for approval or update.

For all intents and purposes, one which I have deduced, this would best suit the Lab as a finding or discovery, and not a resource.

This does not follow the following Spell Submission Rules:

  • Submissions must be made using vanilla GUI (aka triggers), JASS, vJASS, Zinc, or Wurst. Using other third party languages, including UMSWE GUI, or similar, is prohibited.
  • The documentation must at least contain a listing of the API, external library requirements and importing instructions.
  • Systems must be as instance-able as possible (instance-ability will often depend on the type of system).
  • [...] Concepts that do not have a clear purpose, or are extremely simple might be rejected. [...]

The reasons behind the following rules being broken are stated herein

  • uses cJASS
  • No API listed (Only Multiboard is listed)
  • No API -> ambiguous instance-ability traits
  • Concept behind the resource does not fit the properties of a resource.


Status:

  • Substandard
 
Last edited:
Top