Staredit Network > Forums > SC1 UMS Mapmaking Assistance > Topic: cloaking all units in 1 location
cloaking all units in 1 location
This topic is locked. You can no longer write replies here.
Jan 5 2009, 4:46 pm
By: okeee  

Jan 5 2009, 4:46 pm okeee Post #1



Is it possible to cloak multiple units in a location? When i disable doodad state for a location, only 1 of the units gets cloaked.



None.

Jan 5 2009, 5:03 pm Devourer Post #2

Hello

Quote from okeee
Is it possible to cloak multiple units in a location? When i disable doodad state for a location, only 1 of the units gets cloaked.
Yes...
make something like this.

requires 2 locations, 1 big where the units should get cloaked and 1 smaller, 2x2 would be best
x = small, y = big
Condition: Player Z brings at least 1 (unit which should be cloaked) to Y
Action: move location x on UNIT at Y
Action: disable doodad state for UNIT from Player Z
Action: give 1 UNIT from Player Z to Player 8
Action: Preverse Trigger

Condition: Player Z brings exactly 0 UNIT to Y
Action: Preverse Trigger
Action: Give all units from Player 8 to Player Z



Please report errors in the Staredit.Network forum.

Jan 5 2009, 9:07 pm Vrael Post #3



Be careful with this though, because certain units will crash the game when cloaked.



None.

Jan 5 2009, 10:04 pm Falkoner Post #4



If you copy the trigger DeVouReR posted a few times, it should speed up the process significantly, and to avoid extra disabling due to Bring not updating, you could also add a remove unit for an unused unit at the end of that trigger.



None.

Jan 6 2009, 6:11 am Vrael Post #5



Does it matter if he adds the action to the end of the trigger or the beginning? Just my thought process being if SC executes them sequentially, it won't update the bring-location-data untill the end of the trigger? But if the remove unused unit is at the beginning of the trigger actions it will be updated for those actions too?

Edit: Wait, that doesn't matter does it, since the trigger already fired lol sorry bad post



None.

Jan 6 2009, 6:13 am Falkoner Post #6



I would put it at the end, because if you don't, then the last one won't update so the trigger giving them all back won't run in the same loop.



None.

Jan 6 2009, 9:53 am okeee Post #7



ok that might work, but if you have lots of units, you have to increase the wait time between shared vision on and off, right?



None.

Jan 6 2009, 2:36 pm NudeRaider Post #8

We can't explain the universe, just describe it; and we don't know whether our theories are true, we just know they're not wrong. >Harald Lesch

The idea is to first disable them ALL
then give detecting vision
then remove the vision.

So it doesn't matter how many you disabled since you start the vision giving only after all have been disabled.




Jan 6 2009, 11:19 pm okeee Post #9



Quote from Falkoner
If you copy the trigger DeVouReR posted a few times, it should speed up the process significantly, and to avoid extra disabling due to Bring not updating, you could also add a remove unit for an unused unit at the end of that trigger.
I'm not sure what you're talking about. how can there be extra disabeling, if after the last unit, no more units are available (and so "bring 1 unit" condition is not met).



None.

Jan 7 2009, 12:34 am Falkoner Post #10



Quote
I'm not sure what you're talking about. how can there be extra disabeling, if after the last unit, no more units are available (and so "bring 1 unit" condition is not met).

Yes, but when you give units, the bring condition doesn't update for like 2 trigger cycles, so the condition wouldn't actually be met, so it'd run it a few more times, possibly causing bugs.



None.

Jan 7 2009, 9:23 am okeee Post #11



Ok i tried it but it didnt work. I tested another easy setting:

player2:
elapsed time is at least 10s
disable doodad state for unit A at location x

always
disable doodad state for unit B at location y

player1:
elapsed time is at least 15s
turn on vision for player2
wait 0ms
turn off vision for player2


and then ONLY unit A would be cloaked. Both of the units were disabled though (couldnt click on them).



None.

Jan 7 2009, 12:54 pm NudeRaider Post #12

We can't explain the universe, just describe it; and we don't know whether our theories are true, we just know they're not wrong. >Harald Lesch

Vision is slow. Waiting 1 trigger loop (0ms) isn't enough.
Use give, which gives instant vision. (still need 0ms wait)
Or make the wait like 6000ms.




Options
  Back to forum
Please log in to reply to this topic or to report it.
Members in this topic: None.
[2025-6-23. : 10:56 pm]
Ultraviolet -- Also as Nude pointed out, it's incredibly cheap to add one even if you don't already have it. Doesn't seem like there's a good reason to go with an old style SATA SSD these days.
[2025-6-23. : 10:52 pm]
Ultraviolet -- dumbducky
dumbducky shouted: "almost ten years old"
5+5 also = 10. Are you sure your mobo doesn't have the m.2 port for an NVMe drive? My previous mobo which would be about 10 years old at this point had one
[2025-6-23. : 10:43 pm]
NudeRaider -- NudeRaider
NudeRaider shouted: dumbducky There's always a risk, sure, but I wouldn't actually expect it unless you ran a server on it or something. They are way more durable than HDDs.
my Samsung 830 from 13 years ago is still working, though not being used much anymore, admittedly.
[2025-6-23. : 10:39 pm]
NudeRaider -- so you should be thinking about a backup, not a replacement.
[2025-6-23. : 10:39 pm]
NudeRaider -- dumbducky
dumbducky shouted: Attention nerds: my old SSD is almost ten years old and probably at risk of dying in the next year, I assume. What's a good 2.5" SATAIII replacement as cheap as possible? Must be at least 250GB (do they make them that small still?)
There's always a risk, sure, but I wouldn't actually expect it unless you ran a server on it or something. They are way more durable than HDDs.
[2025-6-23. : 10:36 pm]
NudeRaider -- dumbducky
dumbducky shouted: Attention nerds: my old SSD is almost ten years old and probably at risk of dying in the next year, I assume. What's a good 2.5" SATAIII replacement as cheap as possible? Must be at least 250GB (do they make them that small still?)
a mainboard that old will need replacement in the foreseeable future anyway, so for 11 Bucks you can add an m.2 port to it and get an actually good SSD that you can take over to a new pc.
[2025-6-23. : 10:23 pm]
Moose -- There are cheaper ones but I don't know the brands tbh
[2025-6-23. : 10:23 pm]
Moose -- Kingston A400 240GB ~$28?
[2025-6-23. : 10:20 pm]
Moose -- WD Blue 250 is $40, that would probably meet "good" but not "as cheap as possible"
[2025-6-23. : 9:15 pm]
dumbducky -- "almost ten years old"
Please log in to shout.


Members Online: Sie_Sayoka, Roy