TFS 1.X+ Creature Moves On Fields Bug | TFS 1.5 Nekiro Downgrade 8.0

[iNux]

Hello,

While working, experimenting, and testing different things, I arrived at the point of trying out the creature immunity system at GitHub - nekiro/TFS-1.5-Downgrades at 8.0 (https://github.com/nekiro/TFS-1.5-Downgrades/tree/8.0). I attempted to block the creature's path with a field that they were not immune to, for example, a rat. According to the expected functionality, a rat should never be able to pass through a field that is blocking its path, unless it's attacked.

Initially, I thought that I had somehow broken the code that handles movement on fields. However, I tested it on a fresh TFS 1.5 Nekiro Downgrade 8.0 and the result is the same.

Could someone refer me to where I should look or perhaps help me understand why it does not work on GitHub - nekiro/TFS-1.5-Downgrades at 8.0 (https://github.com/nekiro/TFS-1.5-Downgrades/tree/8.0)

Bellow is a gif representing a hunter walking on fire field without being attacked.

Gyazo Screen Video

gyazo.com

 

[rlx]

Did you add <flag canwalkonfire = "0" />? Base nekiro monster do not have these flags for fire/poison/energy fields.

 

[iNux]

Did you add <flag canwalkonfire = "0" />? Base nekiro monster do not have these flags for fire/poison/energy fields.

Thank you, that solved it. I didn't notice those flags.

 

[3alola1]

Thank you, that solved it. I didn't notice those flags.

How did you mange to fix the bug when even the monster is getting flamed loses health too quickly with 0.5 exhaust?

 

[rlx]

How did you mange to fix the bug when even the monster is getting flamed loses health too quickly with 0.5 exhaust?

You might need to apply these changes in items.xml (changing damage to initdamage) - remember about campfires too, not only field items.

M

TFS 1.X+ Post in thread 'Condiction on tfs 1.5 nekiro 7.72'

May 20, 2022

hello I have 2 problems in nekiro 7.72's tfs 1.5, one of them is the condition of the fields, the monster when receiving damage from the player goes up very quickly the first damage, something around 1 second +/-
the other problem is, the monster that in this version didn't go over the fire field, for example, ignores it and goes over it. how to fix it?


View attachment 67140

1. Open items.xml

search for the fields that you need to change(fire and energy)

Change the first damage to initdamage.

From:

    <item id="1491" article="an" name="energy field">
        <attribute key="type"...

• mano368

• 

 

[czouski]

You might need to apply these changes in items.xml (changing damage to initdamage) - remember about campfires too, not only field items.

M

TFS 1.X+ Post in thread 'Condiction on tfs 1.5 nekiro 7.72'

May 20, 2022

hello I have 2 problems in nekiro 7.72's tfs 1.5, one of them is the condition of the fields, the monster when receiving damage from the player goes up very quickly the first damage, something around 1 second +/-
the other problem is, the monster that in this version didn't go over the fire field, for example, ignores it and goes over it. how to fix it?


View attachment 67140

1. Open items.xml

search for the fields that you need to change(fire and energy)

Change the first damage to initdamage.

From:

    <item id="1491" article="an" name="energy field">
        <attribute key="type"...

• mano368

• 

<item id="1492" article="a" name="fire field">
<attribute key="type" value="magicfield"/>
<attribute key="field" value="fire">
<attribute key="damage" value="20"/>
<attribute key="ticks" value="9000"/>
<attribute key="count" value="7"/>
<attribute key="damage" value="10"/>
</attribute>
</item>
this one will spam half second

and this one will not:


<item id="1487" article="a" name="fire field">
<attribute key="type" value="magicfield"/>
<attribute key="replaceable" value="1"/>
<attribute key="decayTo" value="1488"/>
<attribute key="duration" value="200"/>
<attribute key="field" value="fire">
<attribute key="initdamage" value="20"/>
<attribute key="ticks" value="10000"/>
<attribute key="count" value="7"/>
<attribute key="damage" value="10"/>
</attribute>
</item>

also while testing i stepped on the first one then second then first again and the first one didnt repeat the damage over half second so it must be something with condition from the normal one overloading init damage since it is the same condition

Post automatically merged: Nov 19, 2024

@Nekiro it would be nice to maybe from time to time push a few small commits or open the repository so we can do pull requests ?