Living is Pain (alpha version)

[fodz]

5 hours ago, Dlinny_Lag said:

All LiP attributes are 0 by default except Health related attributes (they has 100 as the default). There is just no code yet to alter them on start for player, like it is done for some NPCs.

Is it the issue for you?

 

Hi, health started at 0 and nothing changes, not one attribute. I solved it because I noticed that the load order is actually important, I fixed it by having it this way (check attachment please) . Basically my intuition that the mod was reading null values so there must be something wrong with the order.

Also, If you put (Additional Attributes) AA.esm in a higher order to be loaded after the UI and Livinginpain.esl, LiPUI will not work at all( I know this is common sense to you but I am writing it for others that are not experienced that might stumble here, load order is important and I think you should mention it in the main page). So the Loot organized order ended up in me getting no UI or static 0s. Following the order that I put, everything should be fine and now it is working.  The mod is really ambitious and you are a man of culture, a scholar and a genius. Thank you:)

Edited August 3, 2024 by fodz

[Dlinny_Lag]

32 minutes ago, fodz said:

load order is actually important, I fixed it by having it this way

Looks like an issue of your mod manager. 

For example, LiPUI.esl has AA.esm and LivingIsPain.esl as master files and mod manager should be able to order your mods automatically. But your mod manager doesn't order them right. Even on the screenshot the order is incorrect (LiPUI.esl must be placed lower than LivingIsPain.esl and LiPEffects.esl must be placed lower than LivingIsPain.esl)

 

What mod manager do you use?

 

[fodz]

6 hours ago, Dlinny_Lag said:

Looks like an issue of your mod manager. 

For example, LiPUI.esl has AA.esm and LivingIsPain.esl as master files and mod manager should be able to order your mods automatically. But your mod manager doesn't order them right. Even on the screenshot the order is incorrect (LiPUI.esl must be placed lower than LivingIsPain.esl and LiPEffects.esl must be placed lower than LivingIsPain.esl)

 

What mod manager do you use?

 

Mod organizer 2. The game is playing fine though. The values are changing accordingly. To be honest I agree, the main mod should run first, then the other ones that uses it. But since it is working fine, can I ignore? This is the way I did it, not MO2, the way Mo2 and loot did it, is this

Edit: basically I tried again with this more correct order from Loot and everything also works perfectly. I do not know what made it not work earlier and giving me 0 values, or no UI at all. Both my previous order and this one works, I do not know what order was the first time around that caused the issues. Thank you, I will test and give you feedback in case of errors.

 

 

 

Edited August 3, 2024 by fodz

[Dlinny_Lag]

14 hours ago, fodz said:

But since it is working fine, can I ignore?

If you performed enough tests - yes. But it hard to say at your side - were my tests enough to be sure that everything ok?

 

As I can see MO2 hasn't auto-ordering capability. So my suggestion here - use LOOT always after mods installation/uninstallation.

 

[vranina]

I have a question, which gameplay mods can be used together with this mod?

[Dlinny_Lag]

10 hours ago, vranina said:

I have a question, which gameplay mods can be used together with this mod?

I suppose any. No incompatibilities known. Exception may be mods that may confuse player because of illogical situations. 

[Mimirue17]

any chance you are looking at KFT as well as DD? DD is buggy as all heck and only use it when its a hard requirement for a mod to work (so not used here as its a soft requirement)

[Dlinny_Lag]

5 hours ago, Mimirue17 said:

any chance you are looking at KFT as well as DD?

Chance - yes. When - I don't know. I have no time to work on the mod at this time. 

LiP framework is designed to be more or less easily extended, so anyone else can add support of KFT

[WolFRocK]

[11/22/2025 - 07:52:02AM] Cannot open store for class "LiP:EffectsMain", missing file?
[11/22/2025 - 07:52:02AM] error: Unable to bind script LiP:EffectsMain to LiPEffectsMain (FE034803) because their base types do not match

[Dlinny_Lag]

On 11/22/2025 at 11:11 AM, WolFRocK said:

[11/22/2025 - 07:52:02AM] Cannot open store for class "LiP:EffectsMain", missing file?
[11/22/2025 - 07:52:02AM] error: Unable to bind script LiP:EffectsMain to LiPEffectsMain (FE034803) because their base types do not match

Most likely invalid installation. I suppose you use MO2, as people complain a lot for similar problems when use it. Resolve your mod manager issues.

Less probably - you've deleted somehow the file after installation.

[judge007]

On 11/21/2025 at 10:11 PM, WolFRocK said:

[11/22/2025 - 07:52:02AM] Cannot open store for class "LiP:EffectsMain", missing file?
[11/22/2025 - 07:52:02AM] error: Unable to bind script LiP:EffectsMain to LiPEffectsMain (FE034803) because their base types do not match

 

21 minutes ago, Dlinny_Lag said:

Most likely invalid installation. I suppose you use MO2, as people complain a lot for similar problems when use it. Resolve your mod manager issues.

Less probably - you've deleted somehow the file after installation.

I encountered those errors with Living is Pain, I have a habit of archiving everything.

When archived those errors popped up. When loose files they did not.

 

Maybe that helps?

[Dlinny_Lag]

3 hours ago, judge007 said:

Maybe that helps?

I guess I've got the problem.

Thanks for letting me know. Package LiP-Effects-0.6.2.zip contains wrong file. I will update it shortly

 

UPD: Please use new version of LiP Effects - 0.6.3

 

Edited November 23, 2025 by Dlinny_Lag

[Mistah F]

This is interesting. Is there any integration with Sexual Harassment or Provocative Perks?

[Dlinny_Lag]

6 hours ago, Mistah F said:

Is there any integration with Sexual Harassment or Provocative Perks

No direct integration.

Activities initiated by SH may cause LiP attributes change. PP is totally independent.