Help:Editing - Revision history

Cobblemon: images

2025-12-19T17:32:30Z

images

← Older revision		Revision as of 17:32, 19 December 2025
Line 38:		Line 38:
	<gallery>		<gallery>
	Double block image dimensions.png \| Since the final stage of Hearty Grains is two standard blocks high, all stages should have the same image dimensions.		Double block image dimensions.png \| Since the final stage of Hearty Grains is two standard blocks high, all stages should have the same image dimensions.
			Hearty Grains (block, stage 6).png \| Hearty Grains at the final stage with reference removed.
	Hearty Grains (block, stage 0).png \| Hearty Grains at the first stage. Note that the image dimensions are the same.		Hearty Grains (block, stage 0).png \| Hearty Grains at the first stage. Note that the image dimensions are the same.
	</gallery>		</gallery>

Cobblemon: images

2025-12-19T17:29:54Z

images

← Older revision		Revision as of 17:29, 19 December 2025
Line 27:		Line 27:

	====Blocks====		====Blocks====
	For images of blocks, make sure the image dimensions conform to the size of a standard block. This ensures image uniformity, and will make transitioning between images cleaner for infoboxes and galleries. If a block is smaller than the standard block size, do not crop the image, revise the image dimensions to be equivalent to the dimensions of a standard block image instead. If a block is larger than a standard block like a door block, then revise the image dimensions to be that of an image that encompasses the amount of standard block sized spaces the block will take up.		For images of blocks, make sure the image dimensions conform to the size of a standard block. This ensures image uniformity, and will make transitioning between images cleaner for infoboxes and galleries. If a block is smaller than the standard block size, do not crop the image, revise the image dimensions to be equivalent to the dimensions of a standard block image instead.

	<gallery>		<gallery>
	Block image dimensions.png \| Apricorn block within a standard block for reference.		Block image dimensions.png \| Apricorn block within a standard block for reference.
	Red Apricorn (block).png \| Apricorn block with reference removed. Note that the image dimensions do not change.		Red Apricorn (block).png \| Apricorn block with reference removed. Note that the image dimensions do not change.
			</gallery>

			If a block is larger than a standard block like a door block, then revise the image dimensions to be that of an image that encompasses the amount of standard block sized spaces the block will take up. For example, since a door block takes up 2 vertical block spaces, the image dimensions should be equivalent to the dimensions of an image of two standard blocks stacked vertically.

			<gallery>
			Double block image dimensions.png \| Since the final stage of Hearty Grains is two standard blocks high, all stages should have the same image dimensions.
			Hearty Grains (block, stage 0).png \| Hearty Grains at the first stage. Note that the image dimensions are the same.
			</gallery>

			Crop and plant block models are commonly rotated 45° around the Y-Axis. This can make the model appear flat and two-dimensional when viewed isometrically. For blocks like these, rotate the block or camera view 45° around the Y-Axis before taking the image.

			<gallery>
			Red Apricorn Sapling (block).png \| A Red Apricorn Sapling.
	</gallery>		</gallery>

Cobblemon: Item images

2025-12-19T15:06:11Z

Item images

← Older revision		Revision as of 15:06, 19 December 2025
Line 32:		Line 32:
	Block image dimensions.png \| Apricorn block within a standard block for reference.		Block image dimensions.png \| Apricorn block within a standard block for reference.
	Red Apricorn (block).png \| Apricorn block with reference removed. Note that the image dimensions do not change.		Red Apricorn (block).png \| Apricorn block with reference removed. Note that the image dimensions do not change.
			</gallery>

			====Items====
			Images of item sprites can be directly taken from file assets. For block item images, i.e. block renders displayed in inventory slots, they can be taken from screenshots in-game, with a GUI scale set to 2. The image should be cropped to the dimensions of the item slot, this should result in a final 32px × 32px image.

			<gallery>
			Item slots.png \| A Healing Machine within an inventory.
			Item slot cropped.png \| The cropped item slot.
			Healing Machine.png \| The final image with the item slot background removed. Note that the image dimensions do not change.
	</gallery>		</gallery>

Cobblemon: /* Files */ link minecraft wiki rendering help article

2025-01-20T19:13:48Z

Files: link minecraft wiki rendering help article

