germaniumsystem/starrypy

Plugin-driven Starbound proxy server built using Twisted.

starrypy's Issues

Connection reaper tends to stall.

If reap_dead_connections is called while a player is connecting, the reaper's LoopingCall will stall until the server is restarted.
I'm not entirely sure why this is happening, but a deferred being returned and never fired seems to be a likely cause.

EntityType definitions are incorrect

Most of the EntityType definitions are incorrect.

Known good:

• 0 = PLAYER
• 3 = ITEMDROP
• 8 = NPC

Known bad:

• 1 = MONSTER - Appears to be the new OBJECT.
• 2 = OBJECT - Not observed yet.
• 4 = PROJECTILE - Observed when felling trees and vines. Purpose unknown.
• 5 = PLANT - Appears to be the new PROJECTILE.
• 6 = PLANTDROP - Not observed despite plant interaction.
• 7 = EFFECT - Appears to be the new MONSTER.

Unknown:

• -1 = END - I honestly have no idea what this is or how to cause it. Not observed yet.
• 9 = ? - Payload contains player UUID.
• 10 = ? - Appears to be related to the mater manipulator, projectiles, and crafting. No payload.

Claims plugin allows claiming instance worlds.

Players are able to claim instance worlds (outpost, microdungeons, etc.). Once an instance world is claimed, all other instance worlds are claimed as well.

Claims plugin does not use unique identifiers

The claims plugin uses usernames to determine who should or should not be allowed to interact with a protected planet. Since these are not unique, a malicious user can easily log in using a different user's name (or change their name on-the-fly) and gain full access to protected planets.

planet_protect plugin cannot distinguish projectile origin.

The planet_protect plugin is intended to block banned projectiles from all players not in the claim list. However, the plugin cannot distinguish who created a projectile and often just blocks projectiles planet-wide.
This appears to be based on the UUIDs of players on the planet. Whoever has the first UUID decides if projectiles are allowed.

Colored names are not handled properly

Users with colored names cause multiple attribute errors when sending chat messages.

WARNING - starrypy.plugins.colored_names # Received AttributeError in colored_name. 'NoneType' object has no attribute 'colored_name'