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

DB auth TABLE ban #7

Closed
gpn39f opened this issue Oct 14, 2013 · 2 comments
Closed

DB auth TABLE ban #7

gpn39f opened this issue Oct 14, 2013 · 2 comments

Comments

@gpn39f
Copy link

gpn39f commented Oct 14, 2013

the table "ban" is not includet in the core.
if i take a look into, the banned flag is set/unset in table account.
the table ban holds data about IP
this is not a good Idee here in Germany. we have a dynamic IP. also every time we Access the Internet, we will become a other IP adress. next time maybe you become same IP as i have now.
we can include the ban_date, unban_date, ban_reason, ban_by and ban_active to the table account or create a new structure to table ban.

what is bether? what do you think?

@billy1arm
Copy link

server two has not had a lot of recent work done to it, but the ban table should be indentical to an earlier core

  • We are currently tidying up ServerZero and those changes will filter down into the other cores as soon as we can

If you are feeling brave, please attempt to fix this and issue a pull request

Thanks

@gpn39f
Copy link
Author

gpn39f commented Oct 18, 2013

the Server are now using banning by Name.
i was found several packet there are corrupt.. mostly are now corrected
the first Player can now spawn on world, and all NPCs to..

@gpn39f gpn39f closed this as completed Oct 18, 2013
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