[NEW] Shaiya Studio Editor

[[ADM]Beno™]

Shaiya Editor Studio 2026 – A Professional Editing Suite for Shaiya

Shaiya Editor Studio is a complete editing environment built with .NET 8, WebView2, React, TypeScript, Vite, and OpenTK, designed specifically for working with Shaiya's client and server data.

The project brings many previously separate Shaiya development utilities into a single professional workspace, with a strong focus on data integrity, validation, accurate serialization, and safe file editing.

Instead of treating Shaiya files as simple binary containers, the Studio understands their internal structures and provides dedicated editors, viewers, resource resolution, and database tooling where applicable.

Screenshots & Core Features

1. Workspace Browser – Full Client Support



The Studio can work directly against a complete Shaiya client workspace and resolve the resources referenced by the files being edited.

Rather than simply displaying a folder tree, the workspace is designed to understand relationships between data files and their associated assets, including models, textures, animations, and other client resources. This makes it possible to work with the actual client structure instead of manually locating every dependency.

2. Codepage Selection

Shaiya clients can use different text encodings depending on the client and server environment. The Studio treats codepage selection as an explicit workspace configuration instead of making unsafe assumptions.

Common environments may involve encodings such as CP1258, CP949, GBK, Big5, Shift-JIS, and others. The selected configuration can be retained for the workspace and reused during future sessions.

3. Item Editor – Large-Scale SData Editing



The Item Editor is a schema-driven editor designed for large Shaiya item databases. Current supported Item SData variants include:

• []EP5
  []EP6
• EP6.2

The editor provides structured record editing, filtering, categorization, and visual asset resolution. For large datasets, the interface uses a virtualized grid so thousands of records can be browsed efficiently. The Studio can also resolve and display the real item icons referenced by the client rather than relying on generic placeholders.

4. Item Inspector & 3D Preview



The Item Inspector provides a visual way to inspect equipment and associated client assets. Items can be displayed using the Studio's 3D rendering pipeline, with support for the relevant character and equipment presentation. The current preview workflow includes:

• []Human / Elf
  []Male / Female
  []Equipment visualization
  []Model rotation
  []Wireframe rendering
  []Alpha visualization
• Fullscreen preview

This makes visual verification part of the editing workflow instead of requiring repeated testing inside the game client.

5. Skill Editor – Multiple SData Variants



The Skill Editor provides dedicated schema-driven editing for supported skill formats. Current supported variants include:

• []EP5 x 3
  []EP5 x 9
• EP6 x 15

Skills are organized into their corresponding groups and can be browsed using structured data, icons, types, descriptions, and filtering.

6. Monster Editor



The Studio provides structured editing and inspection for Shaiya monster data. Depending on the format, available fields can include:

MobID, Level, Model, AI, Element, HP, Size, Quest ID

The interface is designed to make large monster datasets easier to search, inspect, and modify without manually editing raw binary structures. Where a value is client-side or format-specific, the Studio distinguishes that context rather than presenting every field as if it had the same purpose.

7. NpcQuest, Cash & NpcSkill

The Studio also supports additional Shaiya data formats, including:

• []NpcQuest
  []Cash
  []Monster
  []NpcSkill

These formats are handled through the Studio's internal document and schema system, allowing them to be opened and edited through the same unified workspace — making it possible to support additional formats without requiring an entirely separate application for each one.

Additional File Tools

ITM / MLT / MLX
Dedicated editors for item definitions, multiple-effect data, and MLX lists and related item resources.

3DO / 3DC
3D model viewers for supported Shaiya model formats. The Studio uses OpenTK as part of its rendering pipeline for supported 3D resources.

DDS / TGA
Texture viewing for common Shaiya client texture assets.

ANI / ALT
Animation viewing and inspection for supported animation resources.

Together, these tools allow developers to move between structured data and the actual assets referenced by those records without constantly switching between unrelated applications.

Extended Format Support

One of the Studio's main objectives is to support a broad range of Shaiya file formats through a unified document system. Supported formats currently include:

• [].mon
  [].wld
  [].svmap
  [].mani
  []NpcQuest
  []Cash
  []Monster
  []NpcSkill
• and additional supported Shaiya documents

The goal is to provide a consistent workflow across different file types while preserving the actual structure and information contained within each format.

Data Integrity & Safe Saving

One of the core design principles of Shaiya Editor Studio is: never silently destroy the user's original data.

Every save operation passes through a controlled transactional workflow:

Serialization
↓
Read-back Verification
↓
.bak Backup
↓
Temporary File Write
↓
Atomic Replacement

If verification fails, the save operation is cancelled and the original file remains untouched.

For complex document formats, the Studio also performs a document-fidelity check: the in-memory document is compared against the data produced by serialization and read back from disk. If the system detects that information could be lost or unexpectedly changed, the save is blocked and the differences can be reported. This matters most with complex formats, where a technically valid write could otherwise result in incomplete data.

Every successful save also preserves a .bak backup of the previous version.

SQL Integration

Shaiya Editor Studio also provides tooling for integration with SQL Server / PS_GameDefs. SQL script generation is currently available for supported datasets including:

• []Item
  []Skill
  []NpcSkill
  []Cash
• Monster

The Studio generates SQL scripts from the relevant Shaiya data instead of requiring developers to manually construct large SQL statements. It can also be used as part of a workflow for moving supported database data back into the corresponding Shaiya file structures — reducing the gap between editing client-side data and applying the matching changes to the server environment.

Modern WebView2 Studio

The current Studio interface is built around a modern React + TypeScript + Vite application hosted inside WebView2. It provides the foundation for a modern editing experience while keeping the underlying Shaiya parsing, validation, and serialization logic inside the native application. Current UI architecture includes:

• []Multi-document tabs
  []Open document management
  []Dirty-state indicators
  []Tab switching
  []Native file and folder dialogs
  []Undo / Redo integration
  []Save integration
  []Internal Studio API layer
  []Item / Skill / Cash / Monster / NPC document APIs
  []Workspace-level configuration

The architecture separates the UI from the core editing engine so the underlying Shaiya data logic can continue to evolve independently from the interface.

Core Architecture

The Studio is built around several independent layers:

• []ShaiyaEditor.Core — Format logic, SData schemas, document engines, asset decoding, resource resolution and validation
  []ShaiyaEditor.App — Native application shell, WebView2 host and Studio UI
  []ShaiyaEditor.Tests — Round-trip, byte-identity and diagnostic testing
  []Asset Pipeline — Model, texture and animation decoding / preview
• License Tools — License and device identification support

This separation matters because the UI is not responsible for the actual file-format logic. The core remains UI-independent, so validation and serialization can be tested independently from the frontend.

Current Development Status – Private Testing

Shaiya Editor Studio is still actively under development and should not be considered a finished or fully stable release. Although a significant amount of functionality is already implemented, it has not yet undergone enough extensive real-world testing across different Shaiya clients, episodes, configurations, and modified environments.

For this reason, I'm currently looking for a small group of serious testers willing to work with the software carefully and provide detailed feedback.

Testing is currently limited. The test build is not intended for unrestricted public distribution. Because the project is still undergoing development and validation, testers are expected to keep the provided builds private and not redistribute, upload, mirror, or share them publicly.

This isn't meant to make the project unnecessarily restrictive — it's simply necessary at this stage so that unfinished builds don't spread across the internet before they've been properly tested and reviewed.

Collaboration & Mutual Understanding

Testing this project should be treated as a form of collaboration, not simply early access to a finished product. I'm looking for testers who understand that:

• []The software is still evolving.
  []Bugs and unexpected behavior may still exist.
  []Some features may change or be redesigned.
  []Test builds may be replaced frequently.
  []Reports of crashes, corrupted output, incorrect parsing, UI issues, and unexpected behavior are extremely valuable.
  []Shared builds should remain within the agreed testing group.

In return, testers will have the opportunity to use the Studio during its development phase and help shape the direction of the project through real-world feedback. A good level of cooperation, communication, and mutual respect is expected from everyone involved.

The goal is to build the Studio together with people who actually work with Shaiya data and can help identify problems that internal testing alone can't uncover.

What the Studio Is Designed For

Shaiya Editor Studio is built for developers, server owners, modders, and technical users who work directly with Shaiya's client and server files. The objective is a unified environment where you can:

Open → Inspect → Edit → Preview → Validate → Save

without constantly switching between unrelated tools. Instead of focusing on a single file type, the Studio is being developed as a broader Shaiya development workspace capable of handling structured data, binary formats, client assets, previews, and SQL workflows together.

Requirements

Supported operating systems:

• []Windows 10
  []Windows 11

Runtime:

• WebView2 Evergreen Runtime

The application is distributed as a self-contained build, so a separate .NET installation is not required.

Final Thoughts

Shaiya Editor Studio is being developed around one central idea: make Shaiya file editing safer, faster, and more professional.

Rather than maintaining a collection of isolated utilities, the Studio brings structured editors, binary-format support, resource resolution, 3D asset inspection, animation viewing, SQL tooling, and validation into one environment. The emphasis isn't simply on being able to change a value — it's on being able to understand what you're changing, verify the result, and save it without unnecessarily putting the original client at risk.

At this stage, the most important part of the project isn't adding more features — it's testing, refining, and making sure existing functionality is reliable across real Shaiya environments.

If you're interested in joining the testing group, please understand this is an early development/testing phase, and cooperation regarding private builds and responsible usage is essential.

Feedback, suggestions, technical discussion, and detailed bug reports are welcome.

Shaiya Editor Studio 2026 – Built with .NET 8, WebView2, React, TypeScript, Vite & OpenTK.

Additional screenshots: