Hytale Movement & Combat-Feel Server Guide: Update 6 MovementSettings, DisableAutoStep & Projectile Config

Combat is what people remember about Hytale. The reveal trailers sold a world where you dodge a sabertooth lunge, parry, reposition, and answer — movement and combat woven into one feel. That promise is exactly what the screenshot at the top of this guide captures: an adventurer mid-fight against a sabertooth in the open wild. For years, server owners who wanted to tune that feel — faster scouts, heavier tanks, build-defining gear — had to lean entirely on community mods. Update 6 changes that. It quietly shipped a set of data-asset hooks that give server owners real, JSON-driven control over movement and combat feel, no heavy Java required. This is not a patch-notes recap — we already covered those in our Update 6 Part 3 patch notes and Part 2 patch notes. This is an evergreen configuration guide: what each new hytale server customization hook is, how to set it up, and what it unlocks for your server. We will cover hytale armor movement settings, the hytale DisableAutoStep block property, hytale projectile config, and how all of it lines up with the community demand behind the most popular hytale movement mods and hytale combat mods. One important caveat up front: these features arrived on the Update 6 pre-release (testing) branch, which ships weekly on Thursdays. It is not the stable build, and no Update 6 stable date has been announced. Everything below is best tested on a staging server before you take it live. Movement-Modifying Armor (MovementSettings) The headline feature for hytale custom movement is that armor can now modify how a player moves through a new MovementSettings data block. According to the official Update 6 notes, this lets gear adjust properties such as walk and sprint speed and jump height. Because it is data-asset driven, you define it in your armor's JSON rather than writing engine code. Conceptually, you attach a MovementSettings block to an armor piece and set the movement properties it should grant while equipped. The exact field names and value ranges are still settling on the pre-release branch, so treat the examples below as the shape of the configuration rather than a guaranteed schema, and confirm against the current build: Speed gear. A pair of "Scout Boots" that bump walk and sprint speed for explorers, couriers, or a parkour class. Heavy armor trade-offs. Plate that boosts defense but reduces movement speed — the classic tank fantasy, now expressible without a plugin. Jump gear. Boots that raise jump height for vertical traversal, hidden-loot access, or movement-skill challenges. For RPG and adventure servers, this is the piece that has been missing. Movement-stat gear makes builds feel different: a glass-cannon assassin that flickers around the arena versus a juggernaut that hits like a truck but lumbers. Pair these armor pieces with tiered loot tables and you get progression that players can feel in their hands, not just read on a stat sheet. If you are tuning weapon and combat balance alongside gear, our PvP weapon tier list and combat guide is a useful companion. Precision Blocks: DisableAutoStep By default, players auto-step up single-block ledges — you walk into a one-block rise and the engine lifts you over it. That is convenient for general traversal and terrible for precision. Update 6 adds a block property, DisableAutoStep: true, that turns auto-stepping off for a specific block. When set, players cannot simply stroll up onto that block; they have to deliberately jump. It is a small flag with outsized design value. A few ways hytale DisableAutoStep changes what you can build: Parkour that stays honest. Auto-step quietly trivializes parkour by letting players walk up gaps they were supposed to jump. Disabling it on your course blocks forces the intended jumps and restores difficulty. Traps and pressure design. A block players cannot casually mount becomes a ledge, a pit lip, or a chokepoint — useful for dungeon and trap design where you want movement to have consequences. Precision builds. Decorative or technical builds where you do not want players accidentally clambering onto surfaces — display platforms, fragile-looking architecture, intended walkways. Because it is a per-block property, you can mix stepped and non-stepped blocks in the same area, which is exactly what good parkour and trap layouts need. Set it in the block's data definition and test the feel in-game — auto-step is one of those mechanics players only notice when it is missing. Projectile Control: IgnorePitch, IgnoreYaw & RotationOffset Combat feel is not only melee. Update 6 gives projectiles finer aiming control through three new levers in your hytale projectile config: IgnorePitch — the projectile ignores vertical aim (pitch). IgnoreYaw — the projectile ignores horizontal aim (yaw). RotationOffset — applies a fixed rotation offset to the projectile's orientation. Together these let you decouple a projectile's direction from where the shooter happens to be looking, which opens up mechanics that used to require custom code: Fixed-direction turrets. Set a turret to fire along a locked axis regardless of facing — ignore yaw or pitch so the bolt always travels the intended line. Trap projectiles. Dart traps, arrow walls, and dungeon hazards that always fire in a set direction, independent of any entity's view angle. Fixed-orientation spells. Spell or ability projectiles that need to launch at a consistent angle — using RotationOffset to tilt the launch — for telegraphed, readable attacks players can learn and dodge. The throughline with the melee changes is the same: predictable, authorable combat. When a projectile's path is deterministic, players can read and react to it, which is the foundation of combat that feels skillful rather than random. A Related Lever: Crop Obstruction Tolerance Worth a brief mention for completeness, since it is part of the same data-asset tuning wave: PrefabFarmingStageData gained TolerateObstructionsBelowY and TolerateObstructionsAboveY fields, which let custom crops keep growing even when partly obstructed. It is not a movement or combat feature, but if you are already in your data assets configuring gear and blocks, it is a handy knob for custom-crop content that otherwise stalls in tight or built-up spaces. What This Means for Combat-Feel Servers Here is the context that makes these hooks matter: the community has been building movement and combat customization on its own for a while, and the demand is loud. On CurseForge, Zephyr — which adds glide, wall-jump, dash, grapple, and zipline movement — is one of the most popular movement mods around, and we covered the surge of interest in it in our Zephyr movement weekend feature. On the combat side, Perfect Parries brings a dedicated parry system that sharpens melee feel. These mods have pulled serious download numbers because players want movement and combat that feel tuned, not generic. The new official hooks do not replace those mods — Zephyr's grapples and ziplines go well beyond what armor MovementSettings covers — but they do something important: they let server owners express a meaningful slice of that customization through plain data assets, no plugin dependency required. Movement-stat gear, precision blocks, and directional projectiles are now first-class, server-side, and JSON-driven. That lowers the barrier for the average server owner who wants their combat to feel distinctive but does not want to maintain a Java plugin. And where you do want more — full traversal kits, parry systems — the modding ecosystem is right there to layer on top. A Note for Modders: The Teleport JOML Change If your server runs custom Java plugins, one small but breaking detail rides along with this update: the Teleport constructor now uses JOML interface types (Vector3dc and Vector3ic) instead of its previous signature. If any of your code constructs Teleport directly — common in movement, ability, or warp logic — you will need to update those call sites to pass the JOML types. It is a quick fix, but it will fail to compile until you do. For the broader plugin lifecycle and the rest of the hytale update 6 modding migration, our modding API and server plugin development guide is the place to start. Test Before You Go Live Because all of this is on the pre-release testing branch, the workflow matters. Stand up a staging server on the pre-release build, configure your MovementSettings gear, DisableAutoStep blocks, and projectile settings there, and actually play the result before touching production. Field names and behavior can shift week to week on a testing branch, so treat the schemas in this guide as the general shape and confirm specifics against the build you are running. Movement and combat are feel-driven — the only real validation is getting in-game and moving around. Get Your Server Ready Update 6's movement and combat-feel hooks are the kind of feature that rewards the server owners who experiment early. Movement-stat armor, precision parkour blocks, and directional projectiles let you build a combat identity that players notice the moment they log in — and a distinctive feel is exactly what turns a one-time visit into a regular. As you tune these systems, keep your HytaleCharts server listing sharp: a current banner, a clear description that calls out what makes your combat feel different, live player counts, and an up-to-date tag set. The players hunting for somewhere fresh to play the new build are browsing the listings right now — make sure yours tells them why your server is the one worth landing on.