Our letter to Valve, part II

I'd like to mention that you can't change or scale the explode sprite in the explode point entity.
Doors that can force open as well as close.
Built in water effects (like moving water that pushes a player and look like it flows)
Allow more points on cylinders and spheres (if possible fix crashing when carving)
If not too difficult, a face detailing tool to help with texture blending and detail (like you could split a face into different texture areas but still be one brush)
Working ladder options
Class, player and weapon editing entities (like giving scouts more maximum health, or more ammo for a gun)
Parenting for everything
Ability to delay hurting a player (a delay for trigger_hurt?)
Maybe a trigger_timer_area (for timing how long something has been in an area)
Maybe a trigger_counter_area (counts all activators inside, flags for clients and phys objects)
Custom HUD with custom variables (including timer placement or multiple timers or player names)
All I can think of for now...

Delays can be accomplished through the outputs tab; pipe to a logic entity if necessary.

Has this letter been sent yet? I think it needs to go out soon if not. Sitting around rehashing this letter isn't going to get anything addressed, and while I understand and agree that the letter should be reviewed to request important and easily implementable changes, we can always send another one next month reiterating what we want.

zbandito said:

Delays can be accomplished through the outputs tab; pipe to a logic entity if necessary.

Click to expand...

No because if a player enters a trigger_hurt it only hurts when the player is in contact. And there is no output that says "Hurt Player" (which was one of my suggestions) Add and remove health doesn't work.

Hm, can you name the player when they enter a trigger_multiple, have it spawn a trigger_hurt entity and set it's parent to the player name? Just a thought.

I don't know if these are possible but it would be great:
allowing the combination of entities
adding properties of other types of entities to another
player tracking entities (and various other detectors)
be able to differentiate between cloaked and disguised spies.
triggers on various stats of a player

zbandito said:

Hm, can you name the player when they enter a trigger_multiple, have it spawn a trigger_hurt entity and set it's parent to the player name? Just a thought.

Click to expand...

I don't know how to name a player, but thats overly complicated, I'd rather have a delay on the trigger hurt...

EDIT: I am too late it appears, since there is a topic Valve has replied!

I hope you have not sent it out yet.

func_regenerate need to have a disable sound or custom sound option.
or/and SetAmmo/SetClip1 player variable.

The Player:SetHealth entity needs to be documented or added to the via this entity list for player. This function currently works, but is not documented. (Trigger Multiple, OnTrigger, Target: player, via this input: SetHealth, with a parameter: 400)


Player class filtering should be moved to #1.


Fire was in one of the later posts, but it needs to be added, not just particle effects or smoke stacks like suggested by other players. Fire does not render but can damage a player, but not ignite them.

senturies and destructiables need to be about to have an onDestruct/onKill/onZapp event/output when using obj_sentury.

Just a comment, but for the "nogrenades" thing...couldnt you just make a func door and not have it activated ever?

More Hud control with controlpoints for PL and normal CP. (AKA let us enable/disable control points on the hud, so we can keep the hud less cluttered)

A tf_projectile_rocket entity would be nice... since they were so kind to put in Obj_dispenser and Obj_sentrygun entities, im hoping its an easy add.