Tweet
Spike just a note on R5 ----
The automatic misc_model idea is awesome, obviously.
Now comes the part where you hate me ...
For a pure effects carrier, it should probably be func_illusionary ...
{
"origin" "430 574 24"
"model" "" // Hi, no model! Non-supporting clients will ignore me!
............ // And the server will just discard me as a static ent with no model index
"classname" "func_illusionary"
"emiteffect" "flame.firey_fire"
}
With the phony misc_model as simply an effects carrier (no model), in a non-supporting will print "no spawn function for" in the console in a non-supporting engine in single player.
But if it is called func_illusionary, it won't print a message. And because it has no model, it basically doesn't even exist (I don't think the server even communicates it in the signon buffer because it shouldn't have a model index). So it will gracefully degrade in a non-supporting client.
Anyway, one thought. Right or wrong.
The automatic misc_model idea is awesome, obviously.
Now comes the part where you hate me ...
For a pure effects carrier, it should probably be func_illusionary ...
{
"origin" "430 574 24"
"model" "" // Hi, no model! Non-supporting clients will ignore me!
............ // And the server will just discard me as a static ent with no model index
"classname" "func_illusionary"
"emiteffect" "flame.firey_fire"
}
With the phony misc_model as simply an effects carrier (no model), in a non-supporting will print "no spawn function for" in the console in a non-supporting engine in single player.
But if it is called func_illusionary, it won't print a message. And because it has no model, it basically doesn't even exist (I don't think the server even communicates it in the signon buffer because it shouldn't have a model index). So it will gracefully degrade in a non-supporting client.
Anyway, one thought. Right or wrong.
Comment