Is there any way to cloak a unit permanently without the use of an Arbiter? I want to cloak a Carrier .. .

Some units, yes, but cloaking Carriers causes a crash. Afaik, the only air unit you can cloak is an Interceptor.

You can try disable doodad state. If that crashes your map, then I don't think so.

Try looking through this site's information, I believe there is a chart somewhere that shows which units can be disabled without crashing the game.

I did this:

Condition:

Always

Trigger Actions:

Disable doodad state of Gantrithor (Carrier) for Player 7 at location 'Follow Boss'
Preserve Trigger.

It crashed when I did that, will enable cloak it as well?

If it crashed, then to the best of my knowledge you can't. Sorry :C

Nevermind, enable doesn't work either. You said the only Air unit I can cloak is an interceptor? How do I keep the interceptor from being destroyed if it has no carrier? They always get destroyed when I make them..

http://www.staredit.net/starcraft/Cloaking
Use the wiki. While you're at it, update it to include anything else you find.

Post has been edited 1 time(s), last time on Jun 9 2010, 7:46 pm by rockz.

Well I can't cloak a carrier, but I guess an interceptor would be fine. How do I keep the interceptor from being destroyed though as if I put it on the map by itself?

You can't, you have to have a carrier off-screen with the interceptor under its control, the interceptor with constantly try to fly back to the carrier at high speeds. The MoveUnit Trigger should work just fine though. What exactly are you trying to do?

Nothing really I just had an idea. Originally I wanted a carrier and I wanted my boss level to have a cloaked carrier at first but you can't make those without Arbiters. Hmm, and you can't make a cloaked Arbiter to Cloak the Carrier either.. grr.. My entire game plan is ruined .. .

You can make an invisible arbiter. Not cloaked, invisible. I don't remember how to do it, but it had something to do with changing the unit ID or something like that. It made a model-less arbiter; you couldn't click on it and you couldn't see it (there's no blur) and it has a cloaking field. If the topic is still there, you can try to find it. I think it's hidden somewhere in the ums assistance or theories and ideas forums.

If it was in UMS assistance I'd know about it, so it's probably in another forum. Also could you please try to dig it up sticky? It's much easier to find something when you know the thread.

the unit id was somewhere in the 4XXX. I remember a korean map using it with drones and stacked (disabled, i think) marines, and a muta.

I have read about being able to place "arbiter cloaking fields" on the map using an extended unit ID that was apparently patched back in 1.13 or 1.14. Are you perhaps talking about that, or does your arbiter cloak trick work in 1.16?

Oh man, I think I got it! But you can't move it anywhere!

1. Open SCMDraft2 and place any unit, anywhere on the map. The cloak field acts like an Arbiter's, so place the unit for the player you want the cloak effect for.
2. Open its properties.
3. Change its unit ID to 4136.
4. Done. Save the map, test, and watch as any units brought close cloak, and decloak when they are moved out.

Is there any way to create this effect using the Create Unit With Properties? That way I can spawn this unit I.d where I want when I want?

EDIT:
Well, I'm trying this Unit ID it's not working either. Nothing happened, you change unit ID and it turns into a Marine.. It doesn't cloak any units I put next to it, and it doesn't cloak any buildings either.. This was just information I got from another site.. Fucking Google..

Post has been edited 2 time(s), last time on Jun 10 2010, 1:15 pm by LaZyMiCro.

Extended units are very patch- and operating system-dependent. What happens is that the game sees the unit ID and tries to read its data. But, obviously, there is no data for that unit, so what it does instead is read where it would be if it would be if it existed, which is some other part of the system memory (usually the game's memory - idk if you could read outside the game's memory without getting a GPF). Now, each patch changes the mapping of the game's memory, meaning that the effects of the extended units change from patch to patch.

Or, maybe they patched it so that extended unit IDs are just set to 0, which would turn them into Marines.

Seriously, they patched it? I was wondering why I could never get that thing to work...

Why does Blizzard always "fix" all the cool stuff we find?



Anyways, there's a way to order interceptors, but I don't remember how to do it. I think it's in Falkoner's Test Compilation. Ah, yes, I think this is it (attached).

Attachments:

Awesome thanks, my final level is a Carrier, commanding interceptors would be great! I'm making a Space Invaders Map.. I've only been working on it since Monday June 6th, 2010. Not even in Beta Testing yet, but when it is I will post the Beta version on the site to get some feedback on the map.

Here is a screen shot of it on Scmdraft2. Click on it to expand the view. What you think .. o.o? Thank you for the tutorial by the way for the interceptor. That is awesome I will definitely use this for the shield generator on my "Ship" for my Carrier Boss. Can You make a unit warp to a "Random" location on the map or does it have to be entered in the Triggers?



Post has been edited 5 time(s), last time on Jun 10 2010, 10:03 pm by LaZyMiCro.

You can only center locations on units and you can only "warp" (I guess you mean teleport) to locations, so you have basically 2 options:
- You have a lot of invisible units preplaced and move to a random one
- You make the unit you center on move randomly across the screen using junkyard dog or randomly between a couple of fixed locations.

Actually there's a 3rd option but I don't recommend it since you need many precious locations:
Just preplace a lot of locations randomly across your map and move to one of them at random.

If you have trouble with the actual randomization you should read the article on randomization in the wiki.

As NudeRaider said, using invisible/burrowed units is a good way to go, that's how I'd do it.