Daggerfall Unity 0.13 Rendering Update

There are some long-standing items on Daggerfall Unity’s Roadmap that have at last found their way into the game. These changes relate to visual rendering of classic textures in Unity engine and how they interact with lighting. There’s also a long-overdue update to the postprocessing stack. To summarise everything before getting into details, these changes are:

  • New default shaders for classic textures
  • Switch rendering from Gamma to Linear colour space
  • Lighting review
  • Update postprocessing stack

New Default Shaders

You might have noticed the visuals in DFU have a kind of silvery “shine” on top, and some textures tend to wash out easily under certain lighting conditions. Examples are objects that emit light, such as lanterns, and naturally bright textures like snowy terrain at midday. Even when using retro rendering with palletization, deep blacks will tend to shift value towards lighter greys.

The reason for this is somewhat technical. A concise version is that modern engines like Unity use something called Physically Based Rendering (PBR) which attempts to simulate the physical properties of a material and how it interacts with light. However, old games like Daggerfall predate physical material properties such as normal maps, smoothness maps, etc. and instead have only basic colour information in a single texture. When attempting to render these simple textures in a PBR engine without any other material properties, they are perfectly smooth and will reflect light in unsatisfying ways. This can give objects a shiny kind of look, as if made from plastic or dull metal.

In fixing this, the goal was to correct lighting incongruity while using classic textures and still allow mods like DREAM to use PBR materials. It was also necessary for these different materials to work together in the same scene with any combination of classic and modded materials. This presented some challenges that were eventually overcome with the help of new shaders and several updates to material pipeline.

The best way to see the difference is to compare a scene in 0.12 and 0.13. Pay close attention to the dark areas of the rat while adjusting slider. You’ll notice in 0.12 screenshot the rat has a uniform specular shine that is removed in 0.13. You’ll see the same across the entire scene, although most obvious in darker textures.

Before Image After Image

To fix this specular shine required new shaders better suited to Daggerfall’s classic textures. These new shaders lean fully into the retro textures and use simple Lambertian reflectance like older games of the time. This leads to better colour sampling under most lighting conditions and fixes brighter areas from becoming overbright. For example, the lantern and Fire Daedra wash out to bright yellows in 0.12 using PBR shaders but show their true colours in 0.13.

Before Image After Image
Before Image After Image

While relatively basic, the new shaders still support Normal maps and Emission maps, and conditional compilation. They are more lightweight than Unity’s Standard shader and will perform slightly better on lower-end computers running without mods.

Gamma to Linear Colour Space

The next change was switching from Gamma to Linear colour space. This is another technical subject, but in short it relates to how colours are added and multiplied. Linear colour space leads to more accurate results with improved lighting falloff and softer shadows. The results can be subtle in unmodded DFU, but the combination of new materials and linear lighting uplifts every scene with deeper colours and improved contrast while eliminating bloom and flat specular shine.

Before Image After Image
Before Image After Image
Before Image After Image

With the change to Linear colour space, modded materials now have a chance to look their best at all times with more accurate colours and no unwanted bright spots near lights. Of course, all these changes also require lighting to be reviewed and materials tweaked so they still look good. This leads into the next item on the list.

Lighting Review

Linear colour space blends and lights differently than Gamma. Lights appear to have a larger radius and is more defined on edges. This is more accurate overall, but also different if you’ve become accustomed to Gamma lighting. As a result, all the light sources in the game need to be tuned so they aren’t too bright and still resemble the game as it was.

In general, dungeons will appear a bit darker from 0.13. The combination of new shaders, Linear colour space, and lighting review result in darker colours becoming more prominent. You can really see the flat silvery shine over everything in below screenshot when comparing 0.12 to 0.13. The dark parts of brick textures stay dark rather than shifting value towards lighter greys.

Before Image After Image

Towns are still nicely lit oases, with Linear’s different light falloff visible against sides of buildings in below screenshot. But the removal of flat specular shine means night-time scenes have better overall contrast between light and dark areas.

Before Image After Image

Daytime scenes will light much the same as there’s only a single directional light source (the sun). The change to Linear with new shaders also resolves the problem of terrain textures looking over-bright under a midday sun. Finally, the daytime light curve was adjusted to provide a longer plateau of sunlight around 10am-3pm.

