Talk:Info null: Difference between revisions
(Created page with "== 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 t...") |
(→workaround: new section) |
||
| Line 1: | Line 1: | ||
== code fix == | == 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. [[User:Nescius|Nescius]] ([[User talk:Nescius|talk]]) 09:58, 29 June 2024 (PDT) | 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. [[User:Nescius|Nescius]] ([[User talk: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 --[[User:Nescius|Nescius]] ([[User talk:Nescius|talk]]) 16:49, 14 March 2025 (PDT) | |||
Revision as of 16:49, 14 March 2025
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)