Wiki Exporter: Difference between revisions
CptTwinkie (talk | contribs) m (→Known issues) |
CptTwinkie (talk | contribs) mNo edit summary |
||
(16 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{SEO|image_url=http://www.medievalengineerswiki.com/images/3/30/Export1.png|description=[OBSOLETE] Due to exports being done by Keen SWH staff, it was decided that the exporter would no longer be merged with the public version of the game.}} | |||
{{Obsolete|0.6|0.6|Due to exports being done by Keen SWH staff, it was decided that the exporter would no longer be merged with the public version of the game.}} | |||
The [[Wiki Exporter|wiki exporter]] is a work-in-progress tool for exporting pre-formatted text and icons from Medieval Engineers. | The [[Wiki Exporter|wiki exporter]] is a work-in-progress tool for exporting pre-formatted text and icons from Medieval Engineers. | ||
{{Version <!-- Do not change the version until the entire page is up-to-date --> | |||
|release=0|major=5|minor=X|suppress=true}} | |||
==How-to operate the exporter== | ==How-to operate the exporter== | ||
*Open Medieval Engineers and load any creative world. It is very important to not have any mods loaded in the world as mods will change the information that is exported. | *Open Medieval Engineers and load any creative world. It is very important to not have any mods loaded in the world as mods will change the information that is exported. | ||
Line 5: | Line 13: | ||
*Click the Medieval button | *Click the Medieval button | ||
*Check the Wiki box. This will open the Wiki Debug Screen panel. | *Check the Wiki box. This will open the Wiki Debug Screen panel. | ||
*Move your mouse to the | *Move your mouse to the export button of your choice. | ||
*Hold the Alt key and click the button. A cog icon will appear while the game is exporting files. This could take some time...as much as a minute or two. | *Hold the Alt key and click the button. A cog icon will appear while the game is exporting files. | ||
{{TextBox|This could take some time...as much as a minute or two.}} | |||
[[File:Export1.png|frameless|600px|center]] | [[File:Export1.png|frameless|600px|center]] | ||
Line 16: | Line 29: | ||
[[File:Export2.png|frameless|600px|center]] | [[File:Export2.png|frameless|600px|center]] | ||
==Using | ==Using Export Blocks== | ||
The block exporter will make a txt file for every Public and GUI Visible block in the game. Additionally, Block Variants will be included as they are in the toolbar configuration screen of the game (g-menu). | The block exporter will make a txt file for every Public and GUI Visible block in the game. Additionally, Block Variants will be included as they are in the toolbar configuration screen of the game (g-menu). | ||
The txt files are formatted closely to what should be included in the wiki and they can be copied and pasted, in their entirety, into matching wiki pages. Each file will contain an icon list. This is made necessary by the mechanism of layered icons in Medieval Engineers. The number of icon layers is unpredictable as it is at the discretion of the game designers how many layers to use. Choose an appropriate icon template to move to the top of the page as the preview image and discard the rest. | The txt files are formatted closely to what should be included in the wiki and they can be copied and pasted, in their entirety, into matching wiki pages. Each file will contain an icon list. This is made necessary by the mechanism of layered icons in Medieval Engineers. The number of icon layers is unpredictable as it is at the discretion of the game designers how many layers to use. Choose an appropriate icon template to move to the top of the page as the preview image and discard the rest. | ||
The exported text should serve as the complete data for all of the block pages on the wiki. Keeping this data standard makes it much easier to check against updates for changes. The distinction should be made, however, that each page should have both data and description. Especially with the exporter available, efforts can be made to describe blocks and block groups in plain text as summary information. | The exported text should serve as the complete data for all of the block pages on the wiki. Keeping this data standard makes it much easier to check against updates for changes. The distinction should be made, however, that each page should have both data and description. Especially with the exporter available, efforts can be made to describe blocks in plain text as summary information. | ||
==Using Export Groups== | |||
The group exporter will make a txt file for every group of blocks in the game. Each file name will be prefixed with '''GROUP_'''. | |||
The txt files are formatted closely to what should be included in the wiki and they can be copied and pasted, in their entirety, into matching wiki category pages. | |||
The exported text should serve as the complete data for the block group category pages on the wiki. Keeping this data standard makes it much easier to check against updates for changes. The distinction should be made, however, that each page should have both data and description. Especially with the exporter available, efforts can be made to describe block groups in plain text as summary information. | |||
==Using the icons== | ==Using the icons== | ||
Attempts have been made to select and export appropriate icons for each block that is exported. There are some exceptions, listed below, that prevent directly exporting the appropriate icon for a block or item. | Attempts have been made to select and export appropriate icons for each block that is exported. There are some exceptions, listed below, that prevent directly exporting the appropriate icon for a block or item. | ||
Line 29: | Line 50: | ||
''It is strongly recommended that all image files used on the wiki should match their original name. This may mean renaming existing images on the wiki. Care should be taken to update other pages that use the image. To rename an existing image, hover over the More tab at the top of the page and choose Move. There is little point to leaving a redirect, especially if you make sure to update all of the pages.'' | ''It is strongly recommended that all image files used on the wiki should match their original name. This may mean renaming existing images on the wiki. Care should be taken to update other pages that use the image. To rename an existing image, hover over the More tab at the top of the page and choose Move. There is little point to leaving a redirect, especially if you make sure to update all of the pages.'' | ||
==Known issues== | ==Known issues== | ||
Icon/Image naming issues (The exporter should be renaming most things properly in the next release). | |||
*There are some exceptions that must be made to icon naming due to limitations in the wiki file name parser and the icon sources themselves. <br/>A notable issue with the wiki file name parser is that it is unable to distinguish between two files with spaces in their names that have the same ending. (e.g. Dish Goulash.png and Goulash.png would both be found when searching for Goulash.png. The wiki would then use whichever file was found first.) This creates the need to occasionally modify file names when conflicts arise. | |||
*A notable problem at this time is [[:File:IronOreIcon.png]]. | |||
**At this time the proper name, IronOre.png, is somehow causing a bug in the database and it will not display using that name. This substitute name will have to be used until the issue with the database can be solved. | |||
*Seedbags and melting recipes use multiple icon layers. It is necessary for those icons, to combine the layers using image editing software like photoshop, gimp, or paint.net that has layering support. This has already been done for existing items, however, the resulting files do not have consistent names in some cases due to naming conflicts. (e.g. The cabbage seeds use a composite icon made from the seedbag icon and the cabbage icon. Naming the icon cabbage.png would conflict with the existing cabbage.png icon used for the gatherable/growable cabbage item.) | |||
At this time the proper name, IronOre.png, is somehow causing a bug in the database and it will not display using that name. This substitute name will have to be used until the issue with the database can be solved. | |||
Seedbags and melting recipes use multiple icon layers. It is necessary for those icons, to combine the layers using image editing software like photoshop, gimp, or paint.net that has layering support. This has already been done for existing items, however, the resulting files do not have consistent names in some cases due to naming conflicts. (e.g. The cabbage seeds use a composite icon made from the seedbag icon and the cabbage icon. Naming the icon cabbage.png would conflict with the existing cabbage.png icon used for the gatherable/growable cabbage item.) |
Latest revision as of 18:06, 17 August 2018
This item became obsolete in version 0.6. It was removed, or will be removed, in version 0.6.
Due to exports being done by Keen SWH staff, it was decided that the exporter would no longer be merged with the public version of the game.
The wiki exporter is a work-in-progress tool for exporting pre-formatted text and icons from Medieval Engineers.
Version: | 0.5 |
How-to operate the exporter
- Open Medieval Engineers and load any creative world. It is very important to not have any mods loaded in the world as mods will change the information that is exported.
- Press Shift+F12 to open the developer screen
- Click the Medieval button
- Check the Wiki box. This will open the Wiki Debug Screen panel.
- Move your mouse to the export button of your choice.
- Hold the Alt key and click the button. A cog icon will appear while the game is exporting files.
Export location
The files will be exported into a folder in your Medieval Engineers appdata. It will be named WikiExport followed by an underscore and a ISO date code.
The appdata folder can be accessed through any explorer windows, the start menu search, or the run dialog (Win+R) by typing
%appdata%
Inside you will find the MedievalEngineers folder that contains the WikiExport folder (hereafter referred to as the export folder).
Using Export Blocks
The block exporter will make a txt file for every Public and GUI Visible block in the game. Additionally, Block Variants will be included as they are in the toolbar configuration screen of the game (g-menu).
The txt files are formatted closely to what should be included in the wiki and they can be copied and pasted, in their entirety, into matching wiki pages. Each file will contain an icon list. This is made necessary by the mechanism of layered icons in Medieval Engineers. The number of icon layers is unpredictable as it is at the discretion of the game designers how many layers to use. Choose an appropriate icon template to move to the top of the page as the preview image and discard the rest.
The exported text should serve as the complete data for all of the block pages on the wiki. Keeping this data standard makes it much easier to check against updates for changes. The distinction should be made, however, that each page should have both data and description. Especially with the exporter available, efforts can be made to describe blocks in plain text as summary information.
Using Export Groups
The group exporter will make a txt file for every group of blocks in the game. Each file name will be prefixed with GROUP_.
The txt files are formatted closely to what should be included in the wiki and they can be copied and pasted, in their entirety, into matching wiki category pages.
The exported text should serve as the complete data for the block group category pages on the wiki. Keeping this data standard makes it much easier to check against updates for changes. The distinction should be made, however, that each page should have both data and description. Especially with the exporter available, efforts can be made to describe block groups in plain text as summary information.
Using the icons
Attempts have been made to select and export appropriate icons for each block that is exported. There are some exceptions, listed below, that prevent directly exporting the appropriate icon for a block or item.
Most of the icons in the game are in the dds format at this time. Conversion to png is necessary before uploading images to the wiki. See Converting Game Icons For The Wiki for instructions. At this time, most of the icons have already been converted and uploaded. If you find an icon missing from a template it is best to check if there is an existing icon already uploaded with a different name. The easiest way to do this is to preview the template, open the link to the page associated with the missing icon in a new browser tab. There you will likely find the icon as the page thumbnail which you can click on to see file information.
It is strongly recommended that all image files used on the wiki should match their original name. This may mean renaming existing images on the wiki. Care should be taken to update other pages that use the image. To rename an existing image, hover over the More tab at the top of the page and choose Move. There is little point to leaving a redirect, especially if you make sure to update all of the pages.
Known issues
Icon/Image naming issues (The exporter should be renaming most things properly in the next release).
- There are some exceptions that must be made to icon naming due to limitations in the wiki file name parser and the icon sources themselves.
A notable issue with the wiki file name parser is that it is unable to distinguish between two files with spaces in their names that have the same ending. (e.g. Dish Goulash.png and Goulash.png would both be found when searching for Goulash.png. The wiki would then use whichever file was found first.) This creates the need to occasionally modify file names when conflicts arise. - A notable problem at this time is File:IronOreIcon.png.
- At this time the proper name, IronOre.png, is somehow causing a bug in the database and it will not display using that name. This substitute name will have to be used until the issue with the database can be solved.
- Seedbags and melting recipes use multiple icon layers. It is necessary for those icons, to combine the layers using image editing software like photoshop, gimp, or paint.net that has layering support. This has already been done for existing items, however, the resulting files do not have consistent names in some cases due to naming conflicts. (e.g. The cabbage seeds use a composite icon made from the seedbag icon and the cabbage icon. Naming the icon cabbage.png would conflict with the existing cabbage.png icon used for the gatherable/growable cabbage item.)