Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Temporary Armour, Creates Infinitely Stacking "Value" Bug #2640

Open
Yyffii opened this issue Apr 11, 2024 · 4 comments
Open

Temporary Armour, Creates Infinitely Stacking "Value" Bug #2640

Yyffii opened this issue Apr 11, 2024 · 4 comments

Comments

@Yyffii
Copy link

Yyffii commented Apr 11, 2024

Describe the issue

When 'Temporary Items' (Create Item Spell Effect) expire while equipped the armour value is retained, this leads to an infinitely stackable
armour value

To Reproduce

simply create a 1/1 duration create item spell, and equip then let expire armour, Repeat.

Expected behavior

the value should reset to the value of no armour in that slot since it has been "unequipped"

Screenshots and Logs

image
image
image

Desktop (please complete the following information):

  • OS: Windows 11 64bit
  • Version 1.1.0 RC2

Additional context

issue doesn't inherently lie within the create item script
but any temporary item.

issue is possibly from DaggerfallWorkshop.Game.Items.ItemCollections.RemoveExpiredItems()

https://forums.dfworkshop.net/viewtopic.php?t=5681
forum post of issue from 2 years back - issue still in effect.

@magicono43
Copy link
Contributor

Here would be my potential suggested fix for this:
2024-04-11_20-01

That being, adding player.UpdateEquippedArmorValues(item, false); just under player.ItemEquipTable.UnequipItem(slotToCheck);

@Yyffii
Copy link
Author

Yyffii commented Apr 12, 2024

Update:

Equipping and unequpping different armours will not fix the bloated value, However Restarting seems to reset the values to zero.

@ajrb
Copy link
Collaborator

ajrb commented Apr 12, 2024

Yes this is the correct way to fix this issue magicono, so submit a PR? Or I can do it if you'd rather not.

@magicono43
Copy link
Contributor

Yes this is the correct way to fix this issue magicono, so submit a PR? Or I can do it if you'd rather not.

I would but my local branch has been all screwed up for a good few months, and I haven't gotten to fixing it, lol. If you want to make that PR that would be nice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants