2) Thus with that, it is possible to create some "map loader" map that can be opened in the editor and loaded via "Test Document". Said "Map loader" can be loaded in the editor from any path location.

This is probably the best way for campaign makers to have a campaign that does work the closest as conventionally done, without publishing while greatly minimizing the lack of publishing's drawbacks.

Also I apologize to Meta for sending a bit of a false information as I didn't understood it too well myself unless I truly found out myself. I honestly expected Blizzard would enforce publishing campaigns in every method possible.

Also posted some map test files about it as an attachment below.Step 1) Extract all 3 files in C:\Program Files\StarCraft II\Maps (or whatever the equivalent on your OS)Step 2) Open the map "Test - Test - Next Map - Menu Loading.SC2Map" in the editor and hit "Test Document" in the first menu.Step 3) If you did Step #1 correctly, it will transition to your chosen map correctly.

EDIT :To make it more obvious for Step #1, the path is NOT the usual path where maps are saved. That's where most people would make the mistake.

As I poked in the editor, one of my project needs is to have at least specific unit-types to convert its actor, model, sounds, etc. to an existent one. This is mostly intended for "on-the-spot customization during gameplay" of units.

In all honesty, having 25+ unit-types just to allow 25+ different actor looks is a lot of waste of time.

Unfortunately, catalog triggers are mostly barred to do it in details. However, there is still a reasonable way I found around it ...

The drawbacks :1) The base unit-type's trained sounds will be heard regardless of the unit to convert to. This is since the triggers only work after the unit itself is present. Also odds are, you will see whatever previous model briefly before your triggers kick in.

Fortunately for the base unit-type, you can probably use a model size of 0.01 model scale to make it barely seen

2) Due to an odd glitch for wireframes, you are basically forced to do a single actor switch to all units of the same unit-type you want to use to convert if you want to avoid this issue.

3) When the "modified" unit's actor dies, you hear both the previous actor's dying sound AND the current actor's dying sound.

So you will have to manually remove the dying sounds references from the base unit-type you want to do this to avoid this issue.

Ultimately due to the issues above, odds are you will have to make a dummy unit-type (still with some sort of actor and model).

There's a "model swap" actor command, but of course it only changes the model, not the actor.

I wonder how well the map transition works in multiplayer, particularly regarding player order. It could in theory be possible to make a "map lobby" where a chat command would load a specified pre-downloaded map, but setting up games like this would not be feasible for the vast majority of bnet players due to there being no chat channels.

So I tested it quickly and I found out that the Reaver doesn't attack at all. I believe the buff to raise or drop its movement speed is bugged as well.

Another weird thing I noticed is that the Swarm Guardian somehow have 275/200 life (and in blue as well but I guess it's due to the lack of wireframe.)

Other than that, I noticed you made some triggers in a library inside that mod. Are any of them required for specific units if I merge your mod into my Warlords & Merchants SC2 map? It doesn't seem to be the case at first glance but I rather be sure.

EDIT : As a side thing, adding a simple map linked to your mod with all added/modified units on the map could help "selling" your mod out for other persons to try. Preferable to add some dummy enemy foes and buildings to allow testing the abilities that absolutely require an enemy target to use.

Ricky_Honejasi wrote:Other than that, I noticed you made some triggers in a library inside that mod. Are any of them required for specific units if I merge your mod into my Warlords & Merchants SC2 map? It doesn't seem to be the case at first glance but I rather be sure.

They aren't used for anything in the mod itself, although the drop pod triggers really need the Campaign drop pod trigger to work correctly.

EDIT: Updated with test map and fix for Reaver. Although I don't know what you mean by the Reaver doesn't attack...

So far, the only thing I still notice is the Reaver's movement speed doesn't change depending if it is making scarabs or not (due to a visible buff that implies that it should change).

But ultimately, that's a rather minor detail as far I am concerned.

Oh, it does. It's a lot more noticeable when you have one Reaver building and one Reaver not.

There's two other annoyances I have with my current implementation-- the Scarab doesn't do random angle turns, and the Reaver will still acquire targets even when it's unloaded. Although... to be fair, the Carrier also does that with its interceptors as well, so it may very well be a purposeful behavior (even though it's clearly different from the Starcraft 1 behavior). I'm sure there's a way to fix that, but I'm not thinking about that at the moment.

I will probably test more at a later date and I plan to do merge your mod into my W&M map in the near future.

There's no need to do any merging, really. You just add it as a dependency and never have to worry about updating mutliple Mod files in parallel. All that would have to be changed is the dependency and that can be done independent of the map (which is how the Reaver weapon fell through).

ED: although I think it's actually possible that my mod contains words censored by Battle.net... one of the skills in the mod is called 'Deathstream' and I heard 'death' is censored.

RazorclawX wrote:There's no need to do any merging, really. You just add it as a dependency and never have to worry about updating mutliple Mod files in parallel. All that would have to be changed is the dependency and that can be done independent of the map (which is how the Reaver weapon fell through).

ED: although I think it's actually possible that my mod contains words censored by Battle.net... one of the skills in the mod is called 'Deathstream' and I heard 'death' is censored.

Normally I would feel that a merging would be necessary but since Blizzard was nice enough to increase the number of maps/mods per account to 10, I can afford to take an extra slot for your mod separately.

Although, ill do some minor specific modifications to fit W&M's use since I already implanted some stuff differently that could come in conflict with your mod. For example, the Lurker is already in with a different method (basically the "Lurker Aspect" SC1 way vs your Hive requirement to transform).

Ricky_Honejasi wrote:Although, ill do some minor specific modifications to fit W&M's use since I already implanted some stuff differently that could come in conflict with your mod. For example, the Lurker is already in with a different method (basically the "Lurker Aspect" SC1 way vs your Hive requirement to transform).

The dependencies are kind of interesting in that it takes whichever one is listed first over the other ones, with the map itself being on top of all of them. Although I did get the feeling that modifying default units would inevitably cause a lot of things to turn out like that. Since I also expect the cut SC1 units to come back I tried to avoid naming things in an obvious manner in reference to them.

By the way, have you had problems with being unable to cancel a Lurker morph? That's one of the things I've had problems with in the morph's default loadout.