Before Image After Image

Update Postprocessing Stack

For some years now, Daggerfall Unity has continued to use an older embedded postprocessing stack. This has now been removed and replaced with current Post Processing 3.1.1 via Unity’s package manager. This updates deferred fog and postprocess capabilities to be in line with current engine. It also required some minor code changes and retuning fog as some parts of the old Post Processing library have been deprecated.

Fog is roughly the same, other than being a bit thicker towards limits of view distance. Compare the distant trees and buildings in below winter scene.

Before Image After Image

Preview Release and Mods

Daggerfall Unity 0.13 will be available as a Preview release soon. Due to all the changes across asset pipeline, colour space, default materials, and postprocess stack, you should expect some mods that work under 0.12 not to work in 0.13. Mods that include new materials and shaders will be most affected. Any non-graphical mods, or those which only change game settings, should be unaffected or only need minor tuning.

It could take several weeks for mod authors to update their mods to be compatible. If you don’t want to help test 0.13 and provide feedback to developers and modders, you can happily stay on 0.12 until 0.13 release is out of preview. You can also run 0.12 and 0.13 side-by-side by unzipping releases to different folders and running different mod loadouts. Other than changes outlined above, the 0.13 release is identical in terms of gameplay and patch level to 0.12.

Looking to the future, this represents the last major change to Daggerfall Unity leading up to 1.0. Bug fix and general refinement will resume once 0.13 is considered stable.

Thank you for reading! I hope you decide to try out Daggerfall Unity 0.13 preview to help test mods and provide feedback.

Retiring Live Builds Page

Future Releases

For the last few versions, patch notes and downloads have been mirrored to our GitHub Releases page. Starting from upcoming July builds, our Releases page will be the official site to find new builds of Daggerfall Unity. Live Builds will be retired and redirect to Releases.

This comes with a few advantages. Patch notes, source, and downloads for each release now all live together in one place, and a longer release history can be maintained. Whereas Live Builds would only keep last two or three builds, Releases can retain all new versions going forwards. It also means new releases can be curated by other developers as future stewardship of Daggerfall Unity broadens beyond myself.

This is part of a strategy to make GitHub the primary Daggerfall Unity site in time for 1.0 release. As a project that has now been worked on by over 50 people across 5+ years, it doesn’t make sense for a personal blog site to be the centre of such an endeavour. I’ll have more to share about this as 1.0 approaches later in 2021.

Development History

Daggerfall Workshop started as a personal blog site outlining my journey creating exploring tools for Daggerfall. Since Daggerfall Unity reached classic parity in 2019, most of the posts here have been patch notes in bullet format. But if you look back over posts from a few years ago, there were more interesting and technical updates as the energy of development was in full swing.

My sentiment is the basic patch notes are starting to bury more interesting posts from DFU’s long development history. Rather than continue this trend, I’d like Daggerfall Workshop to stand as a journal of one person’s mad obsession gradually leading into a rather astounding fan remake that has since outgrown the person who started it.

Back to Its Roots

I’ll still post major news and events here on the Workshop, and I might even use it as a personal devblog again someday. There’s a future coming for Daggerfall Unity that doesn’t need me to manage every release and review every line of code. In that future, I’m just one more person who loves this game. I might at last have some time just to play for fun and build mods of my own on the side.

And someday after 1.0, once I’ve had time to decompress and organise my thoughts, I’d love write a detailed postmortem of Daggerfall Unity’s development. This would be a fitting capstone to the Workshop after more than 20 years of tinkering on this unique game.

Daggerfall Unity Beta 0.11.4

Daggerfall Unity Beta 0.11.4 is now available for download on Live Builds and Releases page. This is a heavy bug-fix build with some new mod support.

As always, a big thank you to everyone adding new code, fixing bugs, and helping test. You all help make each release the best it can be.

General Fixes & Improvements

KABoissonneault

  • Added the ability for mods to specify an item type as “noRepairs”
  • Modding the character sheet’s Skills dialog UI mod system
  • Fix: Show biography skill bonuses during character creation
  • Added two event handlers for loot spawning
  • Added “weather”, “season”, and “climate” quest trigger conditions
  • Added new time-related text macros
  • Expose the SpellMaker and its subwindows to mods UI
  • Added “resistance” formula overrides.

