FakePlayer issues because of unassigned UUID
olee opened this issue ยท 2 comments
This is a bug report in regards to previously closed issues #387 and #352
This is actually a problem on your side, because you create invalid FakePlayer entities:
CommonProxyBase.java#L30
You are not supposed to pass a null
UUID.
Either create your own for AncientWarefare and always use the same (which will mean permission for all blocks using FakePlayers will be treated the same), or the correct way would be to change IOwnable to save the UUID additionally / instead of the playername.
Issue 352 is not closed.
The null argument in GameProfile is valid, as shown by Minecraft own usage and implementation of this class.
Though the best effort will be made to support UUID in the future, there is no guarantee UUID will ever be non-null in all cases, due to backward compatibility and the "no-player logged-in" automation module possibilities.
Branch 2.5 is more advanced on this topic, by the way.