Player UUID UUIDFetcher taking adding lag.

So,

when I use the UUIDFetcher.call to get some data, it takes like 2 seconds n' within those 2 seconds, any commands executed will be delayed until those 2 seconds are over.

 

have you read documentation of fetcher?
if not - you have exellent chance to read it now.

 

Documentation? I don't see any documentation on https://forums.bukkit.org/threads/player-name-uuid-fetcher.250926/.

Also, could you tell me the way of fixing this instead of telling me to read the entire documentation? I will read up on the documentation, but my plugin badly needs this fix and I'm going to go soon.

Thanks
Neil

 

Neilnet You say that you don't see any documentation, yet you use the phrase "entire documentation". If you haven't seen any documentation, then you cannot possibly know its length meaning "entire" is slightly misleading.

As for your problem, it mentions what you're doing wrong on the post you linked. Read it. And sure we could tell you exactly what's wrong, but that's not the point. Using a library without reading the resources about it is just irresponsible

 

Neilnet

not a spoonfeeding section, you must read documentation self and then if you failed to fix issue - provide code, explain steps you take to fix it and what is wrong.

 

Where is the documentation? The github is just code. I can't see any documentation link on the bukkit page :/

 

Neilnet
Read the post word for word. The solution will come up.

 

Thanks!!!

 

Neilnet Run it on a different thread.

 

DevRosemberg
http://www.javaprogrammingforums.com/content/45-problem-spoon-feeding.html

 

Someone help, this is my UUIDThreadFetcher, it uses a thread to fetch UUIDS.

Code:java

 
 
import java.util.Arrays;
import java.util.Map;
import java.util.UUID;
 
 
public class UUIDThreadFetcher extends Thread{
 
    private String username;
    private String UUIDString;
 
    public UUIDThreadFetcher(String username) {
        this.username = username;
        this.start();
    }
 
    public void run() {
        Map<String, UUID> playerMap = null;
        try {
            playerMap = new UUIDFetcher(Arrays.asList(username)).call();
        } catch (Exception e) {
            e.printStackTrace();
        }
 
        UUIDString = playerMap.toString().replace("{", "").replace("}","").replace(username+"=", "");
    }
 
    public String getUUID(){
        return UUIDString;
    }
 
 
}
 

new UUIDThreadFetcher(username).getUUID() returns a null. How do I make a thread return an exact value?

90% of Bukkit things related to events, nulls and everything involves people spoon fed answers.

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

If you're running in online mode and the player has been on the server before, you could get the UUID from an OfflinePlayer.

 

Neilnet Even if it happens, it doesn't mean people should spoon-feed. Debug your code to see the results of methods and such.

 

Neilnet
You should might do it with HashMaps which are loading onEnable and onJoin. So you only listen for one Player once when he joins.

And the thing with the Thread > Isn't it better to use a BukkitRunnable so you are sync?

 

PreFiXAUT You completely missed the point, didn't you? You don't want to do it on the main thread, that was the problem.

 

I know? I never said he should do it in the Main-Thread or did I say it somewhere?
I just said he can also save the UUID's with the Playernames so he doesn't need to lookup the name EVERYTIME.

 

PreFiXAUT

 

AdamQpzm

 

the Callabe is a thread on its self which returns something back in return else it throws a exception it generally throws it a bit faster to.

PreFiXAUT
the link from EvilMidgets class is the best you can get imo, from what ive googled there is nothing more faster than using a Callable, in fact using a Runnable only slowdowns it more.

however the problem what may is the cause for lag is multicraft or lets say shared hosting, some hosters just don't allow multithreading and then a Callable just act as a other thread but is still running on the main thread causing to slow your server down ive solved it myself to move to a dedicated server, however it also made me super afraid all threads of the server can be used by plugins such like PermissionsEx and what not, it made me sort of against looking up accounts just because storing is better.

if you check craftbukkit in VisualVM you already see craftbukkit has some threads to which makes it super hard to have 2 - 3 extra more threads to fetch uuids honestly I doubt mojang thought out about these issues very well.

 

xize Or you could have one thread that is responsible for the look-ups, as long as you're not doing them too frequently and use the ...runOnThread() (or something like that, I know one exists) method to do it every time, saving yourself the extra threads, although the calls would have to stack up.

 

RawCode Telling how to solve != Spoon Feeding

 

DevRosemberg
read thread carefully, everyone asked TS to read documentation and you just spoonfeeded solution.
your action caused TS to ignore documentation further, now he wont read it.

 

RawCode How do you know he didnt read it

 

DevRosemberg Because it told him how to solve the problem - if he'd read & followed it, he wouldn't have posted here