Talk:Point template

I can't understand one bit of this entitys description. What's an interdependancy? How will it change the name? Why? What goes where and how's who what for? --Andreasen 03:07, 7 Apr 2006 (PDT)

This makes complete sense...it's saying that all connections still work when they're recreated—ts2do 14:17, 7 Apr 2006 (PDT)

Fixed is usually a reserved word (in the programming world) that means that the value is immutable. I think you should say redirected or renamed. At least clarify what "fixed" means. --Molaughlen 20:04, 28 May 2008 (PDT)

Looks like point_template can't be in hierarchy with another point_template. Tested in HL2. --FaTony 18:22, 8 Sep 2008 (PDT)

No it can.--Gear 17:12, 9 Sep 2008 (PDT)

Huh, child spawns automatically, but it shouldn't. And if I kill it, it doesn't spawn anymore.--FaTony 22:12, 1 Oct 2008 (PDT)

Ending targetnames with a number will bug out the template

I just tried to spawn a point_template with an entity assigned to it that ended with a number. It effectively generated an error in the console with all data etc... and it was fixed by removing the number from the entity. I will add this as a bug so people are aware of this, should they ever try to do it or encounter the error. --JorisCeoen (talk) 20:36, 2 July 2017 (UTC)

Using Parameter Override box

Tested in TF2: the name fixup will not change anything in the parameter override box. Paraphrased from console:

   (22.80) input relay&0014: train.SetParent(templated_entity)
   Entity func_tracktrain(train) has bad parent templated_entity

As can be seen, the output is trying to use the "base" name instead of the fixedup name.

(Pd) (talk) 01:29, 23 March 2018 (UTC)