This is a checklist template I made for testing multiplayer Minecraft maps. It's mainly meant for minigames, but could work on adventure maps as well. I tried to include as many edge cases as I can think of, so I wouldn't forget them later during testing. To check a box, you need to be able to answer the question, or know what would happen if the situation occurs.

If you want to contribute, simply leave a comment on this gist or reach me on Slack/Discord.

• Delete all files in the playerdata directory. Do first-time players spawn with the right items, scores and in the right position?
• Set the server's simulation distance to 9. Does the map still work?
• Can players go out of bounds by boosting each other with knockback?

how to leverage oracle's temping offers

The limits of the free tier say that you can create up to 4 instances.

• x2 x86 instances (2core/1g)
• x2 ampere instances (with 4core/24g spread between them)
• 200GB total boot volume space across all intances (minimum of 50G per instance)

1. Setup local network:

ifconfig eth0 192.168.1.2 netmask 255.255.255.0

2. Ping your router forever

ping 192.168.1.1

Start ping your router and observe when the TTL change from 100 to 64.

You are a meta-prompt engineer. Your task is to generate a comprehensive, production-ready PRD document that will serve as both a specification AND an executable prompt for an AI coding agent.