Thanks for the update Kerry! I'll start testing ;)

Awesome, thanks Kerry!

Awesome! Thank you very much...

EDIT: Any news on netprops and ChangeLevel()? Is it fair for me to expect them?

I wouldn't plan on netprops - it'll take a significant amount of engineering to make that work well from script. As for ChangeLevel, it's non-trivial due to all the different meanings that a level transition can have in L4D2 (continuing, new game, restarting rounds, team swaps, etc.) but we'll try to work out a general enough solution that would actually be useful.

What about being able to spawn more than 4 "normal bots" (not invincible bots) in a map?

https://steamhost.cn/steamcommunity_com/groups/L4D2WSVB/discussions/0/810923021697866291/

Would being able to iterate/read keyvalues from entities as well as read them be a more realistic possibility?

Also, is there any way to get the custom HUD to resize elements like the stock elements do? People playing on low resolution have all the fonts clipped off

Okay, thanks Kerry. ChangeLevel() would let us do some awesome things. Zelda-style maps for example. Players can gather around a store's door, one guy "uses" the door, and the map changes to the campaign's store map. All we need to do is pass the return location and map name via SaveTable(). This even lets us to re-use maps from other maps-- kind of like "modular" mapping. What's fantastic is that if I wanted to create an _enormous_ map (like in Skyrim), I can break up the map into visible chunks and transition players between different maps-- essentially creating one giant world. My friend also wants to use ChangeLevel() for his Half Life 2 -style map where maps transition without saferooms.


More function ideas...

- z_spawn auto (instead of specifying position, let the director pick out the pos)
- Fake client command (non-networked / server executed)
- Emit sound
- Drop spit at location
- Drop molotov at location
- Vomit on player
- Bile player
- Respawn player (i.e. CTerrorPlayer::RoundRespawn)
- Defib player
- Revive incapped player
- Set black/white count
- Set glow color
- Set player movement speed (currently we can "slow" players down by setting the friction kv, but can't speed them up)
- Get entity owner (netprop m_hOwnerEntity)

... and I have a lot more if you want lol.

My friend says he would appreciate:

- Spawn bots
- Kick bots
- Change player model

Guess I know what I'll be doing over the holiday weekend...

Originally posted by Kerry:

Guess I know what I'll be doing over the holiday weekend...

I will love you forever... no homo lol.

I have a unit test folder with a distribution of simple time-profiled cases. If anything seems to take more time than it should, I'll be sure to post a bug report, although it may take awhile for me to get back to you on the updates (I'm a freshman in college-- I'm 19-- and taking summer school b/c of my accelerated medical track).

Originally posted by Kerry:

Guess I know what I'll be doing over the holiday weekend...

We appreciate your hard work Kerry. Looking forward to more functions!

Have a great holiday.

Looks like Squirrel is using 8-bit ASCII characters. Would it be possible re-compile with SQUNICODE[www.squirrel-lang.org] defined so we can use international characters like ñ in the HUD?

Two more suggestions.
A function to tell if a entity is ignited.
A bigger one but which has a ton of possibilities for new modes/campaign. A generic npc, basically something like npc_citizen.

You could see if the damagetype == 2056, although I'm not sure if that is a characteristic of molotovs too (fire damagetype == 8, ignite/burn is 2056). There's also zombie_ignited, but that only fires for zombies I assume.

But yeah, a way to get the entity's flags would be wonderful. That'll also enable us to detect FL_INWATER, FL_ONGROUND, and FL_DUCKING too.

Originally posted by shotgunefx:

A bigger one but which has a ton of possibilities for new modes/campaign. A generic npc, basically something like npc_citizen.

Interesting suggestion shotgunefx. This would be useful to support non-survivor NPC's as well.

I was always wondering about something like an info_l4d2_survivor_spawn entity, that would only work in L4D1 survivor maps if the mission file had "survivor_set" set to "1". It would function the same as the info_l4d1_survivor_spawn, but it would instead spawn the L4D2 survivor bots helping the L4D1 survivors. Like a reverse of The Passing Port.