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

Call to /user/revive doesn't check if the user is really dead. #3599

Closed
MagicMicky opened this issue Jun 12, 2014 · 4 comments
Closed

Call to /user/revive doesn't check if the user is really dead. #3599

MagicMicky opened this issue Jun 12, 2014 · 4 comments

Comments

@MagicMicky
Copy link
Contributor

I think there's been an ommission when implementing the /user/revive API call as discussed in #3056.
The problem is that when you call /user/revive, you indeed reset the gold to 0, the health to 50 and remove an item, without checking if the user is really dead.
It could end up in bad implementation where you might call the /user/revive API without the user actually being dead.

My opinion would be that it should send back an error if the user isn't dead, or do as it does if the user is indeed dead.

Cheers,

@MagicMicky
Copy link
Contributor Author

Did someone check if it was true ?

@paglias
Copy link
Contributor

paglias commented Nov 3, 2014

@paglias
Copy link
Contributor

paglias commented Nov 3, 2014

typo fixed in HabitRPG/habitrpg-shared@e788872

@MagicMicky
Copy link
Contributor Author

Thanks a lot ! :)

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

2 participants