NexonExecutor - Library for Developers

NexonExecutor​

The simple future logic executor.​

​

Explanation & Usage​

NexonExecutor executes runnable logic pieces in the future. For example, when somebody hits a block, you wish for a message to show 1 second later.​

​

You could create this example environment with the following code:​

​

Code:

FutureExecutor.schedule(new Runnable() {
    @Override
    public void run() {
        player.sendMessage("Hey there!");
    }
}, 1000);

or, if you wish to specify the time unit​

Code:

FutureExecutor.schedule(new Runnable() {
    @Override
    public void run() {
        player.sendMessage("Hey there!");
    }
}, 1000, TimeUnit.MILLISECONDS);

Installation​

Simply add this runtime argument

Code:

-cp nexonexecutor.jar

​

Download​

 

Doesn't the Bukkit scheduler already do that? I don't see any new features compared to that.

 

what about java's default timer?

 

Decompiling this results in:

Code:

package com.nappo.util;

import java.util.concurrent.Executors;
import java.util.concurrent.ScheduledExecutorService;
import java.util.concurrent.ScheduledFuture;
import java.util.concurrent.TimeUnit;

public final class FutureExecutor
{
  private static final ScheduledExecutorService service = Executors.newScheduledThreadPool(1);

  public static ScheduledFuture<?> schedule(Runnable logic, int delay, TimeUnit unit)
  {
    return service.schedule(logic, delay, unit);
  }

  public static ScheduledFuture<?> schedule(Runnable logic, int delay)
  {
    return schedule(logic, delay, TimeUnit.MILLISECONDS);
  }
}

What is the advantage of using this over directly using java.util.concurrent in plugins?

 

A candidate for forum 63?

 

This isn't any different than just using java.util.concurrent, which you shouldn't be anyways because there's BukkitScheduler.

 

Well, at least s?he didn't repackage jars like Neon Volcom.

 

Wow that's amazing, what's next ? a way to send msg to a player ? maybe cake ?
oh well, it made me laugh

 

The only advantage over using java.util.concurrent in plugins is this is far easier to declare.

Other than that, it is just an implementation. I am very sorry if this is not the type of library you seek for

 

Plugins shouldn't use java.util.concurrent. For scheduling tasks, use the Bukkit scheduler. So, this library won't be used by anyone. Nice try at helping us though!