- Sep 5, 2023
- 181
- 100
fair answer to my question, I'm not sure how high of a priority it is for the base game, but I do hope that it comes out soon.
Good to hear that at some point a mod loader will handle multiple mods.You must be registered to see the links
Yeah, I think I will need that againYou must be registered to see the links
I created a proper modDescriptor.json5 for it: just extract and drop the folder into www\mods, it should show up.
Sure, updated to whatever's the latest on GitGud:Yeah, I think I will need that again
Also, do you still have your side mod with you? Is there a problem if I use your mod as an example in the wiki tutorial?Sure, updated to whatever's the latest on GitGud:You must be registered to see the links
Sure, go ahead. And here's my Left Eye Wide mod:Also, do you still have your side mod with you? Is there a problem if I use your mod as an example in the wiki tutorial?
I never actually made a tutorial on how to add a modDescription
0.4.2.7 Error (:: Danube Street): <<weatherdisplay>>: cannot execute widget: 0.4.2.7 Error (:: Danube Street): <<set>>: bad evaluation: Cannot read properties of undefined (reading 'modPath')Export<<weatherdisplay>>
This should fix it. Just replace inside www folder.Can anyone help me? I'm a newbie at this game. Downloaded the windows version on Mega and the face and body won't show up when on grovel position. Aside from that several sceneries also won't load but that I don't really mind.
View attachment 3010633
its just a file name issue. Go to graphical mods settings and enable the community version instead of beeesssWondering if anyone else is having issues with the BEEESSS Mod through the modloader? 9 times out of 10 I'm getting it loading in with the head just floating way above the body and major clipping through clothes. At first I figured it was just a compatibility issue with 4.2.7, but on DOLMods.net the BEEESSS Mod is running on 4.2.7 without any issues.
Not sure if I'm just missing something obvious here- I've tried fresh and in vanilla and I'm getting the same odd issues.
View attachment 3012286
Edit: Nevermind- I just updated the Mod folder with the newest version of the community version and it resolved the issues.its just a file name issue. Go to graphical mods settings and enable the community version instead of beeesss
So the best results for me were enabling and pushing the community mod to the top of the load order, then having the BEEESSS Mod enabled second. Since doing that, the game is running as expected with no graphical issues.I was under the impression that the Community add-on is something that must be run on top of BEES. In other words, with regards to FireMod, shouldn't they both be enabled, with the Community add-on being later than BEES in the load order?
If that's correct, it's probably something that should be mentioned in the descriptions of both mods.
Yeah, that should work as well. Either way you go, it'll end up with one mod covering the missing pieces of the other, which is what's important for preventing the massive visual glitches.So the best results for me were enabling and pushing the community mod to the top of the load order, then having the BEEESSS Mod enabled second. Since doing that, the game is running as expected with no graphical issues.
My thinking being that normally the community mod is used to overwrite files in the BEEESSS mod, so its files should take priority.
Edit: Huh, okay. I tried it out the other way (with BEEESSS first) and that results in the "newer" style coming up. I actually prefer it the other way around ("classic" BEEESSS) so I'll stick with that.
As an AMD user I see this as an absolute win lolone little thing...do not accidently pull up your nvidia overlay while in fullscreen you will be hardlocked out of your computer...like end task disabled hard locked.