Close gaps in your submission according to the documentation, compare with other submissions (see column "Already in Debian" with a "No"). Examples include
- instead of a ITA to adopt an already existing package without an maintainer, you should file an ITP to express your intent to package and the use this bug ticket number in the changelog - use a real upstream reference page, not www.example.com - indicate the public repository dedicated to package the game for Debian. In case you (co)author / (co)maintain the upstream program (on GitHub, Gitlab, gittea, codeberg, etc) and prepare the package for Debian; it is better to keep the two things separate (e.g., package on salsa) because rules and best practices to package for Debian may differ to the ones in other distributions. - In light of semantic versioning (see https://semver.org/), I recommend to await at least the release of upstream version 0.1.0 rather than to package already upstream version 0.0.1 (as 0.0.1-1 to Debian).
