For a binary download, see https://www.nexusmods.com/grimdawn/mods/43/
This project uses Nuget for external dependencies. To reinstall these, simply run Update-Package -reinstall in the package manager console.
Error CS0246 The type or namespace name 'AutoUpdaterDotNET' could not be found (are you missing a using directive or an assembly reference?) IAGrim X:\Y\Z\iagd\IAGrim\UI\MainWindow.cs 13 Active
This means you're missing the AutoUpdater.NET.dll file that IA uses for automatic updates. It can be obtained in two ways:
- Simply copying it from an existing IA install
- Compiling the "Auto updater" project, which is held separately from the IA solution. (SLN) Place this file under IAGrim\bin\Release
The process cannot access the file 'IAGrim\obj\x86\Debug\IAGrim.exe.tmp' because it is being used by another process.
StackTrace:
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite, Boolean checkHost)
at System.IO.File.Copy(String sourceFileName, String destFileName, Boolean overwrite)
at InnerWeaver.ReadModule() in C:\projects\fody\FodyIsolated\ModuleReader.cs:line 22
at InnerWeaver.Execute() in C:\projects\fody\FodyIsolated\InnerWeaver.cs:line 93
When cloning IA and redownloading nuget packages, the settings for fody may have gotten messed up.
In IAGrim\IAGrim\IAGrim.csproj make sure that the Nuget import for fody is as following: <Import Project="..\packages\Fody.2.0.0\build\netstandard1.4\Fody.targets" Condition="Exists('..\packages\Fody.2.0.0\build\netstandard1.4\Fody.targets') And '$(Configuration)' == 'Release' " />
Particulary the And '$(Configuration)' == 'Release' to prevent fody from stamping debug builds.
IAGrim also depends on ItemAssistantHook.dll for detecting the status of various things ingame. The easiest way to obtain this DLL is by simply copying it from a recent installation of IAGrim. If you do decide to compile it yourself, or need to make changes to the DLL, check the IA\ folder. The DLL uses C++ and Assembly, and requires C++ Boost to run. No package managers are in use for this project and expect it to be non-trivial to get up and running.
HowTo:
- cd WebUI
- npm install
- npm run build
- deploy.cmd
When building in "Release mode" the compilation will fail on the first attempt due to an issue with Stamp.Fody.
Running the release mode again should result in a successful build. [Stamp.Fody embeds the git branch/hash into the iagrim.exe file]
The Web view is written in React and Typescript. It can run both Embedded inside IAGrim, and stand-alone in a normal browser for debugging purposes. After first cloning the project, the developer should run "npm install" to download node packages.
The user interface is made in native C# (left side bar, top tabs) with CefSharp (Chromium) to run an embedded web view. The web view is written using React and Typescript.
The web view communicates with IAGrim in the following scenarios:
- [1] Transfer items
- [2] Scrolling (delay load more items)
- [2] Load items on startup
- [2] Load recipes
- This method uses regular links, like transfer://itemid, these are then caught by IA and passed on to the appropriate service.
- This method uses the "magic" global variable called data, which is exposed into the embedded webview by Chromium (via JSWrapper) The data object contains both data and functions which can be called. Ex: Functions which are implemented in IAGrim, so that the Webview can call "data.RequestMoreItems" when infinite scrolling etc. The functions are async, and IAGrim will respond by calling a different callback in the data object.
IA communicates with the Web View in the following ways:
- Update items
- Display messages
- Update recipes
- Etc..
IAGrim exclusively communicates with the Web UI via the "data" object. The web UI will have updated the data object with pointers to its own methods (ala data.globalAddItems = addItems;) So that IAGrim calls the appropriate code.
Database operations are done by the classes located in the DaoImpl* classes. These classes are then wrapped in a "Repo" named counterpart implementing the same interface as the Impl class. The repo-class is responsible for executing all the methods using the ThreadExecuter class.
The ThreadExecuter is a class which contains 1 dedicated thread for running SQL operations. All calls are run async, but uses waiting to run blocking for the calling function.
This ensures that all database transactions are run on a single thread, which is imperative when running with an SQLite backend. (There are older versions of IA which uses PostgreSQL, which do not wrap the calls using the ThreadExecuter)
The StashFileMonitor class is responsible for monitoring the Grim Dawn savegame folder for file changes. Once a change to transfer.gs? has been detected, it will notify the StashManager about the change. The StashManager is responsible for verifying that the player has left the stash area (prevent the player from re-opening the stash while IA is using it) and that the stash is indeed closed.
IAGrim uses a DLL Proxy which it injects into the game process for the purposes of "spying" on some information about the current game state. Such as: If the stash is open, the player position, if cloud saving is enabled. The goal is to ensure that it is indeed safe to transfer items, before any item transfers are attempted by IA.
Messages are passed from the C++ dll via WINAPI SendMessage, IA is listening for these messages using a window created with a specific class name.
Item searches are done for owned items, recipe items*, buddy items* and augments*. The search result is then merged stored. Stats delay loaded and applied to items as the user scrolls.
*) If configured to be included.
In order for IA to recognize item stats, it needs to parse the Grim Dawn item database. (item templates) IA will parse the database and "cache" the results in the IA database for lookups during search. If a player item does not match any known template (different mod, not loaded AoM, other..), the item will simply be displayed as "Unknown Item" Loading items is only done for visual purposes and to enable search. Even if an item is unknown, the item will be replicated in-game with its original stats.
Translations are handled in two ways: For the web ui, they are passed in via the JSWrapper object. For the C# Forms user interface, the "tag" property is used to detect the appropriate translation string. Default language is located in EnglishLanguage.cs, IA looks for tags_ia.txt in GD translation files.
SELECT
id_playeritem,baserecord,PrefixRecord,SuffixRecord,ModifierRecord,null, Seed,MateriaRecord,RelicCompletionRecord,RelicSeed,null, 0,0,MateriaCombines,StackCount, null,null,null,null,0,null,null,0,null,null,null,null,null,null
FROM playeritem WHERE id_itemowner = 41025536
UPDATE PlayerItem SET enchantmentrecord = NULL where enchantmentrecord = 0; UPDATE PlayerItem SET azuuid_v2 = NULL where azuuid_v2 = 'NULL'; UPDATE PlayerItem SET azpartition_v2 = NULL where azpartition_v2 = 'NULL'; UPDATE PlayerItem SET Mod = NULL where Mod = 'NULL'; UPDATE PlayerItem SET TransmuteRecord = NULL where TransmuteRecord = 'NULL';