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

.who not accurate (duplicate names) #75

Closed
Kainzo opened this issue Jul 25, 2013 · 4 comments
Closed

.who not accurate (duplicate names) #75

Kainzo opened this issue Jul 25, 2013 · 4 comments

Comments

@Kainzo
Copy link

Kainzo commented Jul 25, 2013

15:19 Kainzo - .who
15:19 hcbot has 32 players connected: Azden369 #31�, [RoAr]Anzedes #18�, Minion #29�, Headhunter #12�, Sarcen #7�, [RoAr]Anzedes #3�, hayden_hall #32�, Evildark #25�, Sarcen #11�, Simo #17�, Hidden #23�, te cagas :3 #37�, [roar]utsutsu #26�, [ILLUM]GREY #4�, thekillerby #35�, hero #22�, Magorax
15:19 hcbot - #19�, [RoAr]Anzedes #6�, [c3]Omni #28�, [c3]uni #8�, fullmetall #16�, Tyk #14�, iMega #30�, [c3]Oni #5�, Sauce-alfredo #20�, [C3]Yenova #13�, [RoAr]Anzedes #24�, NeWEraJoka #2�, Caveira #1�, sr.drogas #33�, hullunmylly #9�, [RoAr]Anzedes #15

@Jakky89
Copy link

Jakky89 commented Jul 25, 2013

This is because of Cube World allows players having the same names and it isn't good to prevent this because then some players arn't able to join. Therefore I implemented in my fork a player registration to get an unique id and login with password so instead of having only an entity id that changes every time you join players are able to use one account under different names. Although it is implemented it isn't usable yet with commands.

You could take a look at https://github.com/Jakky89/cuwo but I hope I learn how to merge in near future so that there is no confusion about having 2 cuwo's with different functionality xD

@matpow2
Copy link
Owner

matpow2 commented Jul 25, 2013

Jakky89, that is not the issue here.
The issue is caused by the client keeping connections open after /connect, so we need to expand ddos.py to also kick clients that do not send entity updates continually.

@Jakky89
Copy link

Jakky89 commented Jul 25, 2013

Yes sir it's a good idea. I think you could recognize those players by checking which packages are sent and which have to be sent (logically).

Also the need to register and login should prevent this so it's more complicated to write something that logs the player in automatically (and only players that are logged in are processed in relation to mobs/others).

@matpow2
Copy link
Owner

matpow2 commented Jul 25, 2013

Fixed in trunk

@matpow2 matpow2 closed this as completed Jul 25, 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

3 participants