Page 1 of 1

RULES: Read this before posting a MOD support patch

Posted: 05 Apr 2015, 08:09
by Sphax

Rules to post "Patches for Mods"

Please, read them carefully before posting a new thread.

Before creating and posting a MOD support patch for PureBDcraft, you must read, understand and agree with the PureBDcraft Terms of Use.

With the according terms, by default, you are not authorized to create derivative work based on the PureBDcraft texturepack.

I waive this condition of use for MODs support only if, and only if, the following conditions are met:

What to do

  • MOD support must be released as a "patch" of PureBDcraft. That means you cannot include any part of the main pack, unmodified, within your patch.
  • MOD support should be released on this forum. You can also release it in any other forum.
  • The thread dedicated to the MOD support patch must include the MOD banner (if any), the link to the MOD (website or forum thread), a short description of the MOD, a preview (one or more pictures), credits and download section.
  • The thread dedicated to the MOD support patch must be proofread and written in the best English you can manage before being submitted.
  • Remember to always give proper credits to the people who worked on the patch.
  • Downloads should be in .zip format. DO NOT use other formats (e.g. .rar or .7z) as they can have issues on some systems.
  • Read the "Tips & Tricks to create textures in the PureBDcraft style" thread.
  • Minecraft 1.7+: Due to the added feature of resource packs in MC1.7 and above you will be required to include a pack.mcmeta (see the spoiler below for extra details).
Show
pack.mcmeta
You can get an example pack.mcmeta here for MC1.7 and MC1.8, here for MC1.9 and MC1.10 and here for MC1.11+. Save it and open it in your favourite text editor (such as Notepad) and edit it as required.

The use of a valid mcmeta will be enforced and if you do not supply one your links may be removed until you fix it.

MC1.7 and MC1.8

Code: Select all

{
  "pack": {
    "pack_format": 1,
    "description": "PureBDcraft patch by HanFox\nhttp://bdcraft.net"
  }
}
MC1.9 and MC1.10

Code: Select all

{
  "pack": {
    "pack_format": 2,
    "description": "PureBDcraft patch by HanFox\nhttp://bdcraft.net"
  }
}
MC1.11+

Code: Select all

{
  "pack": {
    "pack_format": 3,
    "description": "PureBDcraft patch by HanFox\nhttp://bdcraft.net"
  }
}
This will give you something similar to:
Image

pack.png
This is the official patch icon provided by Sphax which we recommend you use above anything else (however this will not be enforced).
Image

Note
These files go in the "top level" of your zip in the same place as the assets folder.

Even if there are no particular changes between the patch in MC1.6 and MC1.7 you should still make an entirely new zip containing these files.

The same goes for MC1.9, MC1.10 and MC1.11. Even if there are no changes you must upload new zips with the correct pack_format in the pack.mcmeta for MC1.9+.

What you are not authorized to do

  • You are not authorized to create and release a remixpack or use any of the textures from the main PureBDcraft pack in another resourcepack.
  • You are not authorized to release your patch under an adf.ly link or any other payment method. You should do this for fun and to help the community, not to make money. If you disagree, let me know by email or by PM, I'll be glad to discuss this with you. If you want to have a permalink, use bit.ly or any other non-paid URL shortner.
  • You are not authorized to make patches or textures for a commission (i.e. a money payment).

What you are authorized to do

  • You can use any textures included in the PureBDcraft texturepack (recent or old version) or included in official PureBDcraft patches in your patch unmodified as long as the use is similar (i.e. a piston_top, a pumpkin side, etc.)
  • You can release your patch anywhere you want (other websites or forum threads).
  • You can use PureBDcraft and your patch on commercial videos if you want to.
  • You must credit the work used in your art (but not in any way that suggests that the authors endorse you or your use of the work).

Layout guidelines for patch threads

Please be aware new threads may need to await for moderator approval before they appear.

Code: Select all

[img]IMAGE_FOR_THE_BANNER_OF_MOD.PNG (if available)[/img]
[title]Name_of_mod (only if no banner)[/title]

DESCRIPTION OF WHAT THE MOD DOES
(can be copy/pasted from the mod thread, just make sure it's not too long)

[buttons][url=LINK_TO_MOD_THREAD]Go to the Name_of_mod forum thread[/url][/buttons]

[subtitle]Downloads[/subtitle]
[b]for MC_VERSION[/b]
[spoiler][download][link=DIRECT_LINK_TO_DOWNLOAD_PATCH]128x[/link][/download]
[download][link=DIRECT_LINK_TO_DOWNLOAD_PATCH]64x[/link][/download][/spoiler]

[subtitle]Preview[/subtitle]
[gallery]URL_TO_PREVIEW_OF_TEXTURES.png (at least one image is mandatory[/gallery]
(wrap your images in [spoiler][/spoiler] if more than one image)

[subtitle]Changelog[/subtitle]
VERSION_OF_MOD and/or DATE_OF_RELEASE: what's changed
(wrap this section in spoilers if the changelog becomes more than 5 lines long).

[subtitle]Credits[/subtitle]
Do not include yourself, nor the mod maker when listing credits!
Only include Sphax if you used one of his textures for something.

Changelog

Show
2016-12-30 18:19 GMT: Added example mcmetas for MC1.11 patches
2016-06-10 18:42 BST: Added example mcmetas for MC1.9 patches
2016-03-18 16:54 GMT: Added information about MC1.9 patches
2016-03-04 14:24 GMT: Removed note about not using Imgur.com (because they finally unblocked us again)
2016-02-08 10:00 GMT: Added note about not using Imgur.com
2015-04-05 09:09 BST: Tidied up the wording about using unmodified textures from the main pack, tidied up other aspects of the rules and and added adf.ly rules
2014-07-18 21:05 BST: Tweaked the info about MC1.7 patches
2014-03-11 19:39 GMT: Added small change to the thread layout section in regards to saying what version of MC the patch is for
2013-11-26 17:38 GMT: Added information about MC1.7 resourcepacks to the "What to do" section.