← Older revision		Revision as of 19:13, 20 January 2025
Line 23:		Line 23:

	===Images===		===Images===
	For formality and standardization, an isometric view is preferred for images of in-game subjects like blocks. Avoid taking default in-game screenshots. Isometric projection renders can be generated through programs like ''Blockbench'' or through mods like ''Isometric Renders''.		::''Rendering Tips: [[minecraftwiki:Help:Isometric_renders\|Help: Isometric Renders]]''
			For formality and standardization, an approximate isometric view, or more accurately, a dimetric view, is preferred for images of in-game subjects like blocks. Avoid taking default in-game screenshots. Isometric projection renders can be generated through programs like ''Blockbench'', which provides the '''Isometric Right (2:1)''' viewing angle, or through mods like ''Isometric Renders''.

	====Blocks====		====Blocks====

Blob: /* Redirects */ don't use apricorns for this, use apricorns. it act the same.

2023-08-05T12:46:40Z

Redirects: don't use apricorns for this, use apricorns. it act the same.

← Older revision		Revision as of 12:46, 5 August 2023
Line 37:		Line 37:

	==Redirects==		==Redirects==
	Redirects can be done by creating an article with <code><nowiki>#REDIRECT [[article]]</nowiki></code> as the content. Redirects should be created sparingly, and should only be created to help users find articles. Redirects should never be linked to. Linking to a page with a different name can instead be done by separating the article title and some specified text with a vertical bar. For example, <code><nowiki>[[~~Apricorn~~\|~~apricorns~~]]</nowiki></code> will be displayed as ''[[~~Apricorn~~\|~~apricorns~~]]''.		Redirects can be done by creating an article with <code><nowiki>#REDIRECT [[article]]</nowiki></code> as the content. Redirects should be created sparingly, and should only be created to help users find articles. Redirects should never be linked to. Linking to a page with a different name can instead be done by separating the article title and some specified text with a vertical bar. For example, <code><nowiki>[[Link Cable\|link cables]]</nowiki></code> will be displayed as ''[[Link Cable\|link cables]]''.

Blob: /* Blocks */ image file change

2023-08-05T12:44:14Z

Blocks: image file change

← Older revision		Revision as of 12:44, 5 August 2023
Line 29:		Line 29:

	<gallery>		<gallery>
	~~block~~ image dimensions.png \| Apricorn block within a standard block for reference.		Block image dimensions.png \| Apricorn block within a standard block for reference.
	~~red apricorn~~ block.png \| Apricorn block with reference removed. Note that the image dimensions do not change.		Red Apricorn (block).png \| Apricorn block with reference removed. Note that the image dimensions do not change.
	</gallery>		</gallery>

Village: Redirecting

2023-05-13T16:38:12Z

Redirecting

← Older revision		Revision as of 16:38, 13 May 2023
Line 35:		Line 35:
	===Moving===		===Moving===
	If moving or renaming files, do not allow the old file name to redirect to the new one.		If moving or renaming files, do not allow the old file name to redirect to the new one.

			==Redirects==
			Redirects can be done by creating an article with <code><nowiki>#REDIRECT [[article]]</nowiki></code> as the content. Redirects should be created sparingly, and should only be created to help users find articles. Redirects should never be linked to. Linking to a page with a different name can instead be done by separating the article title and some specified text with a vertical bar. For example, <code><nowiki>[[Apricorn\|apricorns]]</nowiki></code> will be displayed as ''[[Apricorn\|apricorns]]''.

Village: update capitalization style

2023-05-13T16:22:17Z

update capitalization style

← Older revision		Revision as of 16:22, 13 May 2023
Line 6:		Line 6:

	===Capitalization===		===Capitalization===
	~~Subject or article~~ pages should ~~not be capitalized unless~~ the subject ~~is a proper noun~~. This guideline should also be followed when linking to other articles. For example, ''[[Poké Ball]]'' is capitalized, ~~while~~ ''[[~~Apricorn Tree\|apricorn tree~~]]'' is not.		Article pages should follow the capitalization of the subject if it appears in-game. This guideline should also be followed when linking to other articles. For example, the item ''[[Poké Ball]]'' is capitalized. Article page titles which do not refer to in-game subjects should be in sentence case, and lowercase when linked. For example, ''[[held items]]'' is not capitalized.

	===Point of View===		===Point of View===