Ferital

  • Cache RMB blocks
  • Add %mn and %fn macros support to TalkManagerMCP
  • Change NPC knowledge in Talk Manager to match classic
  • Fix automap update not triggering on some occasions
  • Add a runtime method to fix invalid RDB blocks
  • Use classic hack to fix Orsinium overlapping blocks

Pango

  • Resynchronize vital indicators after toggling large HUD bug
  • Quest and enchanted items exclusions wip
  • Fix Castle Wayrest backroom door messages not showing up (issue #1974)
  • Stack identical books together (enhancement)
  • Immediately interrupt resting if you die
  • Prevent levitating and swimming diagonally from being 40% faster bug
  • Don’t reset lastSpell when using magic missile items bug
  • Use monotonic screenshot filenames
  • Preserve rumors line breaks on bulletin boards

Jefetienne

  • Add Large HUD offset logic to FPSSpellCasting like in FPSWeapon

l3lessed

  • SpeedChanger Updates

Hazelnut

  • Allow water tile conversion to be handled by terrain texture mods
  • fix warning on trade window
  • Add new promptmulti action for 2-4 button message boxes in quests
  • Add OnItemHover to inventory window for mods
  • Open up spell book for mods
  • Fix typo in DFU macro %pg1 bug
  • Reset ship ownership on new game start bug
  • Enable player torch shadows based on spell shadows setting
  • Re-fix riding sprint in mods bug
  • Refactor guild service window UI mod system
  • Add formula for bank loans

XJDHDR

  • Fixed ArgumentOutOfRangeException on loading game with new dungeon models
  • Extra features for the CustomDoor script

Jay_H

  • U0C00Y00 Fix

TheLacus

  • Create ITerrainMaterialProvider and allow overriding by mods
  • Add “Create > C# Mod Script” menu for quickly adding new mod script

Interkarma

  • Add back Rigidbody to PlayerAdvanced
  • Refill player vitals after banishment
  • Prevent Seducer stunlock during transformation
  • Fix out of work exception
  • Use questor billboard when moved by their own quests
  • Handle removal of magic items broken via combat hits
  • Visibly show effect of Drain Speed on enemies
  • Fix equipped “item used do” quest action handling and more
  • Fix multiple “teleport pc” into dungeon desync from world
  • Change Sx977 PlaySound usage
  • PlaySound now counts times sound is played
  • Fix ending condition for Lysandus’ Revenge
  • Add “print_quests” console command
  • Fix exiting non ground-level doors at higher terrain altitudes
  • Unlock Castle Daggerfall doors after teleporting inside
  • Console font fixes
  • Exclude Mantellan Crux “BOX” as crushing hazard
  • Fix custom region overlay on travel map
  • Do not process exhaustion event if player already dead
  • Store lastKeyCode during EventType.KeyDown handling
  • Force weather update after teleporting to different climate
  • Don’t import classis rumours in Save Explorer

Localizing Strings in Daggerfall Unity – Part 6

Series
Localizing Strings in Daggerfall Unity – Part 1
Localizing Strings in Daggerfall Unity – Part 2
Localizing Strings in Daggerfall Unity – Part 3
Localizing Strings in Daggerfall Unity – Part 4
Localizing Strings in Daggerfall Unity – Part 5
Localizing Strings in Daggerfall Unity – Part 6

Custom Fonts

Note: Before progressing to this tutorial, please update source project to Daggerfall Unity 0.11.3 or later. This version has fixes required to complete this part in series.

In Part 3 of this series, we noted the Korean (ko) locale would print out question mark characters (?? ???) instead of proper glyphs.

This happens because Daggerfall Unity does not yet have an appropriate font asset to render these characters. The default fonts have a full complement of Latin characters but non-Latin languages require a new font to display their unique alphabet.

This tutorial will demonstrate how to add a custom Korean font with a Hangul alphabet to Daggerfall Unity, but the same process can be used to add Cyrillic fonts, Kanji fonts, or even just a custom default font.

The font we’ll be using is Noto Serif KR from Google Fonts. Click Download family on that page to download the font used in this tutorial, or substitute with another TTF/OTF font for your language.

Once downloaded, unzip the whole font family and locate NotoSerifKR-Regular.otf. This is the specific font we’ll be using. To start with, we’ll add this font to our Unity project.

  1. In Project view, navigate to our DemoTranslationMod/Resources folder.
  2. Drag and drop the NotoSerifKR-Regular.otf font into this folder with other resources. Unity will import this like below.

Create TextMeshPro Font

Daggerfall Unity uses TextMeshPro (TMP) fonts. Before we can see this font in game, we need to create a TMP font asset.

  1. Click Window menu > TextMeshPro > Font Asset Creator
  2. Set NotoSerifKR-Regular in Source Font File by clicking the circle selector on right-hand side then selecting font

Now we need to determine which character codes our TMP font will support. This will vary based on many factors unique to the target language, but the core concept is that we want to inform Font Asset Creator which character codes from your alphabet to compile into your TMP font. Any characters not added to TMP font asset will continue to display as question marks in game.

There are multiple ways to describe which characters to use. You can select from a basic list of settings, use decimal/hex ranges, import from another TMP font, import from a file, etc. Whatever method you use, keep track of the settings so you can add to it later if any characters are found missing.

In this example, we’re going to use a subset of Hangul alphabet by directly entering the characters required. It’s better to start with a subset of characters for the region/dialect you’re targeting rather than just trying to include everything. Some languages have thousands of characters which can result in an unusable TMP atlas without enough fidelity.

  1. In Font Asset Creator, drop down Character Set selector and choose Custom Characters
  2. Copy and paste the following custom characters into the Custom Character List text box. Note the very first character is a space character.
 ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz가개갸거게겨고괴괘교구귀궤규그긔기나내냐너네녀노뇌놰뇨누뉘눼뉴느늬니다대댜더데뎌도되돼됴두뒤뒈류드듸디라래랴러레려로뢰뢔료루뤼뤠류르릐리마매먀머메며모뫼뫠묘무뮈뭬뮤므믜미바배뱌버베벼보뵈봬뵤부뷔붸뷰브븨비사새샤서세셔소쇠쇄쇼수쉬쉐슈브븨비아애야어에여오외왜요우위웨유으의이자재쟈저제져조죄좨죠주쥐줴쥬즈즤지차채챠처체쳐초최쵀쵸추취췌츄츠츼치카캐캬커케켜코쾨쾌쿄쿠퀴퀘큐크킈키타태탸터테텨토퇴퇘툐투튀퉤튜트틔티파패퍄퍼페펴포푀퐤표푸퓌풰퓨프픠피하해햐허헤혀호회홰효후휘훼휴흐희히역을선택십시1234567890‘?’“!”(%)[#]{@}/&\<-+÷×=>®©$€£¥¢:;,.*…

The above characters are enough for this tutorial, but will need to be expanded for full language support. This is how it looks in Font Asset Creator. We’re also adding the basic English alphabet to have a well-rounded font that can still display any untranslated English text.

Click Generate Font Atlas to render all the specified characters into a TMP atlas. Once you’ve created the atlas, you’ll see all the characters packed like below. Click for full size.

TextMeshPro renders glyphs using signed distance fields (SDF). How this works is outside the scope of this tutorial, but to summarise it’s a way of representing fonts using mathematical values that can maintain smooth shapes at any resolution.

In the output field, take note of the Missing characters, Excluded characters, and “characters missing from font file”. This will display any character codes you requested but could not be found in the provided TTF/OTF font. If your source font is missing any important characters, then it’s necessary to locate another TTF/OTF font containing those characters.

Depending on your font requirements, you might want to increase Atlas Resolution, e.g. to 4096×4096 or higher to support more characters with good fidelity. You can also adjust packing method, sample size, etc. for your specific font needs.

For this tutorial, the atlas generated above is good enough. Click the Save button and save your new TMP font to DemoTranslationMod/Resources. We’ll use the default name in a moment, please don’t change it. This creates a new TMP font asset like below with the name “NotoSerifKR-Regular SDF”.

This new SDF asset contains the atlas and other information required to render the TMP font in Daggerfall Unity. You can come back and recreate the font later with different properties or more characters if needed.

Associate Font With Locale

There’s one more step before can see this font in game. We need to associate our custom font with the correct locale so that Daggerfall Unity knows to use it. This is done using the StartupScript.cs code we created previously.

Open StartupScript.cs in your code editor and replace the entire contents with below. Don’t forget to save your changes!

using UnityEngine;
using UnityEngine.Localization;
using UnityEngine.Localization.Settings;
using DaggerfallWorkshop.Game;
using DaggerfallWorkshop.Game.Utility.ModSupport;
using DaggerfallWorkshop.Game.UserInterface;

namespace DemoTranslationMod
{
    public class StartupScript : MonoBehaviour
    {
        // Define the names of translated string table collections
        const string runtimeInternalStrings = "Demo_Strings";
        const string runtimeRSCStrings = "Demo_RSC";

        public static Mod mod;

        [Invoke(StateManager.StateTypes.Start, 0)]
        public static void Init(InitParams initParams)
        {
            mod = initParams.Mod;
            var go = new GameObject(mod.Title);
            go.AddComponent<StartupScript>();
        }

        private void Awake()
        {
            // Set TextManager properties to use translated string table collections
            TextManager.Instance.RuntimeInternalStrings = runtimeInternalStrings;
            TextManager.Instance.RuntimeRSCStrings = runtimeRSCStrings;

            // Load KO font
            DaggerfallFont font_ko = new DaggerfallFont(DaggerfallFont.FontName.FONT0003);
            font_ko.LoadSDFFontAsset("NotoSerifKR-Regular SDF");

            // Assign KO font
            Locale ko = LocalizationSettings.AvailableLocales.GetLocale("ko");
            if (ko)
            {
                TextManager.Instance.RegisterLocalizedFont(ko, DaggerfallFont.FontName.FONT0003, font_ko);
            }

            Debug.Log("StartScript has completed.");
        }
    }
}

Let’s take a look at what changed. To start with, we added some new using statements. These import some extra functionality to the script.

using UnityEngine.Localization;
using UnityEngine.Localization.Settings;
using DaggerfallWorkshop.Game.UserInterface;

Then we added the following code to associate our custom font with the KO locale to Daggerfall’s FONT003. This is the default font used in most parts of the game.

// Load KO font
DaggerfallFont font_ko = new DaggerfallFont(DaggerfallFont.FontName.FONT0003);
font_ko.LoadSDFFontAsset("NotoSerifKR-Regular SDF");

// Assign KO font
Locale ko = LocalizationSettings.AvailableLocales.GetLocale("ko");
if (ko)
{
    TextManager.Instance.RegisterLocalizedFont(ko, DaggerfallFont.FontName.FONT0003, font_ko);
}

First, we create a custom DaggerfallFont called font_ko. By default we’re loading FONT003, but we’ll replace this in a moment with our custom font.

Second, we tell font_ko to load our custom font asset using LoadSDFFontAsset(). Any font created using the TextMeshPro Font Asset Creator should load OK. Reminder: you need to be on Daggerfall Unity 0.11.3 or later.

Finally, we try to get the “ko” locale and only continue if this locale is found. If the locale is found, we associate our custom DaggerfallFont with the “ko” locale using RegisterLocalizedFont().

When this code executes at startup, Daggerfall Unity now knows it should use a different font when rendering FONT003 within the Korean (ko) locale. You can associate the same SDF font with FONT001, FONT002, etc. but you might want to use different styles of typefaces to better match the desired look and feel in your translation.

Make sure your changes are saved, then we can try this font in game.

  1. Click Play to start the game and click through to title menu.
  2. Use the locale drop-down to select Korean (ko) in Game view.
  3. Click Start New Game in title menu. If everything works as expected, our custom font will be selected and used with our translated text example.

Click Play again to stop game.

To summarise, creating a custom font requires the following steps:

  1. Locate appropriate TTF/OTF source fonts for your language. These fonts must contain all the alphabet characters you need for your translation.
  2. Import the TTF/OTF font into Unity project.
  3. Use the Font Asset Creator to generate a custom TMP font asset with the required characters and resolution.
  4. Associate new font with your custom locale and related Daggerfall font in startup C# script.

You might need to recreate font several times when creating your translation mod, either to add new characters, change resolution, or just finetune the look and feel. If you change the asset name, don’t forget to update this in your startup script.

Now that we have a custom font, we can move on to packaging our localisation to standalone files. This will be covered in Localizing Strings in Daggerfall Unity – Part 7.

Daggerfall Unity Beta 0.11.3

Daggerfall Unity 0.11.3 is now available on Live Builds page. This is another general bug-fix release with some updates to mod system.

Starting from this release, I’m attaching zipped builds along with patch notes to Releases page on GitHub. This will eventually become a longer-term archive for older builds even after they’re cleaned up from Live Builds page. If there’s enough demand, I can work through attaching older builds to previous releases on this page.

Now that I’m finally caught up with code review, I’ll be able to get back into the localization tutorial series. This series was pending some fixes rolled out in 0.11.2 and 0.11.3, so please be sure to update before the next article in series is published.

Quest Debugger Input Changes

The quest debugger has a few changes to input settings. These changes are to prevent accidentally opening debugger during normal play, free up the Tab key for other uses, and to make shortcuts easier on non-US keyboards. For example, the square bracket keys [ and ] are not so easy to use on AZERTY keyboards.

If you are not a quest author or don’t care about quest debugger, you can ignore these changes.

  • Quest debugger is now disabled by default. Must edit EnableQuestDebugger=True in settings.ini to activate it again.
  • Ctrl+Shift+D now cycles through debugger display states off/partial/full
  • Ctrl+Shift+LeftArrow now opens previous active quest while debugger active
  • Ctrl+Shift+RightArrow now opens next active quest while debugger active
  • Ctrl+Shift+UpArrow now teleports to next dungeon quest marker while debugger active inside dungeon
  • Ctrl+Shift+DownArrow now teleports to previous dungeon quest marker while debugger active inside dungeon

Note: Some inputs might move character, e.g. Ctrl+Shift+D will also move character slightly to right when activating debugger. This is expected and not considered a breaking issue for a debug/development feature that is normally disabled.

General Fixes & Improvements

Pango

  • Potion maker: Fix issues tracking ingredient stack count between cauldron and player inventory
  • Conjured arrows: Don’t stack conjured arrows with different time-to-live
  • Conjured arrows: Always shoot conjured arrows first, priority to lowest time-to-live
  • Conjured arrows: Change colour of arrows to show if conjured or real in inventory and arrow counter on HUD
  • Conjured arrows: Prevent shooting a conjured arrow converting to a real arrow

Ferital

  • World: Fix classic bug relating to %ef macro not using correct local race for building names

Hazelnut

  • DaggerfallQuestJournalWindow: Change access permissions to allow overriding by mods
  • DaggerfallQuestJournalWindow: Allow events to be overridden by mods
  • DaggerfallLoot: Allow mods to add or modify loot items via FormulaHelper.ModifyFoundLootItems() override
  • Inventory UI: Right-click now works as described in Daggerfall manual to perform complement of equip/remove, appearance cycling moved to middle-mouse

KABoissonneault

  • DaggerfallInventoryWindow: Change access permissions to allow overriding by mods
  • Biographies: Fix issues parsing patched BIOG files
  • Biographies: Add ability to add custom biographies
  • FormulaHelper: Add hook to override CalculateCasterLevel
  • FormulaHelper: Add hooks to override spell costing formulas CalculateTotalEffectCosts, CalculateEffectCosts, ApplyTargetCostMultiplier
  • Magic: Fix spells with multiple effects ending too early

Bl4ckh34d

  • World: Fix incorrect nature billboards at climate borders

XJDHDR

  • ActionDoor: Add support for MeshCollider
  • RuntimeMaterials: Fix bug where dungeon texture not applied if runtime material not attached to base object
  • MeshReplacement: Fix regressions of new scripts not added to mod-added models

TheLacus

  • TextBox: Do not draw defaultText if null

Interkarma

  • World: Extend town borders by 4096 units – increases distance at which flavour text is displayed, guards will chase player out of town, etc.
  • Magic: Fix player not receiving payload of Damage Fatigue effect
  • Formula: Fix randomness of levelup health roll so this is always different, even after a reload
  • Localization: Fix exception when determining size of new font atlas using deprecated fields
  • Engine: Update Addressables package to 1.17.17

Daggerfall Unity Beta 0.11.2

Daggerfall Unity 0.11.2 is now available on Live Builds page. This is a general bug-fix release with some updates to mod system.

New Features

Custom Mobile Units (TheLacus)

TheLacus has taken a big step towards support for replacing enemies with custom graphics, including 3D models. See gif below for an example of this in action using a humble cube.

If you don’t think a cube is that amazing, consider this a 3D model injected by a mod into an enemy mobile unit to alter it’s appearance. The same could be done with a fully animated 3D model. There are some limitations around this for now, notably that classic enemy attack triggers are linked to sprite animation frames. So for now a modder would also need to reimplement parts of combat to fully replace model. But this is something that can be refined over time as the community starts experimenting with this feature and sending their feedback.

Teleport To Any Dungeon Marker (Interkarma)

This is a very minor improvement to quest debugger that finally reimplements a test/cheat feature from classic. When quest debugger is open (default LeftShift+Tab) you can now use Shift+[ and Shift+] keys to cycle forwards and backwards through all markers in a dungeon. This doesn’t require a quest to be active in dungeon, only for the quest debugger to be open while player is in a dungeon. This is handy for situations like teleporting to Medora’s room in Direnni Tower, as she’s a permanent NPC without a specific quest marker.

The keybinds for quest debugger and cycling through markers can be changed in StreamingAssets/Text/DialogShortcuts.txt.

General Fixes & Improvements

Lots of bug fixes small and large from our awesome community of devs.

Hazelnut

  • Fix dictionary access for non-existent world variant keys
  • Prevent “remote” Place quest selection from randomly selecting local Place
  • Don’t restrict shields by plate or chain to match classic
  • Move hardcoded info panel colour into DaggerfallUI
  • Allow non-member quests to have rep requirements – to fix non-joinable Witch Coven quest dispensing
  • Fix Oghma removal after use to function from everywhere including wagon

AsesinoBlade

  • Change HotKeySequenceProcessed from Bool to Enum
  • Add forward thrust to click to attack – previously this move was never selected

Deepfighter

  • Fix formatting of date lines in diary entries of quests

KABoissonneault

  • Fixed misnamed formula overrides for CalculateFatigueRecoveryRate and CalculateSpellPointsRecoveryRate
  • Fix torch burning ticks progressing while game is paused
  • Fix %hpw inconsistent with classic for Dunmer characters

TheLacus

  • Import mod settings and presets files after create or changes from editor window
  • Fix mod settings not accepting negative float values
  • Fix mod asset loading on Turkish culture
  • Fix RuntimeMaterials by ignoring climate when using dungeon table
  • Improve support of mod localization through CSV text tables

Pango

  • Toggle large HUD with F10 like classic
  • Fix interacting with HUD when cursor not active on Linux
  • Fix NullReferenceException
  • Horse now has constant jump height to clear hedges

Jefetienne

  • Add joystick middle-click keybind and set joystick UI controls to protected
  • Prevent accidental axis button “presses” from binded movement and camera axes

XJDHDR

  • Reduce delay filling Dungeon variable in PlayerEnterExit
  • Add detailed exception handling and logging to BookReader
  • Automap check CombineRDB state before resetting so it stays disabled if previously set in editor
  • Automap move mesh and material update to separate script and optimise automap creation times
  • Fix texture table in dungeon automap to match environment
  • RuntimeMaterials automap type differentiation for interior types and other models
  • Add support for the discovery state of OBJ models to be saved and loaded
  • Fix some editor warnings

Interkarma

  • Fix vampires not being offered vampire quests
  • Restore per-task click rearming
  • Update DaggerfallFont to use .atlasTexture instead of deprecated .atlas
  • Deprioritise System Locale Selector to prevent an error during localization development
  • S0000011: Fix needing to click Barenziah twice with Chapter 6 before quest ends
  • S0000011: Fix clicking Gortwog to hand in Chapter 6 with per-task click rearming
  • S0000011: Reordered gold reward so it doesn’t interupt Barenziah’s information at end of quest
  • N0B00Y16: Fix issue of clicking on merchant at wrong time stalling quest
  • S0000021: Fix King of Worms potentially spawning into Sentinel during quest
  • S0000021: Fix logic issues with click handling carried over from classic
  • S0000021: Fix success condition to correctly check player has killed lich
  • M0B21Y19: Fix victim default home being selected as local and stashing live version of dead NPC