i thought to release

!next or !saveme

when u stucked somewhere

it changes your position to next respawn position

without killing

that kind of code can anyone help me ?

Don't copy itsmods again.

Anyway it's not possible yet... wait for an update to teleport in the API

NTA posted an update in the NH9 thread that contained a bunch of entity related commands (moveto, clonebrushmodeltoscriptmodel, etc.) Should be coming soon or just copy it from there and compile your own InfinityScript.dll.

Can't you just SetField("origin", [Vector3]), possibly reading all mp_dm_spawn entities?

NTA, self.origin doesn't work properly (atleast in mw2). Just use the function SetOrigin.

NTA, self.origin doesn't work properly (atleast in IW4). Just use the function SetOrigin.

hm, seems correct - PlayerCmd_setOrigin seems to be specialized to players, uses the playerstate struct in addition to the entity state and does UnlinkEntity as well; just like TeleportPlayer.

 

odd, however, that writing to origin on a player entity doesn't cause a script error.

odd, however, that writing to origin on a player entity doesn't cause a script error.

The entitiy's origin field will get overwritten by the PlayerActor's (playerstate) origin again so the game doesn't really care.

odd, however, that writing to origin on a player entity doesn't cause a script error.

The entitiy's origin field will get overwritten by the PlayerActor's (playerstate) origin again so the game doesn't really care.

the only mention of 'playeractor' regarding MW3 I've found seems to be the gentity's 'client' field, which is actually a gclient_t (though in Q3 gclient_t seems to start with a playerstate_t, so I guess it's somewhat right)

 

for reference, the playerstate is the data that only gets synced to that specific client, containing things required for the view and local (event/command) prediction - and therefore generally seems to be what pmove acts on.

 

also, I still don't understand why people use these fake names everywhere in the first place ._.

Fake names? When mentioning the PlayerActor struct I was referring to the struct that is pointed at in the entity struct at offset 0x158. I don't know the proper name but if you feel better when I call it gclient_t (or playerstate_t?) then I'll call it so.