Making a player unable to move?

Blockland Forums > Modification Help

<< < (3/4) > >>

Iban:

--- Quote from: otto-san on February 28, 2011, 10:44:59 PM ---I remember when I had an epiphany like that.

thanks a bunch. :cookieMonster:

question: What role does the variable %this play in that function? :o

--- End quote ---
None.

Armor functions are used when you want something to apply to only one kind of player.

For instance,

--- Code: ---function Armor::zombieExplode(%this, %obj)
{
// Nothing!
}
--- End code ---

Why make this function? So I can put this function in on top of it.

--- Code: ---function ZombieBoomerArmor::zombieExplode(%this, %obj)
{
// Boomer explosion code here.
}
--- End code ---

Then, I can call %armor.zombieExplode(); and it will always work with no console errors. If the boomer explodes, however, the bile affect is applied to nearby players.

For what you are doing, you do not need to use an Armor function. Just apply the code I give you intelligently to the function where the "discombobulation" happens.

otto-san:
Right then. Thank you for your help.

phflack:

--- Quote from: Altered on February 28, 2011, 07:48:06 PM ---Non-moving playertype

somewhere on RTB

--- End quote ---
i should know it's there, as i uploaded it :D
and iban's way would be useful for things

Chrono:
There's many ways to make a player not able to move.

Mount it to an invisible (or visible) static shape, set the client's control object to a camera, etc.

Iban:

--- Quote from: Chrono on March 02, 2011, 01:50:46 PM ---There's many ways to make a player not able to move.

Mount it to an invisible (or visible) static shape, set the client's control object to a camera, etc.

--- End quote ---
Mounting a player to an invisible static shape not only requires some hacking to prevent the player for being able to just right click off the mount, but it requires additional datablocks and a shapefile with proper mount points. The camera method is by far superior.

Navigation

 Message Index

Go to full version