And how to force cpu to cancel building processes like "mutation to hatchery" and so on?
Post has been edited 1 time(s), last time on Aug 25 2009, 3:41 pm by theleo_ua.
None.
If human player (p1 for example) start mutation to guardian\devo - how to force cpu to cancel this mutation for p1?
And how to force cpu to cancel building processes like "mutation to hatchery" and so on?
Post has been edited 1 time(s), last time on Aug 25 2009, 3:41 pm by theleo_ua.
And how to force cpu to cancel building processes like "mutation to hatchery" and so on?
Post has been edited 1 time(s), last time on Aug 25 2009, 3:41 pm by theleo_ua.
memes memes memes memes memes memes memes memes memes memes memes memes memes memes memes memes memes memes memes memes memes memes memes memes memes
To force a CPU to cancel zerg buildings, it must be attacked and at low hp.
The CPU will not cancel morphing of mutalisks.
The CPU will not cancel morphing of mutalisks.
You can use a work-around, maybe something like removing and creating a new mutalisk at that same location?
---Edit----
If I recall Correctly, a version of Storm The Fort has mutalisks to activate "Entering a Vehicle". You mutate into a guardian, and it changes back into a mutalisk some how. I looked through all of my versions, and I don't have the updated version. I probably never got it back since my last reformat. This allows the player's selection on the Mutalisk/Guardian to stay retained on the unit. I'm not entirely sure how it works.
Then again, I may be completely wrong, and it just removes the Guardian/Cocoon and Creates a new Mutalisk in it's place.
Post has been edited 2 time(s), last time on Aug 25 2009, 3:24 pm by Pyro682.
---Edit----
If I recall Correctly, a version of Storm The Fort has mutalisks to activate "Entering a Vehicle". You mutate into a guardian, and it changes back into a mutalisk some how. I looked through all of my versions, and I don't have the updated version. I probably never got it back since my last reformat. This allows the player's selection on the Mutalisk/Guardian to stay retained on the unit. I'm not entirely sure how it works.
Then again, I may be completely wrong, and it just removes the Guardian/Cocoon and Creates a new Mutalisk in it's place.
Post has been edited 2 time(s), last time on Aug 25 2009, 3:24 pm by Pyro682.
None.
Quote from 
Pyro682
Pyro682You can use a work-around, maybe something like removing and creating a new mutalisk at that same location?
This clears selection (player will need to select created mutalisk again).
Quote
I probably never got it back since my last reformat.
If you will find this map - share it please:)
None.
Quote from Pyro682
Pyro682You can use a work-around, maybe something like removing and creating a new mutalisk at that same location?
---Edit----
If I recall Correctly, a version of Storm The Fort has mutalisks to activate "Entering a Vehicle". You mutate into a guardian, and it changes back into a mutalisk some how. I looked through all of my versions, and I don't have the updated version. I probably never got it back since my last reformat. This allows the player's selection on the Mutalisk/Guardian to stay retained on the unit. I'm not entirely sure how it works.
Then again, I may be completely wrong, and it just removes the Guardian/Cocoon and Creates a new Mutalisk in it's place.
---Edit----
If I recall Correctly, a version of Storm The Fort has mutalisks to activate "Entering a Vehicle". You mutate into a guardian, and it changes back into a mutalisk some how. I looked through all of my versions, and I don't have the updated version. I probably never got it back since my last reformat. This allows the player's selection on the Mutalisk/Guardian to stay retained on the unit. I'm not entirely sure how it works.
Then again, I may be completely wrong, and it just removes the Guardian/Cocoon and Creates a new Mutalisk in it's place.
It's just a really long build time for the mutation. Then if it hits guardian it will probably remove the unit and make a new mutalisk or Cocoon.
None.
Options
Pages: 1
Back to forum
Please log in to reply to this topic or to report it.
Members in this topic: None.
[2026-7-18. : 2:27 am]
Symmetry -- https://staredit.net/topic/18903/ THE REVIEWS ARE HERE! "ok these are pretty good memes" - ssj9Kevin[2026-7-17. : 2:58 pm]
Ultraviolet -- SymmetrySymmetry shouted: Man I wish we had this tech back in the day when people played ums lmao
fr fr[2026-7-17. : 2:39 am]
Symmetry -- Man I wish we had this tech back in the day when people played ums lmao[2026-7-16. : 6:28 am]
NudeRaider -- EUD actions, specifically. The conditions remained. Today we can even have actions again, but they're all virtualized/whitelisted (not sure on the actual technical implementation) so you can only use them for specific intended purposed, not arbitrary code injections.[2026-7-16. : 6:26 am]
NudeRaider -- I mean yes, maps - through EUDs - were theoretically able to do that as well, but that was patched quickly.[2026-7-16. : 6:25 am]
NudeRaider -- SymmetrySymmetry shouted: Ohhh imagine a SC map that could delete itself
not the map, the editor[2026-7-16. : 2:28 am]
Symmetry -- I vaguely remember Voy doing some ACE back in the day, but I had no idea EUDs could do that kind of shit. I am very much catching up on the technology[2026-7-15. : 8:51 pm]
NudeRaider -- SymmetrySymmetry shouted: NudeRaider Is EUD editor capable of writing shit onto the player's harddrive? That seems like it would be dangerous
yeah an editor that isn't allowed to write files sounds rather pointless, so I'd assume it can. Like most other programs too btw. and yes, obviously that's dangerous, but also kinda necessary. MS introduced that virtualization for exactly that reason.[2026-7-15. : 4:10 am]
Ultraviolet -- I don't think so. I think they shut that shit down after 1.16, maybe even earlier