For some reason I have a lot of “Vampiric” preffix on low levels. Not sure is it some weight problem or just luck.
I tried to check myself, but those .dbr are hell to understand because affixes don’t have name. Spent two hours extracting everything and comparing files without any result.
On the good side I found how to change global affixes weights. Replace lines in all files:
Btw, twice I forgot to call Doggo at the start, and after that his thing (egg?) was not working, I had to restart. Always works when I call him at the start of the session. Don’t remember how long it took to bug out.
Turns out he doesn’t work near stash, thats probably the reason it failed in those cases.
I just thought the doggo just appearing once per session was your intended limit on it. Sure it bothered me since I do tend to die. But just accepted it.
I dont suppose you would make a version w/o the gods event or does that cheat you told me before still work? & when you do it by console it doesnt give any feed back if you entered it correctly. So I wasnt sure if it was disabled or not. Never ran into it. I havent upgraded since because I dont want all the gods event stuff.
No, they are equal to your current character level, so keep them until you need them!
That already got mentioned before! Could not figure out why, though. Loading into the base game without any mod with a level 100+ character also results in mostly getting vampiric prefixes, so it has nothing to do with the mod, besides the higher level.
Beutekugeln work fine, like here, not one vampiric prefix
I will try to figure something out, again, although no idea where to start. For now, Beutekugeln should compensate this plenty enough.
EDIT: You mentioned “low levels”, I thought this only happens with level 100+?
These weights do look a bit ridiculous, but they actually make no sense, I assume they get influenced by something else. For example, double affixes should be extremely rare, but they are a lot more common than single affixes.
This was indeed intended for multiple reasons, though the dog was also supposed to stay where he got summoned. I should play my own mods more to notice this stuff.
Yes, type “character.GrantPlayerToken ULTIMATE_MECHANIC_DEACTIVATED” to disable them, and “character.RevokePlayerToken ULTIMATE_MECHANIC_DEACTIVATED” to enable them.
Now that you can summon the dog whenever you want, these events should be a lot more manageable, since you can trade Beutekugeln to up the chances for good events after each one easily.
Nope, low level for me. I was just high but then I randomly die facetanking some FG mini-boss and “hello Jarvis, I’ll be back”. That’s why your mod is a must for me.
And this Vampiric is on the low levels uniques, in Normal first Act. Not much, but enough to notice. Strange thing indeed.
It is only about uniqies (I don’t read single rares), so it is possible something with Affixes mod. If not then I guess it will not be easy to find.
ok reinstalled had nps with the install. Doggo is staying in my inventory now after using. Tx for that. I like the new info provided on doggo.
Also questions. When you type in that deactivate code does it have to be put in each time you play your char? or is it permanent for that char? & does it apply to all DOM chars or just the one?
Ugh new problem my quest logs have broken & its not just one char. Anyway to fix that? on low levels it dont matter but I have several in higher difficulties so not liking that.
I went ahead and straight up removed the lifeleech prefix, and this seems to have fixed the problem. I don’t have time to test it thoughtfully though.
No idea what has caused this issue, the Vampiric prefix is exactly set up like the others, but it is the only one that prevents the others from getting rolled. Removing it results in all others to appear equally often.
Point of this extra step is to skip the deletion process, which deletes everything inside the resources folder, since the source files are missing. This is also the fix for the standard version without Affixes for Uniques, where this prefix was also dominant on normal items (> Level 100).
Why don’t Beutekugelns have name when dropped? So we can see them good and clear and be happy when they drop. Also sometimes they are unreachable without clicking on name-tag.
They do? You might not notice some of them, since they are a rarity you probably filter out (e.g. Common or Magical). I could just color code them instead and make them a quest item, but they have to have a rarity, to limit the drop frequency of epic and legendary Beutekugeln (uniques get blacklisted for a while after they drop, I believe).
By the way, the rare Beutekugeln have a drop sound when not instantly picked up, in case you have not noticed yet.
Just wanted to give feed back on crashing issue. Apparently you did find it & did fix it. I swapped to quite a few of my chars going in & out of main menu & never had 1 crash. Tx!
Hi
I merged Lightweight mod with DoM, but I think something went wrong.
As I check the console there are red and yellow text indicating something is not right (the game freezes for a sec, when it generates these big red lines).
More importantly, I get game crashes sometimes (more often during sessions when I raise the hero spawn and general spawn amount).
Is there any way for me to fix this? (I tried my best to follow your instruction on how to merge everything)
First you extract both dom and lightweight to gtim dawn/mods folder.Then go into lightweight and run merge archine.Depends on version.Example type in light.It will create all the files.If it doesn’t start copying press enter as scripts can sometimes take some time.It will tell you x amount of files copied.
It will tell you access denied on templete as the folder already exist.Load up asset manager.Setup asset manager to point it to right directories.There is a guide to do so on the forum tutorials .
Go to mod > select > _Lightweight and select it.Press F7.Next go to Mod > select > Dom and press F7.
Done.Hope this help sorry i am not English so hope it makes sense
Indication that the merge was successful is when all (especially the last one, last row) Dawn of Masteries classes are displayed correctly in the skill tree and the dog spawns (and obviously is visible).
I gave Dawn of Masteries without this mod a try, and these warnings are still popping up, so I don’t think this has anything to do with the merge. I also got micro freezes twice during the two minutes I played with max spawn rates.
Now no idea what is causing these issues, but I would try it without Grim Internals to see if it still stutters or crashes.
The game was recently updated to v1.1.9.2a, so I extracted the game files in AssetManager. Next, I have patched DoM v1.2.4a and found some errors. Is there any problem to use it as it is?
I don’t know if it’s because of these errors, but it seems like skill/attriribute potions etc. are no longer dropping.
Yeah, that is a problem. I updated my game just like 20 minutes ago and the whole process worked for me fine.
Templates are missing, you should delete or rename the template folder in ‘Grim Dawn/database’ and then do the whole process again (using the Merge archives.bat). You might have to delete the records folder inside ‘mods/dom/database’ before doing that, or else the .bat won’t work. That should fix it.
EDIT: I think the template folder extracted through the Asset Manager can’t be accessed through the .bat, so the necessary templates can not get copied over. The .bat would then throw something like Access Denied. That’s probably the reason it did not work at first.
Thanks for the replies. So I removed both DoM and Lightweight, reinstalled them, removed Grim Dawn/database/templates folder and patched them (NonLightweight version).
I copied them to “Grim Dawn/works/mods/” and built them in AssetManager in the order “__Lightweight ≫ DoM”, but I still get the same error. I have no idea what I’m doing wrong.
This might be the problem. Do you put the ___Lightweight and dom inside “Grim Dawn/mods”?
EDIT: What I currently assume is that you put the folder with the .bat inside “Grim Dawn/works/mods”? The .bat goes two folders back (> mods > Grim Dawn) and then puts the template folder into “database”, which in your case would be in “Grim Dawn/works/database”.
Copy the template folder from “___Lightweight/Source” over to “Grim Dawn/database” and the issue should be gone.