Line 12:		Line 12:

	==Files==		==Files==
	File names should be ~~all lowercase~~. The Wiki will automatically capitalize it on the file's page. If the file name contains spaces, replace them with underscores.		File names should follow the capitalization of the subject. Files which do not refer to in-game subjects should be in sentence case. The Wiki will automatically capitalize it on the file's page. If the file name contains spaces, replace them with underscores before uploading. Once uploaded, the file can be linked using spaces.

	If there are multiple files with the same name, suffix the additional files with a descriptor. For existing cases of similar file names, like block and item sprites, item sprite files should take precedence and should have the original file name.		If there are multiple files with the same name, suffix the additional files with a descriptor surrounded by parenthesis. For existing cases of similar file names, like block and item sprites, item sprite files should take precedence and should have the original file name.

	For example, as <code>~~red_apricorn~~.png</code> denotes the item sprite image, the file name for the block render image should be <code>~~red_apricorn_block~~.png</code>.		For example, as <code>Red_Apricorn.png</code> denotes the item sprite image, the file name for the block render image should be <code>Red Apricorn_(block).png</code>.

	For blocks or other subjects that may have multiple variations like crop stages, add the variation label at the end of the file name. For block renders, this will come after <code>block</code>. For example, <code>~~apricorn_block_~~'''stage_1'''</code> or <code>~~healing_machine_block_~~'''charge_2'''</code>.		For blocks or other subjects that may have multiple variations like crop stages, add the variation label at the end of the file name. For block renders, this will be separated with a comma and come after <code>block</code>. For example, <code>Apricorn_Block_'''(stage_1)'''.png</code> or <code>Healing_Machine_(block,_'''charge_2)'''.png</code>.

	If an item has any additional models, such as Poké Balls when held in the main or off-hand, suffix the file name with <code>model</code>.		If an item has any additional models, such as Poké Balls when held in the main or off-hand, suffix the file name with <code>(model)</code>.

	===Images===		===Images===

Village: /* Images */

2023-04-18T02:25:27Z

Images

← Older revision		Revision as of 02:25, 18 April 2023
Line 24:		Line 24:
	===Images===		===Images===
	For formality and standardization, an isometric view is preferred for images of in-game subjects like blocks. Avoid taking default in-game screenshots. Isometric projection renders can be generated through programs like ''Blockbench'' or through mods like ''Isometric Renders''.		For formality and standardization, an isometric view is preferred for images of in-game subjects like blocks. Avoid taking default in-game screenshots. Isometric projection renders can be generated through programs like ''Blockbench'' or through mods like ''Isometric Renders''.

			====Blocks====
			For images of blocks, make sure the image dimensions conform to the size of a standard block. This ensures image uniformity, and will make transitioning between images cleaner for infoboxes and galleries. If a block is smaller than the standard block size, do not crop the image, revise the image dimensions to be equivalent to the dimensions of a standard block image instead. If a block is larger than a standard block like a door block, then revise the image dimensions to be that of an image that encompasses the amount of standard block sized spaces the block will take up.

			<gallery>
			block image dimensions.png \| Apricorn block within a standard block for reference.
			red apricorn block.png \| Apricorn block with reference removed. Note that the image dimensions do not change.
			</gallery>

	===Moving===		===Moving===
	If moving or renaming files, do not allow the old file name to redirect to the new one.		If moving or renaming files, do not allow the old file name to redirect to the new one.

Village at 01:28, 17 April 2023

2023-04-17T01:28:39Z

← Older revision		Revision as of 01:28, 17 April 2023
Line 21:		Line 21:

	If an item has any additional models, such as Poké Balls when held in the main or off-hand, suffix the file name with <code>model</code>.		If an item has any additional models, such as Poké Balls when held in the main or off-hand, suffix the file name with <code>model</code>.

			===Images===
			For formality and standardization, an isometric view is preferred for images of in-game subjects like blocks. Avoid taking default in-game screenshots. Isometric projection renders can be generated through programs like ''Blockbench'' or through mods like ''Isometric Renders''.

	===Moving===		===Moving===
	If moving or renaming files, do not allow the old file name to redirect to the new one.		If moving or renaming files, do not allow the old file name to redirect to the new one.