OK, this is about Munger, so I'd rather want to be careful
I have something like this:
MUNG.Move enemies to XXX and this action contains:
Insert Parameters - MOMA.Thrall move
world_point2d dest - (100.100.100.100) for example
Now I want this MUNG to make it with many MOMA's with other units, so it would be something like this:
MUNG.Move enemies to XXX
Insert Parameters - MOMA.Thrall move
world_point2d dest - (100.100.100.100)
Insert Parameters - MOMA.Soulless move
world_point2d dest - (100.100.100.100)
Insert Parameters - MOMA.Ghols move
world_point2d dest - (100.100.100.100)
Notice that I want all of these units to move to the same destination. And I wonder if I could put there destination only once, so it would look like that:
MUNG.Move enemies to XXX
Insert Parameters - MOMA.Thrall move
Insert Parameters - MOMA.Soulless move
Insert Parameters - MOMA.Ghols move
world_point2d dest - (100.100.100.100)
But I'm afraid it could crash, so I want to know that. It would be great, if it's possible, because endless clicking on the same place is soooo boring.
Munger question
No, it won't work. At best, the world point will only apply to the last Insert Parameter, and ignore the others. Or it may just not do anything. I don't think Mungers are likely to crash you these days. But in Mungers, order is everything, so you can't use shortcuts, unfortunately--you can't even copy existing Mungers, because the duplicate will put the name of the Munger after the other parameters, and screw it up.
I think Insert Parameter is not what you want in this case. Insert Parameter adds to something existing--for instance, if you had a link with two containers in it and wanted to add a third to them while keeping what was already there, you'd use Insert. If you're adding a completely new parameter, you want to use Append Parameter.
But I may be wrong--I'm not sure exactly what you're doing with the script. What's the context for the Munger, and why are they all going to the same point?
I think Insert Parameter is not what you want in this case. Insert Parameter adds to something existing--for instance, if you had a link with two containers in it and wanted to add a third to them while keeping what was already there, you'd use Insert. If you're adding a completely new parameter, you want to use Append Parameter.
But I may be wrong--I'm not sure exactly what you're doing with the script. What's the context for the Munger, and why are they all going to the same point?
Let's start clicking...A-Red wrote:No, it won't work. At best, the world point will only apply to the last Insert Parameter, and ignore the others. Or it may just not do anything. I don't think Mungers are likely to crash you these days. But in Mungers, order is everything, so you can't use shortcuts, unfortunately--you can't even copy existing Mungers, because the duplicate will put the name of the Munger after the other parameters, and screw it up.
Oh, yeah, maybe I should use Append Parameter, thanks. However, it was working with Insert Parameter too.A-Red wrote:I think Insert Parameter is not what you want in this case. Insert Parameter adds to something existing--for instance, if you had a link with two containers in it and wanted to add a third to them while keeping what was already there, you'd use Insert. If you're adding a completely new parameter, you want to use Append Parameter.
Well, it's hard to describe. I'll have few similar Mungers, and every of them will change few MOMAs, and will always be using the same destination. A bit complicated, but after lot of thinking I decided to make it in this way. Thanks for your answer A-Red.A-Red wrote:and why are they all going to the same point?
Last edited by gugusm on Wed Aug 08, 2007 5:42 pm, edited 1 time in total.
from what little i know of MUNGERing through khellek, you can do a lot. he was scripting something very complicated for me once - it used a lot of MUNGs and was still fairly long. then he managed to compress a whole lot of them, by MUNGing MUNGs and using the same MUNG to edit many different actions over and over.
naturally, the advice to be extremely careful of anything you do with them holds (doubly, if not more, if you're using them in more complicated ways), but they're very flexible indeed. just think through everything very carefully before you implement it - what can go wrong, etc..
but i'm not a scripter and i'm not all that intimate with what khel did in that scripting... i can take a look in a day or two and see if he did what you want to do, but it sounds like you have enough of a handle on things to safely work it out for yourself.
naturally, the advice to be extremely careful of anything you do with them holds (doubly, if not more, if you're using them in more complicated ways), but they're very flexible indeed. just think through everything very carefully before you implement it - what can go wrong, etc..
but i'm not a scripter and i'm not all that intimate with what khel did in that scripting... i can take a look in a day or two and see if he did what you want to do, but it sounds like you have enough of a handle on things to safely work it out for yourself.
*toot*
Well, this topic is not about munger at all, but look at A-Red's post, he describes how Munger works very well:
http://projectmagma.net/forum/viewtopic ... ght=munger
BTW: I found another way to make my script, without too many Mungers. Not that I don't like it, but my new method is easier and faster Anyway thanks for your replies about Munger
http://projectmagma.net/forum/viewtopic ... ght=munger
BTW: I found another way to make my script, without too many Mungers. Not that I don't like it, but my new method is easier and faster Anyway thanks for your replies about Munger