3646
Drama / Re: Nienhaus linking child research on tinychat
« on: December 31, 2013, 04:15:16 AM »
Surely Steve will be apprehended if he has access to child research.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
"no aimbotting"Sniper is in the arsenal. Who knows.
lol





if you set .position you bypass any mods that packaged .setposition causing you to break modsthank you. now i understand.
bad
What the forget even is that argument. So you want every player on the server to NOT see the updated position until they either move or turn? Okay then.your argument in that example was "why not just do a bunch of unnecessary steps to cube a number". there are no unnecessary steps in setting .position, but it DOES break the game. fine, i get that now, but your argument was totally invalid, because setting .position takes no unnecessary steps. and i never claimed that you shouldn't update the position; i was pointing out that your argument does not fit the case, because doing it the wrong way (setting .position) is actually one less step than doing it correctly, process wise. (setting position and updating vs setting position)
"Unnecessary steps" my ass. Are you the kind of person who doesn't mind getting in a Cessna with known engine problems, WITHOUT going through the pre-flight checklist? It's just an unnecessary step!
what do you mean by pushes an update? and how is that comparable to setting position? what you've done is a load of unnecessary steps, when there are no unnecessary steps in setting .position; in fact, it's one less step (if you're counting the update as a step)
function mCube(%val)
{
return mPow(%val, mFloatLength(mFloor(getSubStr($PI, 0, 1)), 0));
}
Why shouldn't I do it that way? I've found it works fine.
Anyway, the one actual reason I've found for using .setTransform() as opposed to setting .position is that using .setTransform() pushes the update, while setting .position does not. Other than setting rotation, of course.
Actually, you can change a player's position by setting %pl.position = "some position"; - it's a stupid way to do it and you SHOULDN'T do it that way, but it technically works.why shouldn't you do it? i've found it works fine?