Does anyone know how to keep dead bipeds from disappearing from a map after about 15 seconds? I have placed several around a map I am modding, but after about 15 seconds, they vanish.

The words "garbage collection" keep coming to my head.
I dunno where to look but i think its something to do with garbage collection.

Something like this... uh.... is this in multiplayer? If so, there's a slim to none chance of being able to change this. If it's singleplayer, the bipeds should stay there until collected by script. So yeah, which is it?

multiplayer...

Yes i have the same problems, I posted many threads about my problem, and no one answers ¿Whats wrong with this forum?

I don't know whats going on. It's seems more difficult to get scripting help than it was just a few months ago.

This isn't a scripting issue. Garbage collecting is natural for multiplayer, and I see no way to delay that.

A solution would be to convert these bipeds to scenery models, so they wouldn't be collected. I have yet to learn modeling, so I don't know how easy that would be.

Yeah since this is multiplayer, it automatically collects garbage. You would have to make a scenery, like noobyourmom said.

Is there some way to script them to remain in the location their initially placed in?

You could continuously create them anew, but that would be both inefficient and wasteful, particularly if there are multiple bipeds. The best solution would be to create the dead bipeds as scenery.

This. Plus what you could do is have those scenery objects attach to a dying biped and detatch (in a script), then have that dead biped be destroyed when dead (in guerrilla). This would create a dead body where a specified biped has died (does not work with generalized encounters).

Or add it into the death effect. However, this is not necessary if you only want the bipeds that were placed initially to remain.

After quite a bit of experimentation, I just found that this actually works in multiplayer maps:

(script continuous create_blue_deadmarines
	(begin
		(object_create_anew blue_deadmarine1)
		(object_create_anew blue_deadmarine2)
		(object_create_anew blue_deadmarine3)
		(object_create_anew blue_deadmarine4)
		(object_create_anew blue_deadmarine5)
		(object_create_anew blue_deadmarine6)
	)
)

They remain in the map where initially placed!

Add a sleep 150 to the end of that to reduce lag.

What I said still stands. Sure, it might work, but it has the potential to cause heavy lag for lower end computers.

Reduce the lag, yes, but you're merely delaying the inevitable. It will still lag on older computers, just on 5 second intervals. Object creation is not perfect, especially not with this netcode.

Since they were disappearing at around 15 seconds, I added (sleep 400) to the script to decrease the number of create_anew increments.