Talk:PRIM TEMP ON REZ

Is there a way to gage when the next garbage collection will be or how many temp prims are used up or allowed? In fact there is a great deal of info needed to run a nice temp rezzer on any region. Is that info available from somewhere? -- Eddy ^{(talk|contribs)} 11:01, 12 June 2009 (UTC)

It's complicated and I don't know if what I know is still current. llGetParcelPrimCount can tell you how many temp prims are on the parcel. "Nice" and "temp rezzer" don't go together well. Temporary is designed to be sufficiently unfriendly that you aren't supposed to want to abuse it get around parcel prim limits. Rezzing objects causes lag, deserialization is expensive. -- Strife ^{(talk|contribs)} 20:01, 12 June 2009 (UTC)

Would you then say that rezzing prims with the express purpose of doing a job and dying almost immediately would be considered "bad form" by LL? By "deserialization" do you mean the fact that each new thing has to have a key assigned? -- Eddy ^{(talk|contribs)} 20:05, 12 June 2009 (UTC)

Your example would be considered good form. There are those who repeatedly rerez the same thing so they can get more prims on their property... which is bad form. By "deserialization" I mean getting the scripts in the object up and running. -- Strife ^{(talk|contribs)} 20:44, 12 June 2009 (UTC)

Thanx again Strife. You're a great help to me and all the users of this wiki. I'm working on getting the script(s) (on_rez) down to a minimum but I guess that even that can be a pain in the regions back side. If I manage to get the thing working I would love your opinion on the "decency" of it as a scripted device. Honestly if it turns out to be a Bad device I will chalk it up to experience and scrap it (even if it does work). You were of course right about llGetParcelPrimCount(). Thanx. -- Eddy ^{(talk|contribs)} 20:52, 12 June 2009 (UTC)