1. Are you planning to upload your awesome tool to Hive? Please review the rules here.
    July 9, 2018: The rules for the Tool Section have been revised. Please be sure to read the revisions.
    Dismiss Notice
  2. Updated Resource Submission Rules: All model & skin resource submissions must now include an in-game screenshot. This is to help speed up the moderation process and to show how the model and/or texture looks like from the in-game camera.
    Dismiss Notice
  3. DID YOU KNOW - That you can unlock new rank icons by posting on the forums or winning contests? Click here to customize your rank or read our User Rank Policy to see a list of ranks that you can unlock. Have you won a contest and still havn't received your rank award? Then please contact the administration.
    Dismiss Notice
  4. The Lich King demands your service! We've reached the 19th edition of the Icon Contest. Come along and make some chilling servants for the one true king.
    Dismiss Notice
  5. The 4th SFX Contest has started. Be sure to participate and have a fun factor in it.
    Dismiss Notice
  6. The poll for the 21st Terraining Contest is LIVE. Be sure to check out the entries and vote for one.
    Dismiss Notice
  7. The results are out! Check them out.
    Dismiss Notice
  8. Don’t forget to sign up for the Hive Cup. There’s a 555 EUR prize pool. Sign up now!
    Dismiss Notice
  9. The Hive Workshop Cup contest results have been announced! See the maps that'll be featured in the Hive Workshop Cup tournament!
    Dismiss Notice
  10. Check out the Staff job openings thread.
    Dismiss Notice
Dismiss Notice
60,000 passwords have been reset on July 8, 2019. If you cannot login, read this.

HiveWE - World Editor 0.6

Submitted by eejin
This bundle is marked as approved. It works and satisfies the submission rules.
HiveWE is a fully custom 3rd party world editor. It's completely separate from the original editor and is open-source!

Features:
  • Open and view Warcraft III maps.
  • Edit the terrain.
  • Edit the pathing map directly!
  • Change the tileset to up to 16 tiles.
  • Fly around in first or third person camera
  • Manage your imports with folders
  • Edit global tile pathing
  • Place and remove doodads
  • Edit map loading screen information
  • Import heightmaps
  • View GUI and edit JASS triggers
Limitations
  • Doodad rendering is not 100% accurate (teamglow, billboards, etc)
  • Does not show animations
Required for running HiveWE:

HiveWE 0.6

Additions
- Map script generation!
- Improved Jass highlighting
- Improved Jass autocomplete
- Tabs in the trigger editor now configurable
- Trigger comments shown and editable
- Rudimentary find window in trigger editor
- Move camera with arrow keys
- Shortcuts for opening/saving maps
- Improved doodad pathing placement
- Cool application icon
- Doodad copy and paste
- Doodad positioning with numpad
- Improved themes

Changes
- Camera is now a trackball type instead of TP/FP hybrid
- Camera drag now proportional to distance
- Camera now changes with terrain height
- Doodads height after terrain change now interpolated
- Doodads now selected with one click instead of two

Fixes
- Clicking on minimap now moves you to the correct location

HiveWE 0.5
Additions
- Minimap
- Full undo/redo for terrain/pathing/doodads
- Show destructibles pathing
- Visiblity/Solidity flags for doodads
- Pathing map preview for doodads
- Cliff lighting
- A functioning JASS editor (with some limitations)
- Dark theme
- Doodad palette functionality
Changes
- Check for empty warcraft directory path
- Default doodad palette to Trees/Destructibles
- Tries to run on the fastest GPU
- Now also shows RoC (.w3m) maps in the open map dialog
Fixes
- Can now launch HiveWE while Warcraft is running
- Deep water for terrain palette has proper height
- properly applies water pathing

HiveWE 0.4
Additions
- Warcraft 1.30 support!
- Full BLP1 support
- Loads the shadowmap file (implementation waiting)
- Import a heightmap (PNG, TGA, JPG and many others)
- Load and edit map information! (loading screen/description)
- Trigger viewer! View GUI and JASS triggers
- An option to disabled enforcing water height limits
- Added an experimental doodad palette
Changes:
- Now uses the OS temporary folder instead of the "Data/Temporary" folder
- Greatly increased pathing map contrast
- Trigger and Import editor window modality changed
- Now uses a ribbon instead of the old menu
Fixes:
- Properly set the pathing for water and blight
- Tilesetter now properly enforces 16 tiles
- The correct ground texture variation is now chosen
- Properly scale units and items
- Properly scale doodads
- Saving now chooses the right target

