Someone on Blizzforums has alerted me to a bug in the ModifyUnitResources action. The number you enter will not persist. This is due to a bug in the actions.lst file. So, replace yours with this one. You'll have to remove the .txt extension.
If you've made some customizations to that file already, you can simply make the change yourself. On line 263, change
Action(Where, 0, 0, 0, Owner, 0, 0, 52, Count, 4);
to
Action(Where, 0, 0, 0, Owner, NewValue, 0, 52, Count, 4);
[attachmentid=8695]
First person to get it! woot! (besides you, Heimdal)
Also I put it (link) in shoutbox. You should put it somewhere were everyone can see the link.
Considering that no one's reported this problem until now, and I've been using the same actions.lst for years, I don't think it's that urgent of a problem.
I was just giving an Idea because it would be nice not to have to worry about it in the future.
I've only seen this action used in two maps... ever...
1) What's wrong with this picture?
2) Offensive Strike
I highly doubt this is much of an issue
Lots of maps actually use this, its just you probably don't notice it.
Besides, why would you want something not work, even if it isn't used?
If something is not used, does it matter whether it works or not?
I'm just saying it's not that much of an issue...
It might not be a
big issue, but its still there.
Amagine this: you are doing something and you decide "it would be cool to have minerals that make a "wave" by going 1, 250, 500, 750, and then back down." You couldn't do that without that trigger.
Btw, that idea was taken by Sytheblade
(he probably wasn't the first, but he got mad at me when I copied it into my map)
or if you wanted a mineral to stay at 9.
Also, as I said before, why would you want something to not work?
Its better to have a complede StarForge than an incomplete one
It definitely needed to be fixed, and I appreciate you advertising it. There are probably very few people that it will affect, but for them it will be important.
I think i should stop reading Heimdal's posts... Most of the time they are way too complicated for me to comprehend
QUOTE(Ninebreaker123 @ May 9 2005, 04:54 AM)
I think i should stop reading Heimdal's posts... Most of the time they are way too complicated for me to comprehend
[right][snapback]203909[/snapback][/right]
I understand them and english is not my first language...
Woops, looks like I never saw that post Nic. Sorry.
I can understand even all the technical stuff he puts.
QUOTE
Action(Where, 0, 0, 0, Owner, 0, 0, 52, Count, 4);
to
Action(Where, 0, 0, 0, Owner, NewValue, 0, 52, Count, 4);
all that and the stuff in the txt file I understand. (Maybe not perfectly, but I can make some sense out of it.)
You might have a better chance of understanding it if you do your triggers in Starforge and is familiar with it.
OK i dont get this. it works fine for me.
I'll just ask a quick question.
Modifying the resource amount to 0 will make it dissappear?
or is it changing it to 1 will make it dissappear?
Kaboom: This has to do with the trigger, not setting the resource amount via the properties.
sckor: I think 0 makes it disappear, but you'd have to test that.
I don't think 0 makes it dissapear because you can place 0 ones on the map.