One more though ... for generalizing mutations without having to spec them to a specific map, having some way of retrieving a spawn point in the flow would be nice.

ex: spawn_at <- GetSpawnPosition(SPAWN_IN_FRONT_OF_SURVIVORS, 1000); // returns null if it fails

Maybe a way of ascertaining flow relative to survivors for any given entity as well, Something like...


So for instance , say you wanted to randomly spawn things behind doors, you could loop through the prop_door_rotatings, collect the ones further in flow (IsAheadInFlow) then use GetSpawnPositionFron on the door to make sure you spawn behind it, Of course it would be helpful to know if the door was open, unlocked etc.


Also, the code from the previous post in code tags. I guess I should have read the formatting help. Too bad we can't preview posts

Well, you asked for it ;)

Off the top of my head, I would have liked to have seen some Director hooks along the lines of EnvEntityMaker


OnSpawnSpecial(type, props)
OnSpawnCommon(props)

Both could modify the table of parameters. So you could transmute the type (like ConvertZombieClass) but also change any of the entity properties such as health, speed, model or skin. Returning null would cancel the spawn. I know some of this is do-able in the new mutation system but I don't know if it works in non-mutation modes.

I don't know if you can actually modify individual commons as I know they are somewhat of a collective entity but as an example


DirectorOptions -> {
function OnSpawnCommon(props){
// vary common speed and health
props[health] = props[health] + RandomInt(-10,10)
props[zspeed] = props[zspeed] + RandomInt(-10,10) // I just made up zspeed but I digress..
return props
}

function OnSpawnSpecial(etype, props){
TankMdls <- [
["models\infected\hulk.mdl", 0 ],
["models\infected\super_tank.mdl",2000]
];
if (etype == ZOMBLIE_TANK){
// spawn a tank or super tank
local tanktype = RandomInt(0,1);
props[health] = props[health]+ TankMdls[tanktype][1];
props[model] = props[health]+ TankMdls[tanktype][0];

}
return props
}

}

Great update. Still diving in, but some quicks thoughts based on what people have asked for help on over the years and things I’ve wanted to do myself that I think would be helpful for mutations but also custom campaigns.

FYI These appear to be undocumented...
.IsSurvivor()
.GetActiveWeapon()
.GetZombieType()

Things that would be really useful to have

.IsPlayerIncapacitated()

Some way to distinguish between real Health, Real vs Temporary
GetRealHealth() // returns actual health regardless of temporary health. Also maybe SetRealHealth(num)

.IsDead() // would be nice though this could be derived from (player.GetHealth() == 1 && !player.IsPlayerIncapacitated())
.IsGhost()
.isHangingFromLedge()

CDirector::HowAngy () // returns a value between 0-1

CDirector.GetMaxSurvivorFlow() // returns the total flow to the saferoom/rescue instead of hard coding it per map like the bridge gauntlet

Something like nav_flow_target that doesn’t affect scoring so we can make survivors go to places off the flow or in a non-linear fashion. That or have the nav_flow_target’s original map spawn location used in scoring regardless of where it’s moved to when recomputing flow. Currently directing flow this way breaks scoring as the first target aquired they get 100% travel

Input to make a bot move to location of caller. Similar to nb_move_to_cursor

Input to make a bot attack caller.

Something like TraceLineTraceLine(Vector, Vector, handle) from Portal’s vscript. Right now it’s virtually impossible to interact with the world dynamically.

The ability to read entity KeyValues would also be nice

Apologies, I forgot how terrible Win file searching was.

Excellent!. Quick question, I don't seem to have export_entity_group.pl anywhere under my Beta install

Has anyone else noticed disabled addons getting removed then re-ninstalled, re-enabled?

It's doesn't appear to be every game launch or exit. I'll disable some vpks, the addonlist.txt will have "0" for them, then at some point they get removed both from the addonlist and deleted from addons\workshop, then next game launch, they get re-installed and all enabled again.

I've had it happen I'd guess about six times now but I can't figure out the exact sequence that triggers it

Suggestion: Group Visibility for Workshop Items
Seems like it would be handy for developing maps. Start a private group, invite the people you want to playtest it. Thoughts?