When AMQP starts after API service, paintings are not sent for review because AMQP connection is not established. This should not happen often, but it's something to consider.

Maybe it's better to just crash container and wait for restart.

1. Score half-life decay doesn't work properly
2. Some statistical info is not accumulated (flag is false)
3. No handler for situation where impression/sale made for previous batch

When a new painting is approved, the following error crashes the API, causing a several seconds of downtime:

at async Client.eval (webpack-internal:///156:34:17) {
at async ButtonInteraction.reply (/app/node_modules/discord.js/src/structures/interfaces/InteractionResponses.js:103:5)
at async RequestHandler.push (/app/node_modules/discord.js/src/rest/RequestHandler.js:51:14)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at RequestHandler.execute (/app/node_modules/discord.js/src/rest/RequestHandler.js:350:13)
DiscordAPIError: Unknown interaction
^
throw new DiscordAPIError(data, res.status, request);
/app/node_modules/discord.js/src/rest/RequestHandler.js:350

When a new painting is approved, send it to specialized Discord channel and show assigned tags. That way players will be able to get notified about their paintings approved.

Add name to logs in that case:

Invalid name
Error: Invalid name
    at PaintingService.create

to make sure in-game validation and Gallery validation match

For some players, there's an error happening when trying to fetch Minecraft profile info:

TypeError: Cannot read properties of null (reading 'type')
at MinecraftService.getProfileInfo
at PlayerService.createAssetsForPlayer

I assume that might happen for players without Minecraft installed.