Bunch of Bugs, maybe

[Serious_Stan]

Game related bugs, maybe intended

• Demolitionist class is at severe disadvange compared to everything else. The Terminte Mines have the HiddenFromCombat flag set to false, which causes monsters with autocast skills to trigger (e.g. nullification). For comparision Blade Spirits are correctly hidden from combat.

• Inquisitor’s Aura on Censure seems to have had a template change (maybe). Currently it’s chance for skill disruption is either re-applied constantly or never triggers (ofc recalculated once monster reenters aura range). As already established by a previous report I made this is intended for the current tempalte in use. But is this within expection with this template change? Aura Bug & Skill Modifier On Pet Auras Bug

Modding related bugs, maybe intended

• For Shattered Realm rulesets allowedItems list only works for the misc drop section of the monster. If you want equiped weapons/armor to drop from monsters you have to set DisableMonsterDrops to False. My expectation here is that allowedItems is not limited only to the misc section and any item listed overides DisableMonster drops flag.

• This one is related to conversation files and using LuaScript for conditions. Screenthot 1 below is a “correct” use of LuaScript. Where the bug happens is if you paste the conversation branch as link somewhere else (Like in screenshot 2 ). This causes the LuaScript to be executed once per second or so. Easiest to notice if you monitor the console log or set the lua script to spawn something.
  

  
  
  
  

• An observation that console log sometimes stops showing function calls to lua. Either related to them already being shown once or after going back to the menu and back to game.

• Errors within lua function that have been registered for update do not show in the console log.

Edit: game version 1.2.0.5 and latest files extracts

[Ceno]

@Serious_Stan

Where the bug happens is if you paste the conversation branch as link somewhere else (Like in screenshot 2 ). This causes the LuaScript to be executed once per second or so.

I would recommend staying away from infinite loops (having a conversation Link to itself) in general.

[Serious_Stan]

Just a quick example I made, real use case I had has long been deconstructed. You can have it to link to another separate branch which leads to dead and still have it bug out.

[Zantai]

@Serious_Stan

Demolitionist class is at severe disadvange compared to everything else. The Terminte Mines have the HiddenFromCombat flag set to false, which causes monsters with autocast skills to trigger (e.g. nullification). For comparision Blade Spirits are correctly hidden from combat.

Irrelevant. They are untargetable and invincible.

@Serious_Stan

Inquisitor’s Aura on Censure seems to have had a template change (maybe). Currently it’s chance for skill disruption is either re-applied constantly or never triggers (ofc recalculated once monster reenters aura range). As already established by a previous report I made this is intended for the current tempalte in use. But is this within expection with this template change? Aura Bug & Skill Modifier On Pet Auras Bug

This is how it has always worked.

@Serious_Stan

For Shattered Realm rulesets allowedItems list only works for the misc drop section of the monster. If you want equiped weapons/armor to drop from monsters you have to set DisableMonsterDrops to False. My expectation here is that allowedItems is not limited only to the misc section and any item listed overides DisableMonster drops flag.

This is not how the system was designed to be used.

@Serious_Stan

This one is related to conversation files and using LuaScript for conditions. Screenthot 1 below is a “correct” use of LuaScript. Where the bug happens is if you paste the conversation branch as link somewhere else (Like in screenshot 2 ). This causes the LuaScript to be executed once per second or so. Easiest to notice if you monitor the console log or set the lua script to spawn something.

Don’t create infinite loops!

@Serious_Stan

• An observation that console log sometimes stops showing function calls to lua. Either related to them already being shown once or after going back to the menu and back to game.
• Errors within lua function that have been registered for update do not show in the console log.

You need to run lua.log true