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.
Q. Do trackables work in multiplayer maps?
A. Yes, they work fine. As for tracking which player triggered the trackable, you would need a handler system for that.
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:
modelpath is the path of the model you would like
to use. Use
"" for an invisable
trackable. Remember
to use \\ instead of \.
facing is the angle that the
trackable faces (remember
this cannot be changed after creation)
The events for trackables are as follows:
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.
function Massage takes nothing returns nothing
endfunction
//===========================================================================
function InitTrig_zomg takes nothing returns nothing
local trackable tr=
CreateTrackable(
"units\\human\\Peasant\\Peasant.mdl",0,0,-90)
//Creates our trackable, with the peasant model endfunction
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.
// ===========================
// Trackable API
return GetHandleReal(tc, "x")
endfunction
return GetHandleReal(tc, "y")
endfunction
return GetHandleReal(tc, "facing")
endfunction
return GetHandleString(tc, "path")
endfunction
call SetHandleReal(tc, "x", x)
call SetHandleReal(tc, "y", y)
call SetHandleReal(tc, "facing", facing)
call SetHandleString(tc, "path", path)
return tc
endfunction
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.
// t1 and t2 are visually the same trackable, but in fact they only work for one player each
local string peasant =
"units\\human\\Peasant\\Peasant.mdl"
set path = peasant
endif
set path = invisible
set path = peasant
endif
call SetHandleInt(t1, "player", 0) // Store which player "owns" this trackable
call SetHandleInt(t2, "player", 1) // Same for player 2
// Add events to register track/hit on t1 and t2...
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:
return Player(GetHandleInt(t,
"player"))
endfunction
set path = invisible
endif
call SetHandleReal(tc, "x", x)
call SetHandleReal(tc, "y", y)
call SetHandleReal(tc, "facing", facing)
call SetHandleString(tc, "path", path)
return tc
endfunction
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.
set d = null
return tr
endfunction
It works by creating an Invisible Platform at the given height, and then creating the trackable on top of that. After removing the platform, the trackable stays in place."
_________________________________________________________________
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.
Jass Tutorials
