[Tutorial] Making Bounce Pads/Trampolines.

Have you ever seen on a server how when you step on something it boosts you?
Heres how to do that:
Step One is to make the command/event for when you want to boost them:

Code:

@EventHandler
public void onBoost(PlayerMoveEvent event){
}

Then check what block the player is standing on:

Code:

@EventHandler
    public void onTrampoline(PlayerMoveEvent event){
        Player p = event.getPlayer();
        if(p.getLocation().subtract(0, 1, 0).getBlock().getType() == Material.<The Block You Want>){
        }
    }

Then you add the Vector:

Code:

@EventHandler
    public void onTrampoline(PlayerMoveEvent event){
        Player p = event.getPlayer();
                  Vector v = event.getPlayer().getLocation().getDirection();
        if(p.getLocation().subtract(0, 1, 0).getBlock().getType() == Material.<The Block You Want>){
            p.setVelocity(new Vector(v.multiply(2));
        }
    }

And that's how you make a boost pad. For a trampoline the same thing goes but for the Vector its:

Code:

p.setVelocity(new Vector(p.getVelocity().getX(), 2, p.getVelocity().getZ()));

Also you can do an ItemStack instead of the Material.<The Block That You Want> if you only want it on certain blocks.

Thanks for reading my first ever Tutorial!

 

Can you explain how that would work or what you mean? Last time I checked, Material never equals an ItemStack. If you want the jump pad on more than one block material type, using the .contains() method for Collection would work unless you prefer to put || after || in your if statement.

 

Exactly how I did it!

 

ChipDev I usually use a scheduler

 

Oh what? Lol, Heres my code:

Code:java

public void onCrunch(PlayerMoveEvent e) {
        Player player = e.getPlayer();
        try {
        if(e.getFrom().getBlockY() > e.getTo().getBlockY()) {
                if(!e.getTo().getBlock().getRelative(BlockFace.DOWN).isLiquid()) {
                        if(e.getTo().getBlock().getLocation().subtract(0, 1, 0).getBlock().getTypeId() == 100 ||
                            e.getTo().getBlock().getLocation().subtract(0, 3, 0).getBlock().getTypeId() == 100 ||
                            e.getTo().getBlock().getLocation().subtract(0, 2, 0).getBlock().getTypeId() == 100 ||
                            e.getTo().getBlock().getLocation().subtract(0, 4, 0).getBlock().getTypeId() == 100) {
                            double randomDouble = r.nextDouble();
                            double result = 0.9 + (1.7 - 0.9) * randomDouble;
                            e.getPlayer().setVelocity(new Vector(0, 5.0 + result, 0));
 
                            e.getPlayer().playSound(e.getPlayer().getLocation(), Sound.CHICKEN_EGG_POP, 4, 4);
                        }
                }else{
                      Bukkit.getServer().getPluginManager().callEvent(new HitGroundEvent(e.getPlayer()));
                }
              }
            }catch (Exception ex) {
          }
    }
    @EventHandler
    public void onLand(EntityDamageEvent e) {
        if(e.getEntity() instanceof Player) {
        Player p = (Player) e.getEntity();
        if(e.getCause().equals(DamageCause.FALL)) {
            e.setCancelled(true);
            p.setFallDistance(0.0f);
            e.setDamage(0.0);
            }
        }
    }

 

ChipDev Instead of the move event cause then they can keep bouncing even if they don't crouch

 

Wait, but.. move event calls when the player moves. I test if the player is 1-4 blocks above the mushroom block, and if, jump them forward.. move event calls when the player is pushed because of WASD or velocity etc.

 

ChipDev
Meh, isn't having a scheduler every 20Ticks for a pad vs listening to player move event a lot more efficient?

 

Wat..

 

Such math so wow!!

 

Assist
Its math. Keep it on-topic though..
Hawktasard

 

Code:java

Bukkit.getScheduler().scheduleSyncRepeatingTask(this, new Runnable() {
    @Override
    public void run() {
        for(Player p : Bukkit.getOnlinePlayers()){
            if(p.getLocation().clone().subtract(0, 1, 1).getBlock().getType().equals(Material.<Material You Want>)){
                p.setVelocity(new Vector(0, 2, 0));
            }
        }
    }
}, 0, 2);

Something like that is more efficient because player move is triggered every time someone moves, this includes when someone changes pitch and yaw. Using the scheduler would be more efficient with players who move on a regular basis. If your players only move once a year, you can use the player move event and be efficient.

Edit: I have just realized I was wrong, the player move event will never be more efficient then this unless your players hardly move and they don't use the trampoline. This is because being launched into the sky by the trampoline will also trigger the player move event a lot.