Talk:Info null

code fix

I don't understand the point of that code fix. You are basically just removing the entity. At that point can just add random entity name to the fgd to achieve the same result. Nescius (talk) 09:58, 29 June 2024 (PDT)

workaround

That workaround is flawed. How is not spawning the entity at all a good workaround to this entity being an edict ? If someone is using it to aim lights they can use info_lighting to avoid the issue. If someone is using the vscripts keyvalue to load some script then not spawning the entity would break that. If someone is using it in point_template for whatever reason than again not spawning the entity may cause some issues. Or if there is some other entity that is taking a target and only were to read an origin of info_null during spawning then not spawning the info_null at all would also break that. I did list some very rare cases but the workaround itself is for something that would very rarely cause issue too so it would be better to just remove it instead of bloating it with potential issues --Nescius (talk) 16:49, 14 March 2025 (PDT)

If someone is using it to aim lights they can use info_lighting to avoid the issue.

No, they can't, because VBSP deletes the entity before VRAD has a chance to use it. info_lighting is exclusively for overriding static prop lighting/cubemap origins.

If someone is using the vscripts keyvalue to load some script then not spawning the entity would break that.

Why would they use info_null instead of worldspawn or logic_auto?

If someone is using it in point_template for whatever reason than again not spawning the entity may cause some issues.

Again, why info_null? It usually gets deleted before it can be used to orient anything.

Or if there is some other entity that is taking a target and only were to read an origin of info_null during spawning then not spawning the info_null at all would also break that.

That'd be a very poorly coded entity, then, because depending upon the placement of the entity and the info_null in the entity lump, the info_null may either not exist yet, or already be killed by the time the theoretical other entity has a chance to read its origin.
— SirYodaJedi (talk) 18:23, 14 March 2025 (PDT)

Didn't realize info_lighting can't do that. Would be good to add warning about that on info_lighting page. Still feels very icky the way the workaround is worded so instead of "changing this entity's classname" as a workaround a better solution would be simply adding non-existent entity to fgd and using that instead to point lights --Nescius (talk) 19:34, 14 March 2025 (PDT)