Staredit Network

Many of us know that MindArchon released a program called "Trigger Duplicator" and it doesn't seem to be of much use (copying trigger's isn't useful when you have current player and etc). However, after further analysis of EUD Health Detection and Trigger Duplicator, I have found a way to store the amount of health lost or perhaps if you wanted, the amount of health.

The reason this idea came to me was because I was reading about shields and how to make a good one. I think the best way would be to detect health with EUDs. Then when shields are down, let the health just drain away.

So basically how to set this up is you first need to use uBeR@TiOn and let it calculate for you which player and unit you use for the unit # you are using. Say you are using the first unit placed. You would enter that into uBeR@TiOn and it would spit out
Player 4 has suffered exactly X deaths of 14411.

Using just the Player and Unit IDs, you type this into Trigger Duplicator:
Deaths(P4, exactly, 256*$x, 14411);

For the actions, since I am detecting health loss, I am going to type in this:
SetDeaths(AllPlayers, larva, setto, 10000-$x);
PreserveTrigger();

Basically what this does is it takes the max HP (10000) and subtracts $x from it. Health (for some odd reason) is stored at the second byte and on so you need to do 256*$x in the conditions.

In the loops, I doubt that Unit 1 will be losing more than 500 HP, so I enter
.............v(10000 max HP - 500)
For x = 9500 to 10000 with an interval of 1

Now it stores the amount of health lost in the death counter for Larva. Now using that, you can detect how often a unit gets hit or make a better virtual health system.

I just think that this is faster (a lot faster) than making the EUD Health Triggers one by one with uBeR@TiOn.

Interesting... it makes me want to learn triggering.. and EUD stuff.. but I'm a noob map maker.. I'm pretty much only here for my brain (as in testing maps and judging stuff )

Nice system. Very creative use of the duplicator.

I came up with a virtual HP system earlier where it just detects how much damage it has and subtracts from custom and resets health, but nobody seemed to care about it. I realised i could use trigger duplicator for it, because I wouldn't have spent that much time using uBeR@TiOn to make all of the triggers.

Nice concept, I'm going to try and put it to use.

I talked to mindarchon about the program, apparently there were some bugs that prevented some calculations to occur. But thats a great idea! I realized that it could do EUDs from all the problems ive had getting it to work.

DAMN YOU MINDARCHON! why does the stupid thing miscalculate the units sometimes?

Good concept though legacy.

The triggerduplicatormagigger is really useful for me, how I use it in bounds to set deaths as explosions and to effectively create explosions in massive quantities.

Its really useful. Try it out if you haven't. Useful bugger.

How many triggers do you think your method would take legacy?

EUD actions were patched but we can still use EUD conditions.

We have now, but also we can't actually predict what blizzard will do. They can just patch it one day

If you are doing damage, as many as how much max damage you think the map will have done to your unit.
If you are doing health, as many as how much health the unit has.
Basically you take damage and store it in a Death counter. You can also take Health and store it in a Death counter.
Doubtful. They patched actions way early and if they wanted to patch conditions, they probably would've patched them sometime during the 3 other minipatches that they made after patching actions.

I agree but we the same said before they patched actions in the first place. Remember and the other crap that was said...

I think that is ridiculous to think that triggers in starcraft map can do harm to operating memory. I mean it's a god damned map not program or something

It's like a program running a script. The script can cause the program to do bad stuff.
http://en.wikipedia.org/wiki/Buffer_overfl...erflow_exploits

No Close this thread! I dont want another blizzard patch! This will fark up so much stuff! STOP NOW! Mods, replays.

It's already patched pauper...

Blizzard made a HUGE mistake when they killed EUD actions, sure it allowed you to modify ram but.... they could have at least allowed for us to modify CERTAIN parts of the ram or RESTRICT certain modifiers. When EUD conditions and actions were discovered thousands of masterful yet dormant map makers started making maps again, HECK, it even made me start again. I was so excited cause starcraft turned into this new world where everything goes. Blizzard should have given us some control over the eud actions. Come on bliz, gimmie back my eud.
Whoops, on to this quote...

No, blizzard would be a complete fool if they killed EUD conditions, starcraft is hanging on the brink of existance with dozens to hundreds of starcrafters leaving every day.




We should have just kept all our secrets in secret,... oh wait, then nobody would know how to do it and you would be back in the same place you started at.






"Fixed a bug that crashed replays." The words that forever mark the grave of EUD Actions.

It is in blizzard's interests that starcraft dies and players buy their new games. They doesn't make any money with starcraft anymore, but they do with WoW and WC3. It just isn't gainful that we stay on starcraft that everybody has already bought years ago, they want us to buy new games and subscribe WoW...

Forget that, im trying to keep all my hard earned bucks to spend on bigger better things. The people that blizzard are targeting are: rich kids, who have parents, who do not care about what their child does. I can only pinpoint 15% of the population compared to Starcraft and its amazingly abundant population of freeloaders who suck the heck out of bnet's servers. amen.

They don't care about who buys their games, as long as people buy them...
It's all about money, greedy pigs

If Blizzard cared, they'd make StarCraft 2 already. Before WoW came out, StarCraft still dominated as the most widely played game on Battle.net. Not even WarCraft 3 or Diablo 2 could touch the number of people logged in at once in games.



As for the trigger, I understand what it does, but not how it works or why it works. Wish to enlighten me?

It detects every amount of damage it can get (up to 500, he assumed it wouldn't take more then that) then it resets health, and subtracts from the 'shield' death count which he used as larva.

Or if you mean how does the deaths of 14411 work, that's extended conditions that read the RAM somehow, I think you would need programming knowledge to understand how it works.

WoW actually isnt on battle.net




It works by what is called an overflow in the array.
http://en.wikipedia.org/wiki/Overflow if you want to know more.