Solved Can't make cooldown

Code:

    @EventHandler
    public void onProjectileLaunchDemo(ProjectileLaunchEvent event) {
        Projectile p = event.getEntity();
        if (p instanceof Arrow && p.getShooter() instanceof Player) {
            Player pl = (Player) p.getShooter();
            Vector v = p.getVelocity();
            if (getKitForPlayer(pl) == demoman) {
                List<Player> cooldown = new ArrayList<Player>();
                if (cooldown.contains(pl)) {
                    pl.sendMessage("You are on cooldown..");
                    return;
                }
                p.remove();
                TNTPrimed tnt = (TNTPrimed) pl.getWorld().spawnEntity(p.getLocation(), EntityType.PRIMED_TNT);
                tnt.setVelocity(v.setY(v.getY() + 0.025));
                tnt.setIsIncendiary(false);
                tnt.setYield(10);
                cooldown.add(pl);
                Bukkit.getScheduler().scheduleSyncDelayedTask(plugin, new Runnable() {
                   
                    @Override
                    public void run() {
                        cooldown.remove(pl);
                    }
                }, 40);
            }
        }
    }

The cooldown doesn't work, it allows me to keep spamming my bow..

 

@MgMaor

I think you may want to go study some Java. Specifically the concept of scope.

 

@MgMaor you've declared your cooldown list inside of your onProjectileLaunchDemo method's scope, therefore, a new instance of the cooldown list will be created every time the onProjectileLaunchDemo method is called.

@mythbusterma is right

 

Since you seem to not be even intermediate at Java, (no offence), I recommend you don't store Player instances but you store their UUID.

 

@ItsMattHogan thx
@mythbusterma @KingFaris11 don't post your irrelevant thoughts.

 

Actually, they are very relevant. If you had known Java, I can't imagine you would be having this issue.

So,

Here's a place to start: http://bukkit.org/threads/plugin-dev-sticky-learning-java-where-to-learn.350132/

 

Mine may not be relevant to solving yours, but I also would prevent memory leakage. Oh well, guess you want a terrible plugin with memory leakages, TPS lag, etc. I would never even use a scheduler, the more efficient way is storing the UUID and the time in millis into a Map, then checking against this within the delay check method.