Sometimes upon logout or ship unpilot the hotbar menu does not go away, wiping the player's original hotbar.

Bugged somehow
(todo: fix, and better issue description)

Waiting on #95

Ships need to update carried multiblocks, as it is, they undetect and leave an invalid multiblock in the chunk

Currently custom items and blocks are represented by string ids, which is... rather dumb.

There should also probably be wrapper classes that define a "block", or an "item stack" but doesn't care whether it's vanilla or custom.

This is one of the reasons id like to consider switching to serverside fabric, as items and blocks could be registered mostly normally using something like Polymer or PolyMc

from stellarica-server

Might need to use BlockDropItemEvent to fix.
Pretty sure the issue is event.isDropItems is always true, even if it shouldn't drop items (like if the player is in Creative mode)
Need to look into this more.

We want to have a resource pack to override vanilla stuff, we should probably let polymer-autohost serve it.

Currently it’s just a Set<Material>. EnumSet is better optimized for Enums.

Also the per ship detectable list needs to be reimplemented, some scraps exist from MSP but it isn’t functional.

Just causes annoying log spam.

I'm hoping using the 1.19.4 block displays we can have animated smooth elevators, similar to SL's elevators, but animated.

self-explanatory

The current configuration system is... really dumb.

It uses the built-in bukkit api, which is really terrible compared to libraries such as configurate and kx.ser
In addition, effects such as projectiles, and maybe multiblock actions, should be able to be defined in config files.

If simple config files aren't enough, I wouldn't mind messing around with using kotlin scripts loaded at runtime (kotlin supports it pretty well, and performance should be good enough:tm:)

Effects like rain and snow have issues with ships, as the nms block setting doesn’t update the heightmaps.

See https://discord.com/channels/982317567333007450/982451914899873832/983575178602770482 for a solution

When rotating ships the player's coordinates get rounded, so their relative position to the ship does not stay the same

Because of RecipeChoice.exactChoice items with non-zero power (different nbt) can not be used in crafting.
One way to get around this was custom crafting in which crafting is left to a listener rather than the bukkit api, but the complexity probably isn't worth it.

Currently the rough plan for thrusters is:
3 types, three sizes of each type.
The types are:

• Ion - Requires power, but no fuel. Low max speed, low acceleration.
• Chemical - Requires fuel, but no power. Medium max speed, high acceleration.
• Fusion - Requires fuel and power. High max speed and acceleration, but bulky and has a high operating cost.

Should probably be done after #33

Certain blocks, such as tall grass and snow should be able to be overwritten in ship movement, rather than stopping the ship.

Self-explanatory

Not that much of an issue, but the GC can take a while.
This might lead to a bunch of subtle, hard to find bugs.

Would allow multiple varieties of glass to be used, for example.
Not quite sure how best to go about this. It should probably wait until after #60

See @NovaForeverSL's star system idea.
Also relies on #89

Should be fairly easy using a ChunkSnapshot

Currently it is hardcoded so only chests move properly. This can easily be fixed, but I can't find a way to check if a block is a tile entity from a ChunkSnapshot, other than by checking the material against a list, which seems dumb.

Update: October 12, 2023

I just closed all existing issues on this repo, for the most part they were features to implement, not actual bugs. From now on issues here will be actual bugs, not future planning nonsense.

Original Content

Most of the "issues" here are just issues for the GitHub Project so we can use tags.

If you want to find actual issues, filter by issues with the "bug" label.

Special multiblocks that integrate with the ship to provide a Star Legacy-like weapon system

Hydrazine should have a scoreboard HUD similar to the system I developed for OldIon. In it players can add or remove "widgets" which display data on the scoreboard. The preference would need to be stored, probably in a SQL database

If possible it should be done using the team feature as objectives cause flicker with bad ping (sending 2 packets instead of 1)

Currently only the pilot is moved with the ship. It needs to find all passengers and move them all.

Dark unhospitable planet with a barren obsidian surface, intended to be an endgame mining area concentrating many end-game and high demand resources.
The planet is almost fully made of obsidian, and bedrock is scattered all around underground, with more bedrock blocking your way the deeper you go (like the vanilla bedrock fade-in, but it spans around 80 blocks instead of 4), with more loot to be found on deeper Y levels.

Random details & ideas: no/toxic atmosphere, high radiation levels, possible thunderstorms (?); a gas giant moon (?); cracks in the surface going a few blocks down and having crying obsidian at the bottom, spikes with layers of crying obsidian and an increased concentration of bedrock

/customitem give doesn’t restrict giving items to other players. As seen on SL/HE this can be an issue.

This should be a separate permission node.

Iron bars don't rotate, as they use facing data similar to mushroom blocks. (MultipleFacing, perhaps)

Currently there's no good way to get a reference to a custom block or item in the code. Might want to do something similar to vanilla's Blocks.

Currently ship rotation does multiple sine/cosine operations per block to calculate the rotated position. This only needs to be done for precise locations like that of the passengers, not blocks.

A system to make developing quests easier

Would be nice if our ship code supported some sort of subcraft system.

It doesn't autocomplete the item or count, and count and player are not optional fields

Players shouldn't be able to breathe in space, and should slowly freeze or burn in extreme environments.

Config loading of custom items, blocks, and multiblocks lack good error handling, and are likely to throw NPE's if the config is formatted incorrectly. Useful error messages would be great.

When moving larger ships they sometimes leave visual artifacts in their wake.
Perhaps sendMultiBlockChange() could help?

No idea what causes this, but ships up to 30k blocks work fine so this isn't high priority.