Jump to content
Toggle menu
  • 3.1K articles
  • 4.4K files
  • 18 users
  • 91.5K edits
Ashenzari's Archive
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Current projects: Difference between revisions

From Ashenzari's Archive
imported>Draconius
No edit summary
imported>Draconius
No edit summary
Line 3: Line 3:
{{flavour|This page is a work in progress as of 2026. Please add your name to projects to claim/contribute to them, feel free to add your own ideas in the bottom section, or discuss ideas in the Discussion tab.''}}
{{flavour|This page is a work in progress as of 2026. Please add your name to projects to claim/contribute to them, feel free to add your own ideas in the bottom section, or discuss ideas in the Discussion tab.''}}


CrawlWiki is growing in size with more than [[Special:Statistics|400 registered users]]. To track what we are doing, and show what editors could chose to work on, we have created this list of current projects.
CrawlWiki is growing in size with more than [[Special:Statistics|400 registered users]]. To track what we are doing, and show what editors could choose to work on, we have created this list of current projects.


== Current Projects ==
== Current Projects ==
Line 11: Line 11:
|-
|-
| '''0.35 Update Project'''
| '''0.35 Update Project'''
| See [[Current projects/0.35 update project|0.35 Update Project]] once features have been frozen for this cycle. Add the [[Template:CBA]] for upcoming trunk changes where applicable.  
|Add the [[Template:CBA]] for upcoming trunk changes where applicable. (CBA: Crystal Ball Articles; used to note future changes to the game coming to Trunk.)
If the CBA is in reference to a specific commit on GitHub, reference it inside the CBA Template by adding:
*<code><nowiki> <ref>[https://github.com/crawl... Name of Commit]</nowiki></ref></code>
See [[Current projects/0.35 update project|0.35 Update Project]] once features have been frozen for this cycle.  
|All  
|All  
|Active
|Active
Line 30: Line 33:
|Ongoing
|Ongoing
|-
|-
| ''Outdated CBA articles''
| ''Outdated CBA Updating''
| [[:Category:Outdated_Crystal_Ball_Articles]]. These articles have <nowiki>{{CBA}}</nowiki> template for versions which already have been released, one should verify that change is already in the article (sometimes it was applied automatically, like monster stat change) or update the article according to the change. CBA part should be re-formulated as an entry in history, usually in past tense e.g. <code>Prior to version <nowiki>0.XX</nowiki> this was ...</code>
| [[:Category:Outdated_Crystal_Ball_Articles]]. These articles have the <nowiki>{{CBA}}</nowiki> template (in the history section of the page), which is used to note future changes to the game coming to Trunk. For versions that have already been released, editors should verify that the change is already in the article (sometimes it was applied automatically, like monster stat changes) or update the article according to the change. The CBA part should be re-formulated as an entry in history, usually in past tense e.g. <code>Prior to version <nowiki>0.XX</nowiki> this was ...</code>
| All
| All
|Ongoing
|Ongoing

Revision as of 03:09, 22 September 2026

Ashenzari's Archive
Links
This page is a work in progress as of 2026. Please add your name to projects to claim/contribute to them, feel free to add your own ideas in the bottom section, or discuss ideas in the Discussion tab.

CrawlWiki is growing in size with more than 400 registered users. To track what we are doing, and show what editors could choose to work on, we have created this list of current projects.

Current Projects

Project Goal Contributor(s) Status
0.35 Update Project Add the Template:CBA for upcoming trunk changes where applicable. (CBA: Crystal Ball Articles; used to note future changes to the game coming to Trunk.)

If the CBA is in reference to a specific commit on GitHub, reference it inside the CBA Template by adding:

  • <ref>[https://github.com/crawl... Name of Commit]</ref>

See 0.35 Update Project once features have been frozen for this cycle.

All Active
Talisman Timing For 0.35: Go through all Talisman and Shapeshifting related pages looking for references to the timing for entering a form. Entering a form is planned to be correctly set to 5 turns in Trunk soon. Anyone Waiting until Feature Freeze
Unstub-a-dub-dub Add anything you can to any of the pages in Category:Stubs. If you add a lot of stuff, remove {{stub}}. All Ongoing
Missing pages Special:WantedPages, Special:WantedTemplates, Special:WantedFiles, Special:WantedCategories. This happens when pages link to something that doesn't exist yet. Aim to keep these wanted files empty! All Ongoing
Outdated CBA Updating Category:Outdated_Crystal_Ball_Articles. These articles have the {{CBA}} template (in the history section of the page), which is used to note future changes to the game coming to Trunk. For versions that have already been released, editors should verify that the change is already in the article (sometimes it was applied automatically, like monster stat changes) or update the article according to the change. The CBA part should be re-formulated as an entry in history, usually in past tense e.g. Prior to version 0.XX this was ... All Ongoing

Project Ideas For Adoption

Project Goal Status
Auto Extract Stats Changes Comment from Reddit user kibwen: "One thing that would alleviate the need to constantly update the wiki for each new release would be a companion website that automatically extracts information from the source of the game itself, things like monster stats, item descriptions, spell lists, basically anything that you can bring up via the ?/ in-game search. Such a database would likely require a negligible amount of storage per version (I'm guessing less than 1MB), and with a JSON interface it could then be used to power things like the infoboxes on the wiki (and it could also have a web interface of its own, of course)." Thoughts on feasibility/usefullness welcomed in Discussion Tab.
Updating pages to 0.34 Go through pages that's still relevant from 0.33 and before to update them to the 0.34 version, to be able to automatically update pages with untouched features to 0.35 when it release. (Note: this turns out to be hundreds of pages per version; see Category:0.33_articles for example. Still a good but ambitious idea.) Really big work, but would smooth out 0.35 release.
Your Idea Here Write it in... Ongoing