Show Posts
1
Warcraft III Modelling / Re: War of the Three Hammers (WotTH) Models Gallery
« on: July 24, 2017, 11:04:44 PM »
Updated Bronze Beard warrior
Warcraft III:
Maps •
Models •
Skins •
Icons •
Spells •
Tools •
Tutorials
WC3 JASS: Code Snippets • JASS and vJASS Spells and Systems • Jass Tutorials
Chat @Discord
WC3 JASS: Code Snippets • JASS and vJASS Spells and Systems • Jass Tutorials
Bronze Beard Warrior A model from the abandoned project War of the Three Hammers, a campaign developed initially by Camel's Hump and with the participation of an great staff of modellers, animators and skinners. This is one of the several models developed for this project. I hope you can give a good use in your project. Notes: This model has no team color, but it has a lot of animations. It can be used as unit or hero, but mostly as a hero because it doens't have decay animations. 3
Warcraft III Modelling / Re: War of the Three Hammers (WotTH) Models Gallery« on: July 23, 2017, 09:59:14 PM »
Uploaded BB_Crossbowman.
4
Warcraft III Models / Bronze Beard Crossbowman« on: July 23, 2017, 09:48:50 PM »
Bronze Beard Crossbowman A model from the abandoned project War of the Three Hammers, a campaign developed initially by Camel's Hump and with the participation of an great staff of modellers, animators and skinners. This is one of the several models developed for this project. I hope you can give a good use in your project. 5
Warcraft III Modelling / Re: War of the Three Hammers (WotTH) Models Gallery« on: July 23, 2017, 09:06:04 PM »
Uploaded BB_Ramrider... at last!!!!
6
Warcraft III Models / Bronze Beard Ram Rider« on: July 23, 2017, 09:00:55 PM »
Bronze Beard Ram Rider A model from the abandoned project War of the Three Hammers, a campaign developed initially by Camel's Hump and with the participation of an great staff of modellers, animators and skinners. This is one of the several models developed for this project. I hope you can give a good use in your project. 7
Jass Tutorials / Trackables (Mouse detection)« on: July 09, 2017, 01:51:10 AM »
Tutorial originally made by wonderpriest inspired in Kattana original tutorial.
Trackables A trackable is just something like a doodad, let's say. But it is different as it can't be selected, it can't be moved, it can't die, and it can't be eliminated. It doesn't even have to be seen if you don't want it to. The point of a trackable is to harness the mouse detection for usage in triggers. Mouse detection just means the game registers when your mouse pointer moves over an object, or clicks it. FAQ As I get more questions, I will answer them here so you don't have to sift through the posts. Code: jass [Select]
Limitations Although Blizzard gave us these functions to use mouse detection, it doesn't seem they really cared to finsh the code, because you can not retrieve a triggering player from a trackable event. Nor can a trackable be owned by a player. The usage of trackables is very limited, because you can not manipulate anything about a trackable once you create it, or before. This means you can not move, scale, color, or make any other kind of modification. You just create it, and that's it. Also, one of the reasons not many people know of trackables, is because they require JASS to fully use. You can create and manipulate trackables through the Custom Script action, but there is no event in GUI that uses trackables. Fortunately, the functions are not very hard to understand and require little, if any, JASS knowledge. Usage I wanted to bring these trackables to attention, because even many JASSers seem to not know what they are. Trackables are a powerful tool that can be used to make better interactive systems, and even things like mini-games. To use trackables, first you must create them. They can not be pre-placed in a map, so you must make them through triggers. They are created somewhat like units are created, only you use a model string to determine the model of the trackable, not an id or name. This is actually very useful, because you can use any valid model path. This includes units, buildings, doodads...anything with a model path. If you use a unit or buildiing model, the trackable will appear looking like a neutral hostile unit, with no team colors. Trackables do play animations. If you want a trackable to be invisible, you just insert a void string argument (""). Here is the function to create a trackable: Code: jass [Select]
The events for trackables are as follows: Code: jass [Select]
TriggerRegisterTrackableHitEvent registers when a player clicks on a trackable. TriggerRegisterTrackableTrackEvent registers when a player moves his mouse across a trackable. You may notice that this same system is in place with normal units in Warcraft III. When you click a unit, you select it. When you pass over a unit with your mouse, a bar shows it's health. Trackable events work like any other event, but you also need to specify a trackable for the event to register. A Trigger: This trigger will create a trackable, and when someone passes over it, a message will be sent. Code: jass [Select]
You may notice I display the message to all players. This is because there is no 'GetTriggeringPlayer' for a trackable event, which is probably the biggest limitation of trackables. But, there is a 'GetTriggeringTrackable'. Which opens up possibilites to fix the missing TriggeringPlayer problem. (With 'GetTriggeringTrackable', you may be able to stimulate a Triggering Player, maybe by using the Handle Vars or another system) The Result: ADD: Trackable Workarounds (credits to KaTTana) Using Handle Vars With Trackables KaTTana wrote this part better than I can, so here it is. You can find KaTTana's Trackables tutorial here: Link You can find KaTTana's Handle Var turorial here: Link A Part of KaTTana's Tutorial: "We don't have any natives for getting the (x,y) coordinates of a trackable, but we can handle that ourselves with the Local Handle Variables. Here is a custom API for extended use of trackables. Code: jass [Select]
Trackables in Multiplayer Previously, the tutorial stated that trackables didn't work in multiplayer, but that was wrong. They work fine, and they don't desynchronize the game. However, there is no way to determine which player triggered the event on a trackable. We can work around this by creating a trackable for each player - each can only be triggered by one player. Code: jass [Select]
After this, you can determine the player triggering a trackable by reading the local integer named "player" on the triggering trackable. We can extend to NewTrackable if you like: Code: jass [Select]
Giving height to Trackables Although the natives do not allow it, a simple workaround enables us to create trackables at a given height above ground. Code: jass [Select]
_________________________________________________________________ Once again, that was part of KaTTana's trackable tutorial, which you can find here: Link That's it for the Trackables tutorial, thanks for reading, and hope you have fun using these in your map! Questions, comments, and suggestions are welcome, and appreciated! ADD: If anyone finds this confusing, or wants a demo map to look at, just say iit and I will make a demo map using all of the Trackable functions. 8
Jass Tutorials / Creating simple AIs for Hero Arena-type maps« on: July 09, 2017, 01:42:59 AM »
Developed by Blade.dk
This tutorial will help you add a simple, but cool, AI to hero arena type maps. The AI you’ll learn how to make here will not be perfect. The one we will create here will attack other heroes, pick up items, learn and use spells, but it won’t be as effective as a human player. However, when you’ve learned the basics you should be able to improve it yourself. Requires JASS Knowledge – This tutorial uses JASS examples, and JASS-only features, so you will need to know JASS to follow this tutorial and make the AI. Technically it can be done in the GUI, but I won’t recommend that due to memory leaks, tons of unneeded code, and because using return bug and game cache based systems isn’t possible in the GUI. If you don’t know JASS, check the JASS tutorials at The JASS Vault and Wc3Campaigns. You also need to know what a rawcode are, if you don’t, just search the different Warcraft 3 sites to find out. A game cache and return bug based system – This can be KaTTaNa’s Local Handle Variables, Vexorian’s CSCache module (a part of the Caster System) or any other similar system. In this tutorial I’ll use the CSCache module. This map – A small map I’ve created that shows a simple AI like the one we’ll make in action. It is important that you have this map, as the tutorial often refers to it. Notes - The AI we’ll make here is not as good as a human player, but better than nothing. And when you’ve learned the basics, you should be able to improve it yourself. - A lot of numbers (player numbers, for example) starts from 1 in the GUI, but while they starts from 0 in JASS. As this is a JASS tutorial, they start from 0 here. - You don’t have to do the things exactly like I do them; I do it in my way, but if your way is better or you just feel more comfortable with it, do it your own way. I’m not perfect, and this tutorial isn’t perfect either, but hopefully it will help somebody. - You could use the AI from my demo map without creating your own (if you do so, give me credit), but I suggest making your own, as maps can be very different, and because you should be able to learn more from making it yourself. - The demo map is probably not perfectly unbugged, and it isn’t the funniest map either. Remember that it was just a map I quickly created to show a simple AI, if you want to see a better map with a good AI, take a look at Azeroth’s Arcane Arena. - I would like to specially thank Vexorian for encouraging me to make my first AI for my map, giving me tips on how to do it, and for showing me his AI, which helped me improve mine. Thanks! Initialization First create a new trigger with the “Player - Player 1 (Red) leaves the game” event. Convert it to JASS. We need that trigger to register when a player leaves the game, so we can start the AI for that player. At the moment it will only register when player 0 leaves the game, so we’ll use a loop to make it register when any player from 0-11 leaves instead. We want the AI to use abilities. This may sound hard, but it isn’t. We just have to make the Heroes learn the abilities, and they’ll cast them themselves. NOTE: The situation where a computer-controlled hero will cast a spell is always the same situation as where it would cast the spell it’s based on. So if you have a custom spell based on Silence, it will cast it in situations where it would cast it in melee games. NEVER base your spells of the “Channel” ability, as the AI never will use them. Changing the OrderString field on a spell in the Object Editor does nothing, it will still be the same as on the base spell. To know which spells the heroes have, we create a game cache to store it in. In the example map my trigger creates a gamecache at map initialization and saves it in the udg_GameCache global variable. Note that the cache HAS to be initialized before we starts using it, so I will do that in the first InitTrig function of my map. In my map I create a function called “SetupSkills”. In the AI trigger’s InitTrig function I use the ExecuteFunc native (read more about that native here) to execute that function in another thread. This is to prevent the map initialization thread from getting too long, and crash. My SetupSkills function looks like this: Code: jass [Select]
Here’s my InitTrig_AI function: Code: jass [Select]
Starting the AI for a hero To control the AI I will use a timer. I create a function called “StartAI” that takes a single unit argument: the hero (check the function in the example map). The function just creates a timer, "attaches" the hero to it, and starts it (just make the expiration function now, we will out some actions into it later, but you need the function and endfunction lines to prevent getting compile errors). This is the empty AILoop function and the StartAI function from the example map: Code: jass [Select]
Note that I’m starting it as a “one-shot” timer, by using false as the 'periodic' boolean value (we’ll get back to that later). Now just make your hero selection system call that function when a computer controlled player chooses a hero, and go to the function that is executed when a player leaves the game. Check if the player has a hero, if he/she has one, call the function that starts the AI on that hero. Example: Code: jass [Select]
NOTE: This will make the AI take control of a leaving player's hero, this is not needed, if you want to do something else when a player leaves. Making the AI do something Whenever the timer expires there are some things we want it to do:
We’ll start with declaring all the variables. Notice the real variable 'e' in my function, it defines how long time will elapse before the timer expires again, so we can wait shorter time if the hero is dead, or longer time if he/she/it is attacking. That variable is initialized with the value 5. Declare the local variables: Code: jass [Select]
We start with checking if the hero is dead, if he/she/it is, set the real variable to 1.5 (because waiting 5 seconds after revival is too long time, we don’t want that). The hero’s life ('l' is 0, just set e to 1.5 to make the timer check more frequently for the hero’s revival. Code: jass [Select]
Next I check if the hero’s life is below 20% of it's max life. If it is low, order the hero to move to fountain and set the variable 'e' to 3. The hero’s life is less than 20% of max life, so order the hero to move to the position of the fountain: Code: jass [Select]
If the hero isn’t weak, check if he/she/it has a common order (to prevent it from interrupting channel spells). If it is a standard order, we check if any enemies are within a radius of 500. If true, simply issue an attack order (don’t change the 'e' variable, 5 seconds is fine in this situation). Code: jass [Select]
If no enemies are found, check for items. If an item is found, check if it’s a powerup. If it isn’t, check if the hero has any empty inventory slots, and order the hero to pick it up. Code: jass [Select]
If the hero has items in all slots, or no items existed, order him/her/it to patrol to a random location in the map, to find new targets. Code: jass [Select]
Now let’s check if the hero has any unused skill points (keep this separated from the attack/item pickup/patrol block). If he/she/it has, call a function that learns a skill to the hero. In my example I’ve used a function that stores the number it has taught the hero an ability, to keep a special pattern in the ability learning: Code: jass [Select]
Now simply make the timer expire again after 'e' seconds: Code: jass [Select]
Last we need to set the local variables to null: Code: jass [Select]
Final notes This is the basics of it, it can be way better, but this should help you get started. Feel free to ask questions here or pm me. It shouldn’t be complicated at all, but if you have just checked the tutorial it can be so. The map was made to give a better demonstration, so please check it. When you have finished making your simple AI, try to add one or more of the following things to imrove it: - Try to make it find the weakest enemy close. - Try to make different AI players work together on killing a specific unit. - When most battles becomes centered about the fountain, make heroes run away from it when they’re fleeing. - Make the AI post text messages that varies depending on the situation (for example, an AI player can say “Die, sucker!” before killing you). I hope this will help somebody! Blade.dk 9
WC3 Editing Tools / A new TESH Syntax Highlighter for Warcraft 3« on: March 28, 2017, 10:53:33 PM »
by looking_for_help 1. Introduction It's been a long time since the first Trigger Editor Script Highlighter (TESH) was released by SFilip in 2007. His outstanding work was improved several times by others like Zoxc, Van Damm and Artificial, as well as by the developers of the Horus extension. The TESH adds some very nice Syntax Highlighting and Code-Completion functionality to the Warcraft 3 Editor and made coding in JASS and vJASS much more comfortable and nicer. However, after many years of extensive use, there are still some problems or things that could be solved nicer in order to make vJASS coding even more comfortable. As the original TESH is written in Delphi which is not free anymore and the source code is hardly commented at all, it was not possbile to build up such an extension on the original TESH source. For this reason, and because some of the features I had in mind required a modification of the Scintilla Source-Code itself, I decided to rewrite everything in C++ and restart with it completely from the scratch. 2. Installation and Requirements To install the new TESH to your Warcrat 3 Trigger Editor, just download the attached zip-file, unzip it and put the folder in your jassnewgenpack5d installation folder:
3. New Functionality There is tons of new functionality, both compared to the first TESH and to the older versions of TESH 2.0 (before version 0.9). Many of the features are already listed in the Version 0.9 changelog. To list some here:
And attached some screenshots:  Or some customized dark styling (just one example):  4. Version History Attached is the version history of the TESH documented with links to the corresponding update which contain further information. Version Histroy 10
WC3 Editing Tools / SharpCraft, a managed replacement for Reinventing the Craft« on: May 17, 2016, 10:20:13 PM »
Some of you might have heard about Reinventing the Craft. It's an old project I initially started in 2007 and worked extensively on for several years along with SFilip. Reinventing the Craft changed goals several times, but in the end, the idea was that we wanted to provide a stable API for extending Warcraft III with new natives and features. Sadly, due to limited coding experience and time, the project ended up collecting dust. Since we stopped working on it, I've been contacted several times by people asking for the source, but I was reluctant to release because of the mess it was and all the experimental features it had. On top of that, it was nearly impossible to maintain if an update were released. This got me to slowly work on a replacement. The new goal for the replacement was that it should be easier to use and it should prioritize maintainability in favor of features, and above all, it should be open source. Over the past few years I've worked on and off on project SharpCraft. SharpCraft is written from scratch in C# and using EasyHook to inject into Warcraft III, I'm able to do what Reinventing the Craft did. Likewise as Reinventing the Craft only worked with Windows, so does SharpCraft. If enough interest is shown in the future, I might be able to look into how to make a version for Mac. For the time being, the whole project relies heavily on Windows APIs though. I've finally reached a point where I feel confident in calling it usable and as such, I wanted to announce it. Credits
Code: [Select] v4.0.0.137Tutorials The tutorials assume a basic understanding of programming. SharpCraft Development Environment (basic), shows how to setup Visual Studio and use SharpCraft. SharpCraft Native Tutorial, shows how to add custom natives using the JassAPI plugin. This assumes you've followed the tutorial above. SharpCraft binaries and source can be found on GitHub. 11
WC3 Editing Tools / Gmax 1.2« on: April 27, 2012, 07:49:05 AM »
GMAX 1.2
 Gmax 1.2 is a 3D modelling software developed originally by Autodesk and offered as a lite version of 3Dmax. Minimum System Requirements:
How to install:
12
WC3 Editing Tools / Magos' War3 Model Editor« on: August 28, 2011, 11:16:11 PM »
 This is another "must have" tool for WC3 modding. It allows basic edition and preview of models in WC3. It's a good complement to the MDLVIS model editor. It offers the following features: Quote from: http://home.magosx.com/index.php?topic=6.0 War3 Model Editor as the name suggests a Model Viewer and a Model Editor dedicated to Warcraft 3. It supports both loading and saving of *.mdl and *.mdx model formats which are used in Warcraft 3. It also supports *.bmp, *.tga, *.png, *.jpg, *.jpeg, *.pcx and *.blp texture formats. What's the difference between this version and the one found at home.magosx.com: it comes with a direct 3d library required to run. How to install: DOWNLOAD HERE, uncompress using 7z or other compression software which supports 7z format, open the folder and select "War3ModelEditor.exe". And thew magic will start  13
WC3 Editing Tools / MDLVis« on: February 19, 2011, 10:41:41 PM »
Pages: [1]
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
