Vintage Story Wiki:Community noticeboard

From Vintage Story Wiki
Community noticeboard
This page serves as a central hub for discussion relating to the Vintage Story Wiki.

Wiki news

The wiki is currently ondergoing a heavy overhaul, as a majority of the templates and guidelines were fairly outdated or lacking in information to give an easy onboarding experience for new editors.

If stuff occasionally looks broken, do not fret, as we're doing our best to get everything adjusted to the changes!


Wiki wishlist
As the wiki is developer-run, we cannot spontaneously add new features or change the global styling on our own. As such, this wishlist has been put in place in order to request various extensions or changes that only Tyron can make.

Please do not add anything here unless the wiki community has first come to a consensus about requesting it.

Math
  • Modding:Matrix_Operations currently uses CSS hacks to display the matrices. Standard math syntax would be easier to maintain.
Short URL
  • It might be easier to put in place a short URL at the same time as updating MediaWiki so that the wiki's address becomes something closer to https://wiki.vintagestory.at/wiki/<page>.
Replace the creative teleporter block in the top-left with Vintage Story's logo instead
Extension:AdvancedSearch
Extension:Loops
  • Adds logic loops - self-explanatory.
  • Once again, would help reduce clutter in templates and allow for more dynamic templates.

Requests

If you'd like to request and/or put forward a suggestion for anything in the wiki, feel free to edit it in below.

Work queues

We have a couple of rudimentary ones:

However, I'd love to see/make/maintain another one for specifically updating translation tags, since translation is both one of the easiest ways to get started, but the easiest to "mess up" and overwrite (plus there are many pages in English that are updated for the latest version of VS, but have not been re-marked for translation, meaning their translated pages may be months or years out of date).

Anyone got more? -- Veerserif (talk here or on Discord) 16:12, 8 August 2022 (UTC)


Incorporate 1.19 changes

  • Mini Dimensions
  • First-person mode changes
  • Chat commands code rewrite
  • World Edit commands
  • Live preview during schematic import
  • Chiseling system upgrades
    • Can use knife to remove decor layers again
  • Cave-in system
  • Deer (Barrowisp started)
  • Animal catching - which page(s)?
  • Reworked ruins
  • New Accessibility settings (Barrowisp started)
  • Command Handbook in Creative mode (Barrowisp will start)
  • Scroll racks
  • World map tweaks
    • medieval looking world map
    • Prospecting pick heatmap
    • commands for selecting map type
  • Character selector tweaks
    • new 'Last selection' button
  • Overhauled/New 3D models for troughs, buckets and seeds (Barrowisp will start)
  • Frost overlay visuals on creatures/traders
  • Aged fancy bed, Resonance Archives clutter bed
  • deadfungi and spotty mold decor layer blocks
  • Renamed 3 blocks:
    • Crimson King maple=>Crimson maple
    • Green Spire cypress=>Mediterranean cypress
    • Stone bricks (bricks?? or blocks?) => Ashlar blocks
  • Raccoon and Fox pups now spawn in the world (Barrowisp will start)
  • Gameplay balancing changes
    • Double-headed drifters and Bells drops
    • Double-headed drifters health
    • effects of wetness on body temperature
    • fur clothing set warmth values
    • Wooden paths can now be made with any type of board
    • "Plank path" recipe
    • Archimedes Screw
    • combustibility
    • Night vision goggle fuel
    • flax crop yield (Barrowisp will start)
  • worldconfig option to change the health regeneration speed (Barrowisp will start)
  • new methods to light torches
  • Capability for server owners to compact savegames
  • More streamlined introduction into the game's mechanics (Barrowisp will start)
  • tarnished steel beams
  • Oiled hides mention a bit more on how curing them works
  • Additional command tweaks (Barrowisp will start)
    • Added ability to individually enable world maps
    • Added commands .debug plrattr [path] and /entity cmd [selector] attr [path] to read player/entity attributes.
    • /entity command
  • Reduced default SpawnCapPlayerScaling from 0.75 to 0.5
  • Don't show < > buttons on books with only 1 page (Barrowisp will start)
  • glider fall damage
  • Adjusted prices for a couple of trader goods (Barrowisp will start)
  • Added "Macro Editor" button to the Controls settings tab
  • Sleeping and healing
  • Modding stuff
    • texture atlas - done, connected textures
    • wearable animation support, new data format for animation
    • minimal cellars
    • Block randomizer
    • other modding stuff I don't understand

Barrowisp (talk) 06:24, 29 October 2023 (UTC)

