Skip to content

README #2 #602

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.

Sign up for GitHub

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

Merged
oAnshull merged 2 commits into from
Nov 12, 2025
Merged

README #2 #602

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6971a53
README #2
TheBarii Nov 10, 2025
7c64ddd
Update README with pull request and developer info
TheBarii Nov 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,10 @@ Our current open-source model works as follows. Key portions of Flarial that we
Alongside this, the current model contains delayed releases for version updates. For instance, if the current Minecraft version is 1.21.200, Flarial's signatures and offsets on this repository will stay on the previous version of Minecraft.

Furthermore, as an open-source contributor, you can make pull requests to Flarial with your feature of choice.
**However**, it is highly encouraged to **apply** to be part of the development team, for the moment, open a ticket in our discord.
Two official developers will review your pull request and merge as seen fit. Don't worry, your features will be accepted into the closed source repository and hence the official distribution channels as seen fit.

**However**, it is highly encouraged to **apply** to be part of the development team, for the moment, open a ticket in our discord. We cannot guarantee you an official position at the moment, as obviously, we are in the process of many changes.
Copy link

Copilot AI Nov 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nitpick] The phrase 'as obviously' is awkward and informal for documentation. Consider rephrasing to 'We cannot guarantee you an official position at the moment, as we are currently undergoing many changes.' This improves clarity and maintains a more professional tone.

Suggested change
**However**, it is highly encouraged to **apply** to be part of the development team, for the moment, open a ticket in our discord. We cannot guarantee you an official position at the moment, as obviously, we are in the process of many changes.
**However**, it is highly encouraged to **apply** to be part of the development team; for the moment, open a ticket in our Discord. We cannot guarantee you an official position at the moment, as we are currently undergoing many changes.

Copilot uses AI. Check for mistakes.
Everything mentioned here can and will change in the future.
Copy link

Copilot AI Nov 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nitpick] The statement 'Everything mentioned here' is overly broad and vague. Consider being more specific, such as 'The contribution process and team application requirements mentioned above may change in the future.' This provides clearer context about what might change.

Suggested change
Everything mentioned here can and will change in the future.
The contribution process and team application requirements described above may change in the future as the project evolves.

Copilot uses AI. Check for mistakes.

## Supported Platforms

Expand Down