AssetStoreまとめ 割引情報 beta

- アセットの価格推移をリアルタイムにチェック -

Make noisy Unity YAML diffs readable and help teams resolve scene/prefab conflicts faster with semantic review and safe merge.MergeSight is a Unity Editor extension for semantic review and 3-way merge workflows for text-serialized Unity assets.The tool analyzes Unity YAML assets and presents object-level and property-level changes in a Unity Editor UI.It is built for practical Git workflows around scenes, prefabs, ScriptableObjects, and materials.It helps teams cut review time and resolve merge conflicts by turning raw YAML diffs into a Unity-aware view of objects, components, hierarchy, properties, and references.Main features:- Review changed assets with a semantic diff tree and summarized changes.- Compare sources by branch or commit, including Working Tree scenarios.- Search and filter changed assets by type, path, name, and Git status.- Semantic tree changes filters: filtering by name, change kind, and item type.- Resolve 3-way merge conflicts with conflict classification and merge preview.- Use resolution actions such as Auto-resolve safe, Take Base/Ours/Theirs, and selected-scope resolve.- Apply merged results with unresolved-decision checks, backup file creation, and validation.- Export summaries as Markdown or JSON for code review and reporting.VCS Supported:Git, Perforce, Unity Version Control / Plastic SCM, or SVN.Learn more about MergeSightJoin our DiscordDocumentationSemantic ReviewMergeSight converts Unity YAML diffs into a semantic tree of object-level and property-level changes.This view makes it easier to inspect what changed in Unity terms: GameObjects, components, hierarchy updates, serialized properties, and references. It is useful for branch comparison, working tree review, and pull request review.Version CompareMergeSight compares different versions of Unity assets across branches, commits, and working tree states.This makes it easier to inspect changes before they become merge problems, and to review asset history in the same Unity-oriented model used by the rest of the tool.Filter Assets and ChangesMergeSight lets you narrow large reviews down to the files and change types that matter.You can filter changed assets by type, path, name, and Git/VCS status, then filter the semantic diff tree by search query, change kind, and item type such as objects, components, or properties. This is useful when a single revision touches many assets and only a few of them need close inspection.3-Way Merge WorkflowMergeSight provides a structured BASE / OURS / THEIRS merge view for conflicted Unity assets.Each conflict stays visible in context, and the user chooses the correct side or applies a safe merge action where appropriate. The merge flow is designed for Unity data structures that involve object ownership, hierarchy changes, component attachments, local references, and serialized fields.Conflict Preview and Safe ApplyMergeSight shows the composed result before writing the final asset.Apply is blocked while unresolved decisions remain. The tool creates a backup before writing results and fails closed on ambiguous or unsupported structures. That keeps the merge path predictable during interactive review.Unity-Aware StructureMergeSight understands Unity asset structure directly.Supported structure includes:GameObject and component ownershipparent/child hierarchy relationshipsscene root orderinglocal references and object IDsmaterial saved-property pathsScriptableObject and generic .asset contentThis keeps review and merge decisions aligned with Unity’s data model, which makes the output easier to trust than a line-based text diff.References, GUIDs, and Unity SerializationMergeSight also handles the Unity-specific reference model that appears throughout serialized assets.This includes:GUID-based asset referenceslocal fileID references inside a fileobject fields that point to external assetsobject fields that point to sub-assets or scene objectsserialized Unity structures that depend on stable ownership and reference resolutionThis part matters when a diff looks small in text but changes how Unity resolves an asset graph. Seeing references and object relationships in context makes review and merge decisions much easier to trust.Supported VCSGit, Perforce, Unity Version Control / Plastic SCM, and SVN.Supported Asset TypesPrimary support:.unity.prefab.asset.matSupported Unity VersionsUnity 2022 LTSUnity 2023 LTSUnity 6Editor-only note: Editor and automation tool, not a runtime package.Requirement: Unity assets must use text serialization.Third-party dependency:YamlDotNet is bundled as a YAML parser dependency under the MIT License.AI Tool UsedOpenAI Codex was used as an AI-assisted software development tool during the creation of this package.Implementation AssistanceCodex assisted with portions of the C# implementation, particularly the Unity YAML parsing and semantic processing layers. It also helped investigate parsing failures, identify edge cases, and develop regression fixes.Automated TestingAI assistance was used substantially to plan and author an internal suite containing more than 700 automated NUnit test cases. These tests cover YAML parsing and serialization, semantic diffing, three-way merge and conflict resolution, validation, VCS integration, and end-to-end Unity asset scenarios.Codex helped generate test inputs, identify edge cases, define expected results, analyze failures, and expand regression coverage.Human Review and Final DecisionsAll AI-assisted output was manually reviewed, edited, integrated, and verified by the publisher. The publisher defined the required behavior, selected the final architecture and merge rules, reviewed test expectations, and made all final implementation and release decisions.AI Functionality in the PackageMergeSight does not include generative AI functionality and does not send customer or project data to an AI service.