Grimrock

Zimber, thanks for the reply.

The vampires are always sunken regardless of whether they are on a slope or on flat terrain.

I don't think I have done anything out of the ordinary for the 'Warning! Game object property not saved: scope_camera.camera.camera' error to appear.
There's only two things I can think of:
The first was changing the stone shards spell pattern and its energy cost as they required adjustment;
The second was manipulating the toxiguardian's poison cloud number (I reduced it) and toxicity. Other than those two adjustments, I haven't changed anything drastically for the camera error to occur.

Oh well, I'll try and figure it out.
Cheers!

That warning will always appear when you save the game while the current camera is not the default one. It's harmless and can be safely ignored.

Uploaded a patch for some of the bug I've left behind and totally forgot about

- Fixed Vampire model offset
- Fixed a faulty Scavenger Spitter definition
- Fixed Vampire Lord sword particles
- Fixed crashing on opening party interfaces (Removed hooks referencing to non-existant scripts in party.lua)

Hi zimber In your v1.10 patch there are no files to update only the changelog.txt?

billb52 wrote:Hi zimber In your v1.10 patch there are no files to update only the changelog.txt?

Whoopsie
Reuploaded

Hi zimberzimber,
I was roaming around and just saw you goodbye message, totaly understable. I have realized this quite some time ago as well. Still I wanna thank you for wonderfull assets and models which I have used in my dungeon, they are really jewels. Hope I will see you in Log3 forums one day wish you all the best

I'll definitely drop in for LoG3 if it becomes a thing

Hi zimber (again) have tried downloading your recent upload of patch v1.10.1 and still have the same problem! only the change.log
file, yet on preview of files on nexus it does show your updated files? so I am not sure what's wrong.

Fixed for real this time

Hi! there is a missing object definition for your demon: charge_damage_hack
I looked at the code of this charge, what is the point of it? Did you have a problem with the normal MonsterChargeComponent behavior?