Added PlayerProfile support

[egg82]

Adds PlayerProfile support for Paper, and a raw Mojang API/web request of not using Paper. This is mostly used for offline players (getting correct UUIDs, etc)

[aikar]

Overall I think it is ok as a first pass
would be good if it also had properties too, but that can come later.

but i do like it being a read only object since cant set anything with it for now.

but would like some things changed:

1. Use interface design pattern everything else uses.

• The goal is one could replace implementations with reflection in their own plugin if they wished, or create reflection based "plugins" to PaperLib they can ship as their own modules.
• This allows you to change impls per version with concrete implementations

2. implement the isComplete() and .complete(fromCache) pattern

• network calls should only be made on Bukkit if either fromCache is false OR fromCache is true but can not be found in cache.
• use getOfflinePlayer for cache usage if we have a UUID but don't have name
• name to uuid might need to always be network, as name to uuid in offline player can be really slow

3. complete should take two params, fromCache and async andd should return a CompletableFuture,

if async is true (Default for .complete() or .complete(fromCache), dispatch the network requests on an async task, then complete future back on main thread.

• rate limit errors should reject the future.

Papers version of complete should also be done async too.

if async is false, do the network request on current thread and use CompletableFuture.completedFuture(result) or CompletableFuture.failedFuture(ex)

[egg82]

Adds PlayerProfile support for Paper, and a raw Mojang API/web request of not using Paper. This is mostly used for offline players (getting correct UUIDs, etc)

[aikar]

Overall I think it is ok as a first pass
would be good if it also had properties too, but that can come later.

but i do like it being a read only object since cant set anything with it for now.

but would like some things changed:

1. Use interface design pattern everything else uses.

• The goal is one could replace implementations with reflection in their own plugin if they wished, or create reflection based "plugins" to PaperLib they can ship as their own modules.
• This allows you to change impls per version with concrete implementations

2. implement the isComplete() and .complete(fromCache) pattern

• network calls should only be made on Bukkit if either fromCache is false OR fromCache is true but can not be found in cache.
• use getOfflinePlayer for cache usage if we have a UUID but don't have name
• name to uuid might need to always be network, as name to uuid in offline player can be really slow

3. complete should take two params, fromCache and async andd should return a CompletableFuture,

if async is true (Default for .complete() or .complete(fromCache), dispatch the network requests on an async task, then complete future back on main thread.

• rate limit errors should reject the future.

Papers version of complete should also be done async too.

if async is false, do the network request on current thread and use CompletableFuture.completedFuture(result) or CompletableFuture.failedFuture(ex)

[egg82]

Adds PlayerProfile support for Paper, and a raw Mojang API/web request of not using Paper. This is mostly used for offline players (getting correct UUIDs, etc)

[aikar]

Overall I think it is ok as a first pass
would be good if it also had properties too, but that can come later.

but i do like it being a read only object since cant set anything with it for now.

but would like some things changed:

1. Use interface design pattern everything else uses.

• The goal is one could replace implementations with reflection in their own plugin if they wished, or create reflection based "plugins" to PaperLib they can ship as their own modules.
• This allows you to change impls per version with concrete implementations

2. implement the isComplete() and .complete(fromCache) pattern

• network calls should only be made on Bukkit if either fromCache is false OR fromCache is true but can not be found in cache.
• use getOfflinePlayer for cache usage if we have a UUID but don't have name
• name to uuid might need to always be network, as name to uuid in offline player can be really slow

3. complete should take two params, fromCache and async andd should return a CompletableFuture,

if async is true (Default for .complete() or .complete(fromCache), dispatch the network requests on an async task, then complete future back on main thread.

• rate limit errors should reject the future.

Papers version of complete should also be done async too.

if async is false, do the network request on current thread and use CompletableFuture.completedFuture(result) or CompletableFuture.failedFuture(ex)

[egg82]

Adds PlayerProfile support for Paper, and a raw Mojang API/web request of not using Paper. This is mostly used for offline players (getting correct UUIDs, etc)

[aikar]

Overall I think it is ok as a first pass
would be good if it also had properties too, but that can come later.

but i do like it being a read only object since cant set anything with it for now.

but would like some things changed:

1. Use interface design pattern everything else uses.

• The goal is one could replace implementations with reflection in their own plugin if they wished, or create reflection based "plugins" to PaperLib they can ship as their own modules.
• This allows you to change impls per version with concrete implementations

2. implement the isComplete() and .complete(fromCache) pattern

• network calls should only be made on Bukkit if either fromCache is false OR fromCache is true but can not be found in cache.
• use getOfflinePlayer for cache usage if we have a UUID but don't have name
• name to uuid might need to always be network, as name to uuid in offline player can be really slow

3. complete should take two params, fromCache and async andd should return a CompletableFuture,

if async is true (Default for .complete() or .complete(fromCache), dispatch the network requests on an async task, then complete future back on main thread.

• rate limit errors should reject the future.

Papers version of complete should also be done async too.

if async is false, do the network request on current thread and use CompletableFuture.completedFuture(result) or CompletableFuture.failedFuture(ex)

[egg82]

Adds PlayerProfile support for Paper, and a raw Mojang API/web request of not using Paper. This is mostly used for offline players (getting correct UUIDs, etc)

[aikar]

Overall I think it is ok as a first pass
would be good if it also had properties too, but that can come later.

but i do like it being a read only object since cant set anything with it for now.

but would like some things changed:

1. Use interface design pattern everything else uses.

• The goal is one could replace implementations with reflection in their own plugin if they wished, or create reflection based "plugins" to PaperLib they can ship as their own modules.
• This allows you to change impls per version with concrete implementations

2. implement the isComplete() and .complete(fromCache) pattern

• network calls should only be made on Bukkit if either fromCache is false OR fromCache is true but can not be found in cache.
• use getOfflinePlayer for cache usage if we have a UUID but don't have name
• name to uuid might need to always be network, as name to uuid in offline player can be really slow

3. complete should take two params, fromCache and async andd should return a CompletableFuture,

if async is true (Default for .complete() or .complete(fromCache), dispatch the network requests on an async task, then complete future back on main thread.

• rate limit errors should reject the future.

Papers version of complete should also be done async too.

if async is false, do the network request on current thread and use CompletableFuture.completedFuture(result) or CompletableFuture.failedFuture(ex)

[egg82]

Adds PlayerProfile support for Paper, and a raw Mojang API/web request of not using Paper. This is mostly used for offline players (getting correct UUIDs, etc)

[aikar]

Overall I think it is ok as a first pass
would be good if it also had properties too, but that can come later.

but i do like it being a read only object since cant set anything with it for now.

but would like some things changed:

1. Use interface design pattern everything else uses.

• The goal is one could replace implementations with reflection in their own plugin if they wished, or create reflection based "plugins" to PaperLib they can ship as their own modules.
• This allows you to change impls per version with concrete implementations

2. implement the isComplete() and .complete(fromCache) pattern

• network calls should only be made on Bukkit if either fromCache is false OR fromCache is true but can not be found in cache.
• use getOfflinePlayer for cache usage if we have a UUID but don't have name
• name to uuid might need to always be network, as name to uuid in offline player can be really slow

3. complete should take two params, fromCache and async andd should return a CompletableFuture,

if async is true (Default for .complete() or .complete(fromCache), dispatch the network requests on an async task, then complete future back on main thread.

• rate limit errors should reject the future.

Papers version of complete should also be done async too.

if async is false, do the network request on current thread and use CompletableFuture.completedFuture(result) or CompletableFuture.failedFuture(ex)

[egg82]

Adds PlayerProfile support for Paper, and a raw Mojang API/web request of not using Paper. This is mostly used for offline players (getting correct UUIDs, etc)

[aikar]

Overall I think it is ok as a first pass
would be good if it also had properties too, but that can come later.

but i do like it being a read only object since cant set anything with it for now.

but would like some things changed:

1. Use interface design pattern everything else uses.

• The goal is one could replace implementations with reflection in their own plugin if they wished, or create reflection based "plugins" to PaperLib they can ship as their own modules.
• This allows you to change impls per version with concrete implementations

2. implement the isComplete() and .complete(fromCache) pattern

• network calls should only be made on Bukkit if either fromCache is false OR fromCache is true but can not be found in cache.
• use getOfflinePlayer for cache usage if we have a UUID but don't have name
• name to uuid might need to always be network, as name to uuid in offline player can be really slow

3. complete should take two params, fromCache and async andd should return a CompletableFuture,

if async is true (Default for .complete() or .complete(fromCache), dispatch the network requests on an async task, then complete future back on main thread.

• rate limit errors should reject the future.

Papers version of complete should also be done async too.

if async is false, do the network request on current thread and use CompletableFuture.completedFuture(result) or CompletableFuture.failedFuture(ex)

[egg82]

Adds PlayerProfile support for Paper, and a raw Mojang API/web request of not using Paper. This is mostly used for offline players (getting correct UUIDs, etc)

[aikar]

Overall I think it is ok as a first pass
would be good if it also had properties too, but that can come later.

but i do like it being a read only object since cant set anything with it for now.

but would like some things changed:

1. Use interface design pattern everything else uses.

• The goal is one could replace implementations with reflection in their own plugin if they wished, or create reflection based "plugins" to PaperLib they can ship as their own modules.
• This allows you to change impls per version with concrete implementations

2. implement the isComplete() and .complete(fromCache) pattern

• network calls should only be made on Bukkit if either fromCache is false OR fromCache is true but can not be found in cache.
• use getOfflinePlayer for cache usage if we have a UUID but don't have name
• name to uuid might need to always be network, as name to uuid in offline player can be really slow

3. complete should take two params, fromCache and async andd should return a CompletableFuture,

if async is true (Default for .complete() or .complete(fromCache), dispatch the network requests on an async task, then complete future back on main thread.

• rate limit errors should reject the future.

Papers version of complete should also be done async too.

if async is false, do the network request on current thread and use CompletableFuture.completedFuture(result) or CompletableFuture.failedFuture(ex)