Flight Freedom

Flight Freedom

No flying ceiling, no no-fly zones, no town dismount, a mount you can summon in the Abyss, and a Blackstar that stays where you leave him. Crimson Desert 2. 03. 01.

Blackstar and the Wyvern stop climbing at 1350, and somewhere around 1550 the game takes the mount away from you. Both numbers come from the game's own data. With this installed the ceiling is gone from both flying mounts and nothing dismounts you for being too high. The same rule that dismounts you is what answers "Cannot summon in this area." on the floor of the Abyss, so that goes as well.

What it changes

• []The ceiling. Every mount has a maximum height in the game's vehicleinfo table: 1350 on Blackstar and the Wyvern, none at all on the other 32. The plugin finds the table by name at startup, writes your setting over those two rows and reads it back into the log so you can see it took.

  []No-fly zones. Each region carries a list of mount categories it turns away. One routine answers whether the region you are standing in, or any region that contains it, lists the mount you are on. That single answer is what pulls you off a flyer high up and what refuses a ride into a listed region. Three bytes make it answer "not blocked" everywhere.

  []Summoning in the Abyss. The summon check asks that same routine, and its refusal is the "Cannot summon in this area." message. A second patch, one byte, makes it skip that refusal, so you can still call a mount underground even if you decide to keep the zones.

  []Flying over towns. A separate rule takes the mount off you for flying low across a town away from a road, with "Cannot ride the mount in town." The condition is "in town and not above a road within 20", which is why riding through on the road never triggered it. Three bytes make the road half always answer yes, so the rule can never be true. That check is used by one condition row in the whole game; the in-town test is left alone, because 23 rows use it for bounty escalation and trade pricing.

  []Blackstar staying put. About 30 seconds after Blackstar lands, his AI starts a takeoff action and he flies away. Every action an AI starts goes through one function in the game, and the plugin turns down that one action by its id and lets everything else through. You can still ride him, and summoning him from more than 30 m away works as before. 1. 1. 5 tried this by changing his spawn duration, which turned out to do nothing; this build is the one that works.

• []Ceiling (-1) Height cap for the flying mounts. -1 removes it, 0 leaves the game's 1350, a number sets your own.

  []NoFlyZones (1) 1 means no region blocks any mount. Set it to 0 and altitude dismounts come back.

  []AbyssSummon (1) 1 means the summon check never refuses you for the region you are in. It does nothing extra while NoFlyZones is on, and is separate so you can keep the dismount zones and still summon underground.

  []PlatformSummon (0) 1 means the summon check never refuses you for whatever you are standing on. That check is what stops a summon while you stand on an Abyss Nexus teleport circle. Off by default: it is read out of the disassembly and one report, and it also lets you summon on top of a moving platform anywhere in the game.

  []TownFlight (1) 1 means flying low over a town off the road never dismounts you. Set it to 0 for the game's own behaviour.

  []BlackstarStays (1) Blackstar stays where you get off him instead of flying away about 30 seconds later. Set it to 0 for the game's own behaviour. An old number left here from 1. 1. 5 is read as 1, and LandedTimeout is ignored.

  []Probe (0) The research mode this was built with. It hooks every mount-related check in the game, reads three further ini sections that can hook, patch or watch any address, and writes a very large log. Leave it off unless you are digging into something.

  Installation

  With Definitive Mod Manager (DMM)

  • []Download the DMM file and drag it onto the DMM window.

    []Enable it and Mount. DMM registers FlightFreedom.asi and brings its own loader.

  The DMM archive holds the plugin alone, since that is what DMM installs. Defaults are compiled in, so it is complete on its own. From 1. 1. 3 the plugin writes FlightFreedom.ini beside itself the first time it finds none there, so start the game once and the fil