Skip to content
Bullet Hero
ENRU
Asking an author for permission
On this page
Level author

Asking an author for permission

The letter template, the three points that must survive editing, and what counts as proof afterwards

Before you write

Recommendation

Ask before you build the level. Otherwise you can build four minutes of level around a track and end up with a finished level you cannot share. A reply usually takes a day or two

Send the template in English. Most rights holders you will be writing to do not read Russian

The template

Adjust the tone however you like, but keep points 1 to 3 intact. Those are what make the permission valid for CC BY-NC distribution

Subject: Permission to use "[work]" in a Bullet Hero level

Hi [author],

My name is [you], I am making a level for Bullet Hero (a rhythm and bullet-hell game, [link]) and I would love to use your work "[work]" ([link to the original]) in it.

Specifically I am asking your permission to:
1. Use "[work]" inside my Bullet Hero level.
2. Allow the level, including your work, to be shared and redistributed for FREE and NON-COMMERCIALLY by anyone who downloads it, through Bullet Hero's official and unofficial services (its official server, Steam Workshop, and any community-run servers).
3. Credit you as "[how you want to be credited]" wherever the level shows attribution.

To be clear, this permission is for non-commercial use only. The level will not be sold, and nobody will make money from it or from your work through it.

If you are fine with this, a simple reply confirming points 1 to 3 is all I need - I will keep this message as proof of permission. If you would rather be credited differently, or want to set any other condition, just tell me.

Thanks a lot either way,
[you]

What counts as proof

Anything a moderator can open and read: a reply by email, a direct message, a public post. A public url is the strongest proof. If an exchange has no public address, a quote of the reply is stored instead

What does not count:

  • "he said it was fine" with nothing attached
  • a screenshot with no source
  • a permission for your own use that says nothing about redistribution
  • silence. It is the same as never having asked
Caution

A permission that says nothing about redistribution is the most common reason a permission comes back unusable. That is why point 2 exists in the template

Scope and dates

Write down the permission's scope and dates:

  • "for this track, in this level" - one level. A second level needs asking again
  • "use it in anything you make" - every level of yours

Next: Two ways a resource qualifies, A resource's record