Welcome. Here's the place where modding your favorite game can be possible, and supported by a nice and warm community. Here you will find resources which will help you to develop your projects faster. Additionally you can show off your projects and share with a growing community, even be part of the Blizzard Modding Network, which aims to gather all the projects and clans around this game.
It was really rude of me to leave map described like that, so i came to change it. First of all, forgive me for description you are about to see because i am writing it based on remains of my memory of making it. It is not very recent map.
Keywords: Fel Lord, Demon, Burning Legion, Warrior, Fel, 512
Categories: Unit,World of Warcraft,Demon
Fel lords are a type of large and powerful mo'arg demons in service of the Burning Legion. They're usually found in the heat of battle tearing through enemies, cleaving and enjoying the ongoing mortal torment imposed.
They act as regional commanders for the Fel legions of the burning crusade.
As always, you're free to check out my Texturing thread for updates about my current skin works.
(Description) Summons a dark matter at the targeted point. The dark matter has ability to absorb all enemy units within 400 range onto it's position while releasing smaller dark particles to attack those captured units. Each particle deals 90 damage on hit. Lasts for 15 seconds. <...
This snippet is a replacement to the BJ function GetRandomSubGroup with the advantage of being able to directly enumerate random number of units in a group instead of creating another subgroup of an already existing group. Notice that this is not the same as GroupEnumUnitsInRangeCounted in which case the enumerated units are not random but is based on which units are picked first.
Useful system especially in making an MUI spell which uses timers. Instead of saving the spell data in a hashtable with the handleid of the timer as the parent key, you can just use normal arrays with the timerid as the index. This also allows you to pass custom data (integer) to timers.
Indexed timers (Array safe, 1-8190 but can also be customized to be 8190+) NEW
Timer custom data (integer) attachment [NEW]
Timer double free protection
Automatic timer replacement (Useful safety feature which automatically replaces timers belonging to this system with a timer of the same timerid and handleid when destroyed)
debugcall Debug("Total number of timers created: " + I2S(i))
debugcall Debug("Timer stock count is complete")
privatestruct S extendsarray
v1.2 - Added more functionalities such as attaching custom timer data, now the system comprises all but is not limited to the main functionalities of Vexorian's TimerUtils - Optimized the code especially in the part in updating the timer stack - Fixed some bugs
v1.1 - Added the possibility for users to configure the timer stock size above 8190 - Some fixes
Today is that lat day of the year where is an opportunity to remember all the thing we've done so far.
Thanks God, there's new stuff in the community to stand out, and I'll try to summarize.
One account for all the affiliate sites: With the new implementation, all the sites that belongs to the Blizzmod community allows to use the same account to access them. So if you registered your account in wc3modding.info, this same user and password can be used in the other places (blizzmod.info, wc3jass.com, etc...)
Resource filtering and easier search method available: You can see in blizzmod.info, wc3modding.info and wc3jass.com offer direct access links to the resources offered in those sites. All of them allows to have a clear description about its features and they can be filtered and searched by different categories, keywords and rating.
Topic integration with social networks: Every topic in blizzmod.info, wc3modding.info and wc3jass.com have links to Facebook and Google+, so you can share this topics easily with your friends. All the pages show nicely in those social networks. If the topic has an image in the first post, it will be used to stand out the topic in the sharing process.
Wiki/ integrated to the site: This section is aimed for integration with the coding highlighting. If you check, in the jass coding you can see a link over the function name which allows you to create or view a documentation to that function.
Related topic / resource: This feature allows to link any topic in all the pages from the Blizzmod network with other topics. This is useful to build "packs" of resources or to keep a trace of previous topics. This improves the chances that your topic gets accessible via google search.
Discord Chat: And the last but not least, the chat integration with Discord, where we're keeping together the community in support and chit chat in a reliable and faster way. It's easy to join, just follow the link
What's coming for 2018
Implement a faster way to upload resources. Right now you have to do two posting editions in order to implement the resources with images and download links.
uploading the model resources from the backup, so we can have again the big model database from the 2012 times. That's a big task to do.
Improve the icon submission system. Right now it's is slow and tedious to upload icon to the site.
Prepare the last version of JNGP (2.0.10) according to the new changes that seems to come in new patches of WC3
With all of this, I wish to all the community a happy new year 2018, expecting that your projects and goals gets successful and we hope this site keeps being useful to the WC3 community.
//The main tooltip of the added unit will always ignore color tags so the text will always appear to be white. Color tags should be parsed the same as all unit tooltips.
With each of call of this function, the minimap is modified in a bugged way :
The positions of units and the fog of war are modified to fit to the new camera bound but not the terrain, nor the destructables.
The minimap is compressed (vertically) according to the current camera's rotation. With a rotation of 90°, there is no compression. With a rotation of 227.40, the minimap is fully compressed. Between 227.5 and 312.6, the game crashes.
Moreover, the camera bounds will also be adjusted according to the rotation of the current camera. The camera bounds created will be a rectangle going trough the 4 points given and whose sides will be parallel to the camera.
nativeSetCameraBoundstakesreal x1, real y1, real x2, real y2, real x3, real y3, real x4, real y4 returnsnothing
Destroy all bound triggeraction objects.
Currently it only destroys all bound events, triggercondition and the trigger itself leaving all triggeraction objects to leak unless explicitly destroyed before.
Also destroy all currently scheduled trigger threads from that trigger.
Currently destroying a trigger with scheduled trigger threads can cause handle stack corruption which has a high chance to cause Warcraft III to crash.
//This BJ function is currently not net safe. Details explained: https://www.hiveworkshop.com/threads/fixing-smartcamerapanbj-desync.243334/
constantnativeGetEventDamagetakesnothingreturnsreal//Return the amount of life damage taken through an imperfect mana shield. Currently returns 0 or negative only even if the unit takes life damage through the shield.