Skip to content

Using sm_fixgrenades results in grenade data deletion #136

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

Open
xmrv opened this issue Dec 2, 2019 · 2 comments
Open

Using sm_fixgrenades results in grenade data deletion #136

xmrv opened this issue Dec 2, 2019 · 2 comments
Labels

Comments

@xmrv
Copy link

xmrv commented Dec 2, 2019

Expected behavior

Using this command would normally only reassign the ids used for grenades (and it does).

Actual behavior

But after using it; grenadeType, grenadeOrigin and grenadeVelocity entries in the nade config files get deleted. Every single nade has to be thrown and .updated again.

Steps to reproduce

  • Plugin version: 1.3.3
  • Sourcemod version: 1.10.0.6458
  • Steps to reproduce (please be specific): Just .save 3 different nades. Then .delete either 1st or 2nd one. Use sm_fixgrenades and try to .throw any <grenade id>. The nade won't be thrown.
@splewis splewis added the bug label Apr 12, 2020
@splewis
Copy link
Owner

splewis commented Apr 12, 2020

I'd suggest map reloading after sm_fixgrenades . Do you know if the grenade data is actually deleted? Your steps to reproduce don't mention whether the actual data files get deleted or not.

@xmrv
Copy link
Author

xmrv commented Apr 12, 2020

Map reloading does not fix it, sadly. The file in which the nade data is stored, does not get deleted; the text inside however does. Tested with SM 1.10.0.6478 and the bug still exists.

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

No branches or pull requests

2 participants