Gifts

Fields of Mistria Gift Guide With Pictures: Rights Status

Direct answer

This is a text-first Fields of Mistria gift guide with pictures, not a published image gallery. The collected sources support a visual card format for each character, but they do not include reusable portrait or item image files. A safe guide should pair a licensed character image with birthday, romance status, named loved gifts, named liked gifts, and character-specific warnings. Until image provenance and reuse rights are checked, the text data below can be published but the missing pictures remain Pending verification (待确认). [S1][S2][V1]

Last verified 2026-08-16Evidence status: Needs review

Pending verification (待确认): this page contains clearly labeled community reports or details that the collected sources could not fully confirm.

At a glance

Quick Facts

Quick facts for Fields of Mistria Gift Guide With Pictures: Rights Status
Page scopeText-first guide; no published portrait or item gallery
Card fieldsCharacter, birthday, romance status, loved gifts, liked gifts, warnings, version, and review date
Image statusReusable files and permissions are not established in the collected sources
Sample dataJuniper, March, Ryis, and Caldarus examples are intentionally partial
StatusMissing pictures remain Pending verification (待确认)

Do this first

Fastest path

  1. Use the text cards for named birthdays and gift tiers while treating the page as text-first.
  2. Before adding an image, confirm the original file, character or item identity, rights, credit, and spoiler status.
  3. Keep loved and liked examples in separate labeled fields and verify incomplete rows in the current profile.
  4. Do not present a placeholder or external screenshot as a finished illustrated catalog.

Detailed guide

What the text-first guide supports

The GameSpot capture is organized as an image-heavy gallery, while the Pro Game Guides capture supplies more detailed version 1.0 gift text. Together they support a page design where each character has a distinct visual card instead of one dense, flattened master table. The extraction preserved labels and gift facts but not reusable screenshots, portraits, or item icons. [S1][S2]

Image-credit fragments in the source are not image licenses and do not authorize copying art into this site. A source link can show where a visual appeared without establishing that it may be republished. The page therefore treats visual assets as a separate verification task from the text preferences. [S1][S2]

Each card should show the character name, a verified portrait, birthday, and romance status before listing gifts. It should then include three to five unambiguous loved items, three to five practical liked items, and a warning area for documented dislikes or broad Junk and Weird Gift risks. A version or review date belongs on the card because preference guides and relationship systems can change. [S1][S2][V1]

The visual hierarchy should not make an attractive but uncertain item appear more authoritative than a text-only verified row. Every picture needs alt text naming the exact character or item, and the label must match the source data rather than a guessed object identity. If no verified image is available, a clearly labeled placeholder is safer than importing an unrelated game screenshot. [S1][S2]

Juniper sample card

The captured sample gives Juniper a Fall 26 birthday. Named loved examples are Crystal Rose, Fish Tacos, Golden Cookies, Mushroom Brew, and Pizza, while named liked examples are Middlemist, Morel Mushroom, Nettle, Red Wine, and Shadow Flower. These examples are intentionally short and should not be presented as her complete preference database. [S2]

A Juniper visual card could display those two tiers and a note that complete current reactions should be checked in the relationship profile. The broader source also warns about dislike categories, but a card should only attach a character-specific warning when the relevant row remains readable. This avoids turning a universal-looking design into an unsupported universal reaction claim. [S1][S2]

March and Ryis sample cards

March's sample lists a Spring 16 birthday with Dragon-Forged Bracelet, Gold Ingot, Meteorite, Perfect Copper Ore, and Sushi Platter as loved examples. Copper Ore, Iron Ore, Mocha, Silver Ore, and Hot Chocolate are liked examples in the same capture. A March card should keep perfect ore and ordinary ore in separate tiers because similar names do not mean identical reactions. [S2]

Ryis's sample lists a Spring 4 birthday and names Golden Bristle, Golden Bull Horn, Hard Wood, Lobster Roll, and Veggie Sub Sandwich as loved examples. Bristle, Glass, Lilac, Stone, and Wood are liked examples, giving his card a construction and ranching-material theme. That theme helps scanning but should not be used to add unlisted building materials. [S2]

Caldarus sample card

Caldarus has a Spring 25 birthday in the sample data. Apple Honey Curry, Fried Rice, Harvest Plate, Seafood Boil, and Sushi Platter are loved examples, while Chocolate Cake, Fish Tacos, Marigold, Pumpkin Pie, and Vegetable Quiche are liked examples. His card should also be spoiler-aware because portrait or relationship imagery may reveal a later form. [S2]

The gift material elsewhere warns that Dragon Parts can be poor Caldarus gifts, showing why a visual guide needs a warning field as well as favorite icons. An image of a dragon-themed object could otherwise encourage exactly the wrong inference. Use the preference label alongside the icon and do not let theme replace source-backed reaction data. [S1][S2]

Version 1.0 relationship context

The official version 1.0 announcement confirms 10-heart proposal and wedding events, marriage, and children. The Pro Game Guides capture is presented as a version 1.0 gift guide, while the GameSpot opening retains older Early Access framing and an earlier romance group. Current cards should therefore use the newer relationship context and label older roster statements as historical. [S1][S2][V1]

Seridia's complete preference list was still being confirmed in the captured current-style guide. A visual design can make an incomplete card look finished, so it needs an explicit Pending verification (待确认) state rather than blank icons that readers may interpret as neutral gifts. The same rule applies whenever a flattened source table loses item boundaries. [S2]

Image and data publication checklist

Before adding any picture, confirm the original file, rights or permitted reuse, accurate character or item identity, and spoiler status. Before adding any gift, confirm the recipient, exact item name, preference tier, and current version context. Keep source links visible so a later editor can recheck both asset and data provenance. [S1][S2]

The resulting page can still be useful before the artwork review is complete because the text cards answer which fields and sample gifts are supported. It should not advertise itself as a finished illustrated catalog while the binaries and licenses are absent. This evidence-first treatment prevents image-credit noise, old roster data, and malformed source rows from becoming polished but unreliable guidance. [S1][S2][V1]

Conditions and exceptions

Version, conditions & exceptions

The Pro Game Guides capture is framed as version 1.0, while the gallery capture retains older Early Access context; image rights and complete current rows remain unresolved.

Last verified 2026-08-16. Unresolved details are intentionally marked Pending verification (待确认).

Evidence trail

Sources & last verified

This page is limited to the collected sources below. Source conflicts, missing image data, and version-sensitive details remain labeled instead of being filled with guesses.

Last verified: 2026-08-16

Continue exploring

Evidence pack processed August 15, 2026 · Page updated 2026-08-16