Need System Ideas!

[UndeadDragon]

It would be pretty complicated if it was in GUI though.

 

[Romek]

:< if only it were not jass thanks though!

It's easy enough to use in GUI, despite it being coded in Jass.
Just make a boolean variable and a unit variable.
and use this:
Custom Script: set udg_<Boolean Variable Name> = GetUnitCombatState(udg_<Unit Variable Name>)
For example:

• Actions
  • Set Unit = Triggering Unit
  • Custom Script: set udg_InCombat = GetUnitCombatState (udg_Unit)

Then the boolean variable (called InCombat, in this case). Will be true if the unit is fighting, and false if it isn't.

 

[Charapanga]

What about a Jump System? How high it jumps depending on the distance between the caster and where he wants to jump?

 

[Romek]

What about a Jump System? How high it jumps depending on the distance between the caster and where he wants to jump?

Jumping Spell Template.

And there are about 50 other jump systems around anyway

 

[Igor_Z]

Here is something that isn't made i think:
2. Make System for Missle detection to detect when the storm bolt missle will hit the target but in GUI i don't need it in JASS... I just wanted to know that can it be done in GUI?!

 

[TriggerHappy]

Pretty much anything can be done in GUI as with jass. But it's harder and i will code the system in jass.

 

[Pharaoh_]

2) Impossible to click icons , unless you use advanced trackables.

Since i am interested in such thing, could you explain what those advanced trackables are, that are required to make clickable icons on Multiboards?

 

[Romek]

> Igor_Z
Ever heard of "damage detection"?.
Search it on the forums. It's quite easily made in GUI as well.

A 'system' like that wouldn't be anything more than a Damage Detection.

What's the difference between "trackables" and "advanced trackables"?

 

[Renendaru]

I think he means things like raised trackables, and player-specific ones...

 

[TriggerHappy]

Player Specific Trackables are impossible.

 

[Renendaru]

Nope... Use handles... They provide examples of this on wc3campaigns.net

 

[Viikuna]

Some nice lightning struct would be cool.
Im currently making a Lighning struct for my map. It has lots of cool methods, like moving lightning between units and changing lightning color over time. ( Like fading from 255 alpha to 0 alpha over 1.5 seconds )
I think people would find it usefull, so why dont you make something like that?

There is many damage detection systems, but that doesnt mean that you shouldt try to make a new better one, if you feel like it.

And make your systems not to require any other systems please. I dont really like when people do that.

 

[TriggerHappy]

Rendaru , i'm pretty sure you can't detect who clicked a trackable.

 

[Viikuna]

Maybe trackables are like pseudohandles? Try H2I and see.

EDIT. You can "create" them for only one player by setting path to "" for others. Just use GetLocalPlayer

 

[TriggerHappy]

I'm pretty sure it's been proved that you can't :

1)Detect Triggerer of trackable
2)Destroy a trackable
3)Move a trackable

 

[Viikuna]

GetTriggeringTrackable and different trackables ( by using different paths ) for different players should work. I havent tested it tought.

 

[TriggerHappy]

GetTriggeringTrackable Detects the trackable , not the triggering player.

 

[Renendaru]

Hmmm... Can't go to wc3campaigns for some reason.... Used to be able to..

@Happy: It is possible to detect it through GetLocalPLayer() isn't it?

 

[Viikuna]

Yes, but if you know what trackable it is, you know which player hitted it, since you actually can make them to ignore all players but one.

local string path = "footman.mdx"
if GetLocalPlayer() != Player(0) then
    set path = ""
endif
call CreateTrackable(path,0.0,0.0)

or something like that.

EDIT. Then you just use old good gamecache and attach some nice structs to those trackables.

 

[Romek]

You can't move or destroy trackables. But you can create a trackable for each player in the same place, and only make one of them visible to each player.
So every player actually clicks a different trackable.

Then just get the player, depending on the trackable clicked.