Barrowisp (talk) 18:14, 30 October 2023 (UTC)

  • Cracked vessel page needs Arctic supplies section added with loot tables. I suggest a History section, too. Data can be found at line 234 of vssurvivalmod-master\Block\BlockLootVessel.cs
    • While at it, check whether the loot tables for other categories have changed.
    • Update the page's game version.

Barrowisp (talk) 04:45, 12 September 2023 (UTC)

  • The Traders page could benefit from a basic infobox-with-image
    • Add a Dialogs section between Transactions and Hostility
    • But which file(s) contains the lines of dialog?
      • assets\survival\config\dialogue\trader.json and assets\survival\config\dialogue\treasurehunter.json

Barrowisp (talk) 06:49, 12 September 2023 (UTC)

  • Fertilizer currently redirects to [1] but I think it merits its own page. I would work on the content, but need to first figure out how to undo a redirect.
    • Add sections for how to obtain each fertilizer, with pics.
    • Include the relatively new visual effect of fertilizer.
    • Include a History section.
    • Include a Notes section with advice on how to make rot in bulk for compost.

Barrowisp (talk) 06:49, 12 September 2023 (UTC)

Extension wishlist

If we are going to keep using the Translate extension, maybe getting Extension:TranslationNotifications will help us retain volunteer translators? -- Veerserif (talk here or on Discord) 16:59, 8 August 2022 (UTC)

I can see it being eventually useful, and probably good to have for the time being - but seeing as most translations are barely even started, it might not get much use for now? Sana (talk) 02:10, 9 August 2022 (UTC)

New permissions hierarchy

Right now, anyone with edit permissions has a lot of edit permissions, including default access to the Template namespace, translation administration etc. I would like to ask for:

  • A second "tier" of user, maybe trusteduser or something like that, granted on request via Discord or similar
  • Page protection on the whole Template namespace (and maybe even translation administration, though that would significantly slow the work of translation markup), requiring a "trusted user" userright to edit

Although we haven't really had issues with vandalism, I have definitely seen issues arising from enthusiastic application of translation tags breaking templates - see the version history of {{Breaking}} for one example. -- Veerserif (talk here or on Discord) 16:59, 8 August 2022 (UTC)

To add to this, I've looked through our current user groups, and I'm noticing a few of issues.

  • For one, Confirmedusers and editor seem to both have the exact same rights, so getting rid of one would clean things up a bit.
  • Second, it looks like all users can translate pages as well as review them, which might not be preferable.

-- Sana (talk) 02:42, 9 August 2022 (UTC)

Yeah, I'm with your first point completely (or one of those becomes the new "trusted" user group).
With regards to translation rights, I'd be completely OK with setting up one of the "basic" categories to have both the translate and translate-messagereview userrights, and put pagetranslation and translate-manage behind "trusted" users. This would mean it's relatively easy to get started with actually translating content into another language, and harder to mark up pages for translation (which carries obviously the risk of breaking the pages in question). As a historical note, I think the original rationale was to make it really easy to mark up any page for translation to get the ball rolling, but I think that was also before seeing the potential downsides of, eh, messily-tagged pages.
Also, certain high-traffic pages should probably also get page protected, such as the Main Page. -- Veerserif (talk here or on Discord) 13:59, 10 August 2022 (UTC)

Reduce Code Chaos

I've been trying to figure out how this wiki works and what would be the best way to get something done, but I keep running into difference in code, confusion on how something should work, and running into half-finished systems (i.e. Grid/Crafting). A focus towards sweeping through old pages, even those that may not need to be changed, and standardizing a method of source editing will make it easier in the future to understand, find and edit pages. It will probably take a lot of work in the beginning, and may start to fall behind on new content updates, but by making everything standardized, it will potentially speed up learning and editing for other people, leading to less burnout and confusion. -- RathfulConcepts (User talk) 14:35, 16 March 2023 (EST)

For the record, on Grid/Crafting in particular, I've spent several months seeing how it works on other wikis and what work would be needed to overhaul e.g. the infoboxes. You can see how far I got on my user sandbox. I ran out of steam when it became abundantly clear to me that making it truly backwards compatible was a monumental task, far beyond my availability and ability. -- Veerserif (talk here or on Discord) 18:47, 8 January 2024 (UTC)


Editing articles
Hubs Community noticeboard
Guides How to help • How to translate the wiki
Styling Style guide • Versions


Retrieved from "https://wiki.vintagestory.at/index.php?title=Vintage_Story_Wiki:Community_noticeboard&oldid=179264"