Skip to content

Commit

Permalink
fix some improper bold text in addon rules
Browse files Browse the repository at this point in the history
  • Loading branch information
3vorp committed Jun 27, 2024
1 parent 89bac67 commit f2d136d
Showing 1 changed file with 7 additions and 5 deletions.
12 changes: 7 additions & 5 deletions pages/manuals/add-on-rules.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,17 +14,19 @@ date: "2022-08-13"
<li><b>It must be descriptive enough to give anybody a basic idea what your pack does.</b></li>
<li><b>It has to be properly capitalised with <a href="https://en.wikipedia.org/wiki/Title_case">Title Case</a>.</b></li>
<li><b>When possible, use proper English grammar.</b>
<br>(If you forget to do any of these nothing bad will happen, but please keep this in mind so that the managers don’t have to fix the title for every add-on.)</li>
<li><b>Avoid using the word “Better” in the name! Be creative — Describe your pack more precisely. (This can be tolerated in some cases if the header image shows what the add-on does clearly, but we'd still prefer more creative names for your add-ons.)</b></li>
<br>If you forget to do any of these nothing bad will happen, but please keep this in mind so that the managers don’t have to fix the title for every add-on.</li>
<li><b>Avoid using the word “Better” in the name!</b>
<br>Be creative and describe your pack more precisely. This can be tolerated in some cases if the header image shows what the add-on does clearly, but we'd still prefer more creative names for your add-ons.</li>
<li><b>No obscenities or swear words.</b></li>
<li><b>Don’t use the word “Faithful” in the title unless absolutely necessary.</b> It’s already evident that your pack is made for Faithful, since, you know, it’s on the Faithful website. The same goes for the resolution – don't include it in your title, it's displayed right above it anyway.</li>
<li><b>Don’t use the word “Faithful” in the title unless absolutely necessary.</b>
<br>It’s already evident that your pack is made for Faithful, since, you know, it’s on the Faithful website. The same goes for the resolution – don't include it in your title, since it's displayed right above it anyway.</li>
</ol>
5. **The add-on description must characterise what the add-on does and what it’s like. More is better than less.**
5. **The add-on description must characterise what the add-on does and what it’s like.** More is better than less.
6. **No NSFW or NSFL content.** (As in pornography, over-the-top gore and other questionable stuff.)
7. **Please use the built-in tags to let people know whether OptiFine is required or not, and what edition/Faithful resolution your add-on is made for.** Don’t specify that in the title.
8. **Your pack must comply with our [license](https://faithfulpack.net/license).** That means crediting Faithful and linking back to https://faithfulpack.net when listing your pack anywhere except the Faithful website. Also, refrain from using any monetisation sites such as adf.ly.
9. **Your add-on can’t be the same as an already existing one. If you want to make updates or changes to an existing add-on, contact its creator.** If they don’t respond within a reasonable timeframe, contact one of the Managers to ask for editing permissions. If you want to make an add-on with the same purpose as an existing one but done in a different way, that’s fine, but please use a different title.
10. **All download links must be direct.** No linking to posts on other sites. Ideally, clicking on the download button should directly download the pack file, but linking to services such as MediaFire or Mega is also fine.
11. **The add-on needs to be zipped properly.** Users shouldn't be required to unzip the pack and fiddle with the folders to get your add-on working. Just make sure that your zip works in-game.

Lastly, the managers reserve the right to correct small grammar/spelling mistakes in your add-on’s description, should they find any.
Lastly, the managers reserve the right to correct small grammar/spelling mistakes in your add-on’s description, should they find any.

0 comments on commit f2d136d

Please sign in to comment.