Release v0.1.4 with terrain rescanning and owner-published map updates
All checks were successful
Deploy MineGeo to Dokploy / deploy (push) Successful in 6m26s
All checks were successful
Deploy MineGeo to Dokploy / deploy (push) Successful in 6m26s
This commit is contained in:
37
MineGeo community report.txt
Normal file
37
MineGeo community report.txt
Normal file
@@ -0,0 +1,37 @@
|
||||
MineGeo community improvement report
|
||||
|
||||
28 October 2026 • Review of the live homepage and Discord server
|
||||
|
||||
Make it easy for new players to start a game, find support and discover community maps. The server already has English and Russian channels, a shared support selection, announcements and a server guide.
|
||||
|
||||
Changes made
|
||||
|
||||
Updated the Discord server description to explain the game, community maps and bilingual support. Combined support selection into the existing language answers and removed the duplicate support question. Clarified the language and notification questions in English and Russian. Created the map-showcase forum with bilingual posting guidance and an optional onboarding answer. The English and Russian support channels now direct players to the bug button on the site. Sending messages and thread replies is denied to @everyone in both channels; administrator privileges and explicit role overrides can still affect access.
|
||||
|
||||
Recommended next steps
|
||||
|
||||
Make the first journey obvious: link the server guide to Play and maps, the field guide, official links and the site support button. Test it using a normal member account.
|
||||
|
||||
Encourage members to use the new map-showcase forum for one post per map, with a link, screenshots and spoiler warnings. Review its activity before adding more channels.
|
||||
|
||||
Run a small recurring community challenge: select one map, publish the deadline and rules, and invite players to share scores without revealing locations until the event ends.
|
||||
|
||||
Give players an optional map creator or event notification choice in onboarding, linked to a real channel or role. Keep notifications opt-in and use clear bilingual labels.
|
||||
|
||||
Continue applying English and Russian labels consistently across onboarding and the server guide.
|
||||
|
||||
Replace the image-only rules with accessible text in both languages and clarify how to report harassment or unsafe content. Keep the existing rules until the replacement is agreed.
|
||||
|
||||
Review the duplicate general and voice channels as membership grows; retain them for now and consolidate only after checking activity and existing content.
|
||||
|
||||
On the homepage, distinguish production maps from test content. The live page showed two published maps, including one labelled TEST, and two ranked players at review time.
|
||||
|
||||
Add a short first-game walkthrough and a prominent way to discover community maps. Explain browser and desktop options and link creators to the capture and publishing guide.
|
||||
|
||||
Test the support journey end to end in both languages, including mobile navigation, the bug button, submission confirmation and how users follow up. This review did not submit a real report.
|
||||
|
||||
Scope and limitations
|
||||
|
||||
The site observations are from the live homepage, not a full functional or accessibility audit. Discord permissions were reviewed in the owner account; test with a regular member to confirm effective permissions. Existing channel history was preserved.
|
||||
|
||||
Sources: https://minegeo.site/ • https://forum.minegeo.site/ • MineGeo Discord server
|
||||
Reference in New Issue
Block a user