VoxelSniper: The journey through the Fabric of time. Part two: Implementing the project

KevinDaGame / VoxelSniper-Reimagined

The premier long-distance brush editor for Minecraft, reimagined!

GNU Lesser General Public License v2.1

62 stars 6 forks source link

VoxelSniper: The journey through the Fabric of time. Part two: Implementing the project #219

Closed KevinDaGame closed 1 year ago

KevinDaGame commented 1 year ago

What type of PR is this? (check all applicable)

[x] Feature
[ ] Refactor
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update

Description

Implement the fabric (empty) project

QA Instructions, Screenshots, Recordings

https://www.youtube.com/watch?v=YPN0qhSyWy8

Added/updated tests?

[ ] Yes
[ ] No, and this is why: please replace this line with details on why tests have not been included
[ ] I need help with writing tests
[ ] Not needed

[optional] What gif best describes this PR or how it makes you feel?

alt_text

KevinDaGame commented 1 year ago

maybe it would be good to put this on a separate branch for now, similar to what we did with Forge?

I disagree. I want to take a different approach than we did with forge. I found it very difficult to work on, because the branches deviated so much. In addition, keeping those seperate was needed because we did the major refactor. That shouldn't be necessary this time.

While our Fabric version is in alpha, we won't guarantee stability at all, so it's use at your own risk. We will however enforce master to compile, so our releases should stay stable.

Lennart99 commented 1 year ago

maybe it would be good to put this on a separate branch for now, similar to what we did with Forge?

I disagree. I want to take a different approach than we did with forge. I found it very difficult to work on, because the branches deviated so much. In addition, keeping those seperate was needed because we did the major refactor. That shouldn't be necessary this time.

While our Fabric version is in alpha, we won't guarantee stability at all, so it's use at your own risk. We will however enforce master to compile, so our releases should stay stable.

Sure, both is fine I guess.