HiveWE 0.3
Additions:
- Warcraft 1.29 support
- Added a Tile Pathing setter
- Added a Terrain Palette.
- Added an Import Manager
- Now shows the pathing texture on cliffs too
- Added a first person camera and allow switching between them
- Added terrain shadows
- Reset camera using CTRL + Shift + C
Changes:
- Removed war3Patch.mpq from the hierarchy
- Added deprecated.mpq (from 1.29) to the hierarchy
- SLK loading is now roughly 4x as fast (improved map load time)
- Hides the brush when palette is inactive
- Some small quality of life improvements
- Improved RoC compatibility for unit loading
- Changed terrain rendering to support different ground texture sizes
- Now remembers your last open/save location
- Further increased rendering performance for doodads a lot
- Now remembers your Warcraft 3 directory if you previously located it

Fixes:
- Fixed tileset/map hierarchy order
- Fixed loading items placed on the map
- Fixed a bug with the terrain being off by one (64x64 became 63x63)

HiveWE 0.2
- Instanced rendering for Doodads and Cliffs provide a massive speed upgrade
- Added tooltips to all buttons
- Centered brush on mouse
- Some code refactoring
- Added tilesetter
- Fixed blocky pixels under oblique angles
- Added terrain saving
- Allow running multiple instances
- Fixed tile variation bug
- Fixed tile texture UV bug
- Added unit rendering
- Very rudimentary animation parsing and geoset hiding
- Improved RoC file format compatibility
HiveWE 0.1
- Initial release
- Draws terrain and doodads
- Editing the pathing map

Technically a Warcraft installation is not required since the editor relies only on the game CASC files. We cannot distribute these due to legal reasons. Just point the editor at the folder containing them when it asks and you should be good to go!

If you encounter any issue with HiveWE then do ask for help! You can post here, reach me on the Hiveworkshop Discord eejin#4240 or message me on GitHub.

Many thanks to Ghostwolf for without him I wouldn't have gotten anywhere near as far. Also thanks to the rest of the Hiveworkshop community for supporting the creation of this editor.

Backup your map before using HiveWE
Previews
Contents

HiveWE 0.6 (Binary)

Reviews
Retera
This is a state of the art open source World Editor that draws on all of the community's knowledge of how to make Warcraft III maps. This current build is great for drawing terrain and doodads -- and new features are clearly under active development....
  1. eejin

    eejin

    Tool Reviewer

    Joined:
    Mar 6, 2017
    Messages:
    137
    Resources:
    1
    Tools:
    1
    Resources:
    1
    I totally forgot that Apple stopped implementing newer OpenGL versions and stopped at 4.1. So Mac support seems off the table for now atleast.

    Direct State access is 4.5 and GL_DEBUG_OUTPUT is 4.3. There are probably some more, but these are off the top of my head.
     
  2. Dr Super Good

    Dr Super Good

    Spell Reviewer

    Joined:
    Jan 18, 2005
    Messages:
    25,546
    Resources:
    3
    Maps:
    1
    Spells:
    2
    Resources:
    3
    Although an optimization, it does not appear to be a critical feature. Warcraft III is so old that even with the old context binding method it will still perform well. In fact it will still likely perform better than Warcraft III and WorldEdit as both still use the old fixed function pipeline to render before programmable shaders were added to OpenGL and Direct3D.
    Appears to serve a similar purpose to the debug layers of Vulkan applications. This is an optional feature that is useful for developers but optional for users. Hence could easily be removed for final builds.

    If performance is a concern you would already be using Vulkan, which only has a slightly higher requirement to run than the currently required OpenGL version.
     
  3. karaulov

    karaulov

    Joined:
    Jun 17, 2010
    Messages:
    203
    Resources:
    3
    Tools:
    3
    Resources:
    3
    Last edited: Feb 17, 2018
  4. eejin

    eejin

    Tool Reviewer

    Joined:
    Mar 6, 2017
    Messages:
    137
    Resources:
    1
    Tools:
    1
    Resources:
    1
    Your GPU probably supports the GL_DEBUG_OUTPUT extension and that OpenGL header exposes those.

    I will think about supporting a lower OpenGL version.
     
  5. karaulov

    karaulov

    Joined:
    Jun 17, 2010
    Messages:
    203
    Resources:
    3
    Tools:
    3
    Resources:
    3
    I try to 'convert' it to 3.x version Opengl

    HiveWE_openl3.x.zip

    But i can't convert shaders from 450 to 3xx )
     
  6. Dr Super Good

    Dr Super Good

    Spell Reviewer

    Joined:
    Jan 18, 2005
    Messages:
    25,546
    Resources:
    3
    Maps:
    1
    Spells:
    2
    Resources:
    3
    Possibly because they are using a 4.5 feature. Dropping back to 3.X is a huge regression in available shader features and capabilities. That said technically WC3 does not need any such advanced stuff because the game itself uses nothing more than the most basic OpenGL fixed function pipeline. One can however expect performance regressions as a result, after all that is largely what the more recent API revisions focused on.

    I personally would recommend targeting the editor at similar requirements to what one needs to run WC3 since that would make it the most available to potential users. Note that Warcraft III had its system requirements raised to Direct3D9 recently, so there are still many features one can use.
     
  7. lan nguyen

    lan nguyen

    Joined:
    Feb 14, 2018
    Messages:
    34
    Resources:
    0
    Resources:
    0
    Is it able to change the tiles editor like sc2? Not completely replace the old one,but just add the circle tiles and cliffs editor. Sorry,bad english :(
     
  8. Dr Super Good

    Dr Super Good

    Spell Reviewer

    Joined:
    Jan 18, 2005
    Messages:
    25,546
    Resources:
    3
    Maps:
    1
    Spells:
    2
    Resources:
    3
    No it cannot because that is not how Warcraft III works.
     
    Last edited: Feb 18, 2018
  9. lan nguyen

    lan nguyen

    Joined:
    Feb 14, 2018
    Messages:
    34
    Resources:
    0
    Resources:
    0
    I'm working on a project called Wardota2 that brings dota 2 experience to dota1's players but we cant because the tiles editor was bad
     
  10. Dr Super Good

    Dr Super Good

    Spell Reviewer

    Joined:
    Jan 18, 2005
    Messages:
    25,546
    Resources:
    3
    Maps:
    1
    Spells:
    2
    Resources:
    3
    What does this have to do with a third party Warcraft III editor? If you are saying that you are making a DotA2 based map for Warcraft III then you will have to deal with the limits of the Warcraft III engine.

    DotA2 is over a decade more advanced than Warcraft III.
     
  11. A Void

    A Void

    Joined:
    Mar 29, 2011
    Messages:
    2,486
    Resources:
    10
    Models:
    2
    Spells:
    1
    Tutorials:
    7
    Resources:
    10
    Welcome to Warcraft 3 modding. This is just an editor, it doesn't add new features beyond the scope of the game. However, there are various workarounds to your tile problem.. Try using Ubersplats as ground textures. See my attachment for an example.
     

    Attached Files:

    • cl3.png
      cl3.png
      File size:
      502.1 KB
      Views:
      166
  12. karaulov

    karaulov

    Joined:
    Jun 17, 2010
    Messages:
    203
    Resources:
    3
    Tools:
    3
    Resources:
    3
  13. lan nguyen

    lan nguyen

    Joined:
    Feb 14, 2018
    Messages:
    34
    Resources:
    0
    Resources:
    0
  14. TriggerHappy

    TriggerHappy

    Code Moderator

    Joined:
    Jun 23, 2007
    Messages:
    3,665
    Resources:
    22
    Spells:
    11
    Tutorials:
    2
    JASS:
    9
    Resources:
    22
    There's also Zépir's War3 Map Editor 1.0, however none of them have rendering like HiveWE.

    I actually didn't know about Mrkol's war3editor. It looks like he will be trying to implement rendering as well but it's in early stages. The code is C# though which is nice (@MindWorX).


    Take a look at the attached images. I couldn't find a download link but maybe they are using ubersplats like A Void said.
     

    Attached Files:

  15. karaulov

    karaulov

    Joined:
    Jun 17, 2010
    Messages:
    203
    Resources:
    3
    Tools:
    3
    Resources:
    3
  16. Wareditor

    Wareditor

    Joined:
    Jan 16, 2009
    Messages:
    681
    Resources:
    3
    Maps:
    3
    Resources:
    3
    @karaulov, Do you realise this doesn't work for Warcraft 3 at all? You can find hundreds of editors like that, are you gonna post them all in this thread?
     
  17. karaulov

    karaulov

    Joined:
    Jun 17, 2010
    Messages:
    203
    Resources:
    3
    Tools:
    3
    Resources:
    3
    Wareditor, but some features can be moved from not working map editor to HiveWE, or no ? :)
     
  18. A Void

    A Void

    Joined:
    Mar 29, 2011
    Messages:
    2,486
    Resources:
    10
    Models:
    2
    Spells:
    1
    Tutorials:
    7
    Resources:
    10
    By the way, why are the textures more detailed and crispy in the editor? They look damn fine, but in-game it gets worse. War3 needs rendering upgrade... Ironic considering that rendering from editor is better than the game we're playing in.
     
  19. eejin

    eejin

    Tool Reviewer

    Joined:
    Mar 6, 2017
    Messages:
    137
    Resources:
    1
    Tools:
    1
    Resources:
    1
    If you are playing on 16:9 then the game is stretched while in the editor they aren't. I probably use better texture filtering too.
     
  20. Dr Super Good

    Dr Super Good

    Spell Reviewer

    Joined:
    Jan 18, 2005
    Messages:
    25,546
    Resources:
    3
    Maps:
    1
    Spells:
    2
    Resources:
    3
    No they cannot. It is like asking if you can ride your bike to the moon. Just because a rocket can go to the moon does not mean your bike can.
    Because they incorrectly use mipmaps, which is not supported by the way tile textures are composed. This is why the textures look utter garbage in this editor on oblique angled terrain because bilinear filtering has to be turned off which in turn means it looks like an ancient PS1 game (although with affine correction) due to nearest texel interpolation being used.
    You use incorrect filtering. There is a reason why in a game where all other world models use mipmaps Blizzard designers purposely told the terrain to not... Your hacky work around causes major artefacts with oblique angles, which are not a problem for and render perfectly in Warcraft III.

    This is what I mean...
    [​IMG]
    Notice the pixilation that is occurring due to nearest texel being used during interpolation. Watch the texture feature positions as well to see bad UV logic. Seamless Warcraft III terrain will show seams in this editor!
    [​IMG]
    Notice how the green smudge is lower down showing bad UV or mipmap logic in HiveWE. Additionally notice how no pixilation is present because bilinear sampling is being used. Aliasing can be noticed with the textures in the background due to the lack of mipmaps.

    The map shown is not mine, but rather one I had lying around and just happened to use for testing the editor that noticeably showed the problem. I do not claim any credit for it.

    The correct (Warcraft III) UV logic is to place the vertex corners exactly in the middle of the 2 pixel boarder assuming 64*64 pixel tile components or in the middle of the boarder pixels assuming 32*32 pixel components. Assuming a numeric range from 0.0 to 1.0 for the tile component (with all 64*64 or 32*32 pixels being square and equal sizes) this would mean they would have some combination of the values 0.015625 and 0.984375.

    If one wants to use mipmaps for terrain one would have to break each tile component into its own texture (possibly a 3D texture?). This is to prevent cross component bleeding at lower mipmap levels than 32*32 pixel components where the bilinear interpolated sample is derived from texels of neighbouring tile components. This obviously has huge performance implications which is why Blizzard decided to disable mipmaps for the terrain and why StarCraft II blends in continuous textures rather than using tile components.
     

    Attached Files: