Medieval Engineers Wiki:News
This article is a stub. You can help Medieval Engineers Wiki by expanding it. Click to edit this page
This article is a draft. You can help Medieval Engineers Wiki by completing it. Click to edit this page
2018-04-11 0.6.3 Update
All data has been updated to 0.6.3. Template:Stat Effects has been updated to reflect the new stats system. Enjoy the update :D ~CptTwinkie
2018-02-02 Update Complete
I've finished copying the export data. The wiki is now (mostly) up to date for 0.6. There may be some categories that need to be touched up. I plan to go through all of them one last time today. Blocks, block groups, items, quests, and schematics are all up to date. Everything is now fair game for descriptions and improvements. ~CptTwinkie
2018-01-05 Preparations Complete (mostly)
Twenty Eighteen...that phrase will take a while to get used to. I have written a rather large news post and changelog so I'm making use of that nice expandable template I worked out. There have been a lot of organizational changes lately but no content. As far as I can tell, I've reached the end of 0.6 organization and I'm ready to move on to data exporting. Hopefully I'll be flooding the wiki with data updates soon. ~CptTwinkie
| About History and Tags |
|---|
HistoryIn the past few days I've focused a lot on history in the wiki. I realized, very slowly I know, that keeping history for an early access game will have some challenges. I had already done some research about wiki history so I knew some methods but it was only now that I rationalized those methods to our humble ME Wiki. There are two main/popular/easy methods of history for any given article on a wiki: history references and sub-page archiving. References are the easiest because you only need to link to a history state of the page and you're done. This works well for, what I call, non-functional pages. You can view them and with a little effort you can even update them (edit → save → undo → save → new history created). This doesn't work well for functional pages, things like categories and templates. A good example that we have is Category:Schematics. Schematics have changed completely from 0.5 to 0.6 and they cannot be updated. The old schematics no longer exist and a bunch of new ones are in their place with new rules. This is where archiving comes in. Move the category to Category:Schematics/0.5, re-link all of the schematic pages, create a new Category:Schematics and add new schematics pages to it. This gives us separate content, separate histories, and easy updates. It's also a lot more work. With all of this history activity going on I realized that a lot of pages were acquiring links to the past. I started making a history template when I realized that our two kinds of history keeping (references and archiving) called for two kinds of template (it's technical :P). So I made Template:HistoryId, which uses reference ID's, and Template:HistorySub, which uses archived sub-pages. They have identical formatting to each other and the Version template. Place just after the version on pages. TagsDo you look at the Recent changes page? As an admin I'm on that page all the time. Like right now I'm looking up my own recent changes to write this news. With so many changes happening it's not always clear why a change was made. Sure, I could go back to adding messages every time I save a page but that takes time and I can't always remember how I worded something before...so I don't do it. I know, lazy editor. Those messages are still an option for something truly out of the ordinary. For the most part, I tend to do mass updates for simple things like template changes and re-linking. Having a way to quickly identify those common action in the recent changes is really attractive to me. It turns out that the MediaWiki software has my back! I've added some basic tags for template updates, linking, categorization, pasting game data, and importing pages (yes, I have an offline test wiki I can export things from). So far I've only found one thing confusing. When I change a template or category and I need to touch all of the linked pages, should I use Tag:Template and Tag:Categorization or Tag:Links? What I decided is that I will use Tag:Links anytime I'm just changing the target of something. If I move/rename a category - links. If I rename a template or image - links. If I move pages from one category to another (reorganization) - categorization. If I update a template with different attributes - template. |
Change Log
- Created Template:HistorySub to link archived sub-pages.
- Created Template:HistoryId to link history ID's.
- Created Template:Anchor because it seemed like a good idea at the time.
- Created Template:TransclusionNotice, used on Taxation which is transcluded into Claim Block and Wooden Claim Block.
- Created Template:Quest prototype. It has some cool categorization behavior but, I had to guess at the information I would export from quests so, it may not be complete.
- Updated Template:Crafting Blueprint with more concise labels.
- Documented Template:Fullurl, which is actually broken but does exactly what it needs to do so don't judge the source.
- Fixed Template:Infobox/End by adding more robust linking to work properly with categories.
- Fixed Template:Version to have consistent padding.
- Archived Category:Research and Quests/Schematics.
- Archived Template:Resource.
- Archived Template:Crafting Schematic.