K.O.R.E. custom fighters and MUGEN import compatibility
K.O.R.E.’s inspected custom fighter workflow imports sprite sheets and authors animation slots through development tooling. It does not establish general public-browser support for MUGEN character ZIPs or CNS/CMD logic.
What the character importer actually does
The inspected Character Import screen starts from a sprite sheet, detects frame regions and assigns frames to animation slots. The draft includes a character identity and gameplay values before building a K.O.R.E. character definition. That is a native authoring workflow, not a transparent execution layer for another engine's character logic.
Saving the imported character posts to /__kore/dev/import-character. This is a development endpoint. Its presence in source must not be advertised as a production upload service available to every visitor at playkore.com.
A character contains several independent layers
| Layer | What needs deliberate authoring or verification |
|---|---|
| Source images | Frame bounds, transparency and facing direction |
| Animation slots | Coherent ordered sequences for each state/move |
| Gameplay definition | Inputs, timing, hit behavior and other move data |
| Rendered representation | Scale, alignment and appearance in the game |
| Supporting assets | Effects, projectiles and audio where applicable |
A successful image extraction only verifies the first portion. A fighter can have clean frames and still need substantial animation or gameplay work.
What is not established
This review did not find or verify a general public character-pack importer that reproduces arbitrary MUGEN CNS/CMD behavior. A MUGEN-style roster concept, a project folder name and a stage parser are not substitutes for that compatibility layer.
Likewise, a converted visual asset does not establish that a creator's complete character behaves identically. If preserving an existing external project is your primary requirement, inspect the receiving engine's explicit compatibility documentation and test a small example.
A useful first authoring exercise
Keep an untouched copy of your source material. Prepare one short, clearly separated sequence and check that every frame contains the intended fighter rather than adjacent cells or stray effects. Assign the correct state, inspect facing and size, then test one move before expanding the sheet.
After that, inspect rest, movement, attack, reaction and recovery states. A single attractive idle frame is not full-fighter verification. This is original practical guidance based on the inspected pipeline; it is not a claim that a new character was imported during this SEO review.
Stages are a separate path
K.O.R.E. also has MUGEN stage conversion tooling, described in the stage guide. Its selected DEF/background handling does not imply character-logic compatibility. Keep the two workflows separate when planning a project, and use the comparison guide to choose an engine by your actual requirements.
Sources & verification
View the research record
Coverage: Named source passages inspected; practical routines are original advice. Production entry and selected source comparisons are recorded separately. No whole-roster, full-campaign, physical-device or universal network certification.
First-party facts: Named runtime/source passages and the selected live entry checks recorded here. Original additions: Explanations, comparison framing and practice routines. Gaps: No full-campaign, whole-roster, universal device or network certification. Development tooling is distinct from public capabilities.
Source review: October 20, 2026. Public claims remain bounded by the scope of each source.
- kore app
Inspected menu, mode and importer source. Character import and MUGEN stage import POST to /__kore/dev/ endpoints. Source inspection is not a complete production compatibility test.
Inspected named local source passages and public response; bounded coverage below.
Inspected source fingerprint:
c91886ba1e3ebc951e3c3ef50356cfe64fb2718164bdccf7ea59d636960160ae. Public response fingerprint:38cc2f2a18a415a64a9cea8d0af2880043ff8c826d00f37d973b5f28e0f80d9d. Local source and public response differ or are different representations; no complete build equivalence is claimed.- kore mugen
DEF/background parsing and sprite-to-stage conversion, distinct from character CNS/CMD emulation.
Inspected named local source passages and public response; bounded coverage below.
Inspected source fingerprint:
8fc75a8372213139824755479575a59d4ffb2fe1f9154abfb966d90d8e760660. Public response fingerprint:38cc2f2a18a415a64a9cea8d0af2880043ff8c826d00f37d973b5f28e0f80d9d. Local source and public response differ or are different representations; no complete build equivalence is claimed.
Article fingerprint: 32f2e04b2f304041a49068b87ac31bfd96093f446acd634af0234b7d57c06d4b.