CraftBook 3

CraftBook 3

139k Downloads

Craftbook trying to lookup UUID of invalid usernames

LadyCailinBot opened this issue ยท 8 comments

commented

CRAFTBOOK-3050 - Reported by asgarioth

During our tests of Craftbook 3.8.9 and any later builds we detect strange profile lookups sent to Mojang. The account names used match to sign contents which are used for decoration purposes. None of these signs are actually valid Craftbook signs.

Whenever I disable Craftbook or do a downgrade to Craftbook 3.8.8 the messages do not appear any more which is the reason to post this issue here. We currently try to find out where these signs are placed within our spawn area (which is quite large and detailed) in order to provide more details.

Here is a sample log output:

[16:31:54] [Server thread/DEBUG]: Opening connection to https://api.mojang.com/profiles/minecraft
[16:31:54] [Server thread/DEBUG]: Writing POST data to https://api.mojang.com/profiles/minecraft: ["o "]
[16:31:54] [Server thread/DEBUG]: Reading data from https://api.mojang.com/profiles/minecraft
[16:31:54] [Server thread/DEBUG]: Successful read, server response was 200
[16:31:54] [Server thread/DEBUG]: Response: []
[16:31:54] [Server thread/DEBUG]: Page 0 returned 0 results, parsing
[16:31:54] [Server thread/DEBUG]: Couldn't find profile o
[16:31:54] [Server thread/DEBUG]: Opening connection to https://api.mojang.com/profiles/minecraft
[16:31:54] [Server thread/DEBUG]: Writing POST data to https://api.mojang.com/profiles/minecraft: ["o "]
[16:31:54] [Server thread/DEBUG]: Reading data from https://api.mojang.com/profiles/minecraft
[16:31:54] [Server thread/DEBUG]: Successful read, server response was 200
[16:31:54] [Server thread/DEBUG]: Response: []
[16:31:54] [Server thread/DEBUG]: Page 0 returned 0 results, parsing
[16:31:54] [Server thread/DEBUG]: Couldn't find profile o
[16:31:55] [Server thread/DEBUG]: Opening connection to https://api.mojang.com/profiles/minecraft
[16:31:55] [Server thread/DEBUG]: Writing POST data to https://api.mojang.com/profiles/minecraft: ["o "]
[16:31:55] [Server thread/DEBUG]: Reading data from https://api.mojang.com/profiles/minecraft
[16:31:55] [Server thread/DEBUG]: Successful read, server response was 200
[16:31:55] [Server thread/DEBUG]: Response: []
[16:31:55] [Server thread/DEBUG]: Page 0 returned 0 results, parsing
[16:31:55] [Server thread/DEBUG]: Couldn't find profile o
[16:31:55] [Server thread/DEBUG]: Opening connection to https://api.mojang.com/profiles/minecraft
[16:31:55] [Server thread/DEBUG]: Writing POST data to https://api.mojang.com/profiles/minecraft: ["vvvvv"]
[16:31:55] [Server thread/DEBUG]: Reading data from https://api.mojang.com/profiles/minecraft
[16:31:55] [Server thread/DEBUG]: Successful read, server response was 200
[16:31:55] [Server thread/DEBUG]: Response: []
[16:31:55] [Server thread/DEBUG]: Page 0 returned 0 results, parsing
[16:31:55] [Server thread/DEBUG]: Couldn't find profile vvvvv

commented

Comment by me4502

Oh.. What mechanics do you have enabled?

commented

Comment by asgarioth

We currently use the following mechanics:

  • Variables
  • Ammeter
  • ToggleArea
  • Bridge
  • ChunkAnchor
  • Door
  • Elevator
  • Gate
  • HiddenSwitch
  • LightStone
  • PaintingSwitcher
  • Pay
  • SignCopier
  • Teleporter
  • MinecartEjector
  • MinecartNoCollide
  • MinecartTeleporter
  • BoatDrops
  • BoatUncrashable
  • ICs
commented

Comment by me4502

Are you able to disable Variables, and see if it stops doing this?

commented

Comment by asgarioth

Yes I am. It looks pretty much as if you are on the right track. ;)
After I disabled the Variables none of the above mentioned requests were issued to Mojang anymore.

commented

Comment by me4502

Thanks, I believe I have fixed the issue now.
If you want, you can disable UUID conversions in the craftbook config and re-enable variables.

commented

Comment by asgarioth

Thanks a lot for your support. I would have never expected such a quick response and solution. Keep up the great work and attitude towards us end-users. :)

commented

Comment by me4502

That has already been fixed in the 3.9 betas.

commented

Comment by asgarioth

"and any later builds" <= I observe this behavior with 3.9 beta3 build as well.