msw-defaultplayer

msw-defaultplayer manages the MapleStory Worlds DefaultPlayer character model. It uses the sibling msw-general ModelBuilder to inspect and patch the DefaultPlayer model files, add or remove components, and configure movement speed, jump force, HP, camera, and per-map-mode movement components. Costume and avatar equipment are handled by the separate msw-avatar skill, since costumes apply not only to DefaultPlayer but to any entity. The DefaultPlayer is the player character model provided by default in the Maker workspace; a player entity is created from it whenever a user enters a world, and the model ID used is set by the PlayerUri property of DefaultUserEnterLeaveLogic.

The model is composed of two .model files. Player.model at ./Global/Player.model is the base model that defines the full Components list and the Properties links, with empty Values because defaults come from the engine. DefaultPlayer.model at ./Global/DefaultPlayer.model inherits Player via BaseModelId "player", lists only the components added on top (such as script.PlayerHit and script.PlayerAttack), and holds the array of overridden Values. Both files live in ./Global/, while custom script files are created under ./RootDesk/MyDesk/. All editing is done through msw-general/scripts/model/msw_model_builder.cjs rather than raw JSON: property values are changed with ModelBuilder.read(...).value(...), components are added or removed with component() and removeComponent(), and the base component list is checked with ModelBuilder.snapshot("./Global/Player.model").

The skill enumerates the player's default native components and their roles, including TransformComponent, MovementComponent, RigidbodyComponent, KinematicbodyComponent, SideviewbodyComponent, StateComponent, AvatarRendererComponent, PlayerControllerComponent, PlayerComponent, CameraComponent, and others, plus the script components added in DefaultPlayer.model. A quick-reference table lists key properties and methods per component, such as PlayerComponent's Hp, MaxHp, RespawnDuration, IsDead(), ProcessDead(), and ProcessRevive(), and MovementComponent's InputSpeed and JumpForce. It also documents the Values entry format (TargetType, Name, ValueType, Value) and TargetType rules, where null maps to a model property defined in Player.model's Properties, MOD.Core.<ComponentName> overrides a native component property directly, and script.<ScriptName> targets a custom script property. A mapping table connects model property names like speed, jumpForce, gravity, and the camera dead/soft zones to their source component properties and defaults.