SC2Mapster

All it needs is the right footprint. Problem is footprints are direction specific. It is the same principle as making a bridge doodad that spans multiple cliffs. Guess you will require a placement footprint that on the one layer requires a cliff for placement at a specific orientation.

There is a footprints editor in the data editor. No need for XML anymore since they fixed the bug which broke the footprints editor.

Just make a building unit under the Units data type and give it a footprint in the Movement: Pathing Footprint field that has a pathable region that extends at least one square of the smallest division over the edge of the unpathable part of the cliff and covers the whole unpathable part.

The footprint cannot affect the Z height so the unit would go like a colossus of being at the base of the cliff and then suddenly increase in height. Some models introduced in HOTS have a property that any unit walking over then has the height of the actor raised to be on top of the model. There are some stair doodad models with this property and several of the HOTS campaign platforms including the Invisible Platform model. Just have one of those with 0 opacity placed at the right incline to give the impression of the unit climbing up the ramp.

Your last question would be possible using a Region actor that uses a Query Persistent event action that uses a Query Response actor to send a Signal event action to your Query Director (casting actor that created the Region actor). Have two regions offset using a SOp(Local Offset) SOP on either side of your Unit actor that if it detects another actor with the correct Alias (eg. _Burnable is used for the tree killer) it sends the signal which can then be used for your connection visuals. You could even have animations of the parts connecting together is you wanted to make the effort.

Would also work for those made by the player.

I would advise looking at the Char Doodad Anim Monitor actor of the Char Weed doodad as an example. Like all actors with the event actions make sure you are referencing the correct target actor. Also the Char Doodad Pop Up/Down actors which are the Query Responses. Sorry got a bit confused as to what field the query director selection had to go into.

In short what you want to do is get your main Unit actor to create the Region actors at offsets to itself. These regions then use a Query Response actor to detect if there are any other ramp unit actors nearby (make sure the regions are not detecting the creating actor just through the offset). This query response sends a signal to the director. The director (the Region actor) then sends a signal back to the ::Creator or just does the visual affecting event actions itself).

Signal event actions send a signal to a target which needs to be specified. This is picked up by a Signal event under the events of the target actor. This then does what you want.

I would just get the Unit actor of your wall unit to create the region actors.

You could also get the query response to send the signal to your unit actor directly.

Unlike doodads who can use a footprint under the actor, the footprints of units are determined by the unit itself and not the actor. To change the footprint would require your unit to morph into another unit with a different footprint (like a gate). Doodads also have a problem that their footprint is permanent even if you destroy them so are not suited for dynamic change. As you are just painting pathable terrain over otherwise unpathable terrain if you design your footprints correctly that they overlap in the right way there should be no need to change the footprints.

Use the Actor Creation event to use the Create action and then specify what actor to create.

Everything to do with actors doing something involves events.

For your regions use the Actor Creation event to use Query Persistent actions.

Actually they only make a call when there is a change in state.