Anonymous | Login | Signup for a new account | 2025-07-27 13:59 UTC | ![]() |
My View | View Issues | Change Log | Roadmap | All Projects Issue Support Ranking | Rules | My Account |
View Revisions: Issue #2119 | [ All Revisions ] [ Back to Issue ] | ||
Summary | 0002119: Server doesn't inform the client of actor TIDs with ACS Spawn/SpawnSpawn functions | ||
Revision | 2015-03-09 20:52 by cobalt | ||
Description | When spawning an actor with Spawn() or SpawnSpot() in ACS, one of the parameters you can pass is the "newtid" parameter, which automatically assigns the newly spawned actor the given TID. However, this TID is not sent to the client, and if used in any clientside scripts, ACS functions will behave as if the TID doesn't exist. A workaround is to immediately call Thing_ChangeTID(newtid, newtid) after using Spawn() or SpawnSpot(). I've confirmed that this does inform the client that the actor has the new TID. |
||
Revision | 2015-03-07 16:11 by haxmurderer | ||
Description | When spawning an actor with Spawn() or SpawnSpot() in ACS, one of the parameters you can pass is the "newtid" parameter, which automatically assigns the newly spawned actor the given TID. However, this TID is not sent to the client, and if used in any clientside scripts, ACS functions will behave as if the TID doesn't exist. A workaround is to immediately call Thing_ChangeTID(newtid, newtid) after using Spawn() or SpawnSpot(). I've confirmed that this does inform the client that the actor has the new TID. |
Copyright © 2000 - 2025 MantisBT Team |