Skip to content

Commit 8108a17

Browse files
aaronaalmendarezaaronaalmendarez
committed
Add structured voxel architect and planner upgrades
1 parent bf91172 commit 8108a17

28 files changed

+8398
-6336
lines changed

‎.gitattributes‎

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
1-
#
2-
# https://help.github.com/articles/dealing-with-line-endings/
3-
#
4-
# Linux start script should use lf
5-
/gradlew text eol=lf
6-
7-
# These are Windows script files and should use crlf
8-
*.bat text eol=crlf
9-
1+
#
2+
# https://help.github.com/articles/dealing-with-line-endings/
3+
#
4+
# Linux start script should use lf
5+
/gradlew text eol=lf
6+
7+
# These are Windows script files and should use crlf
8+
*.bat text eol=crlf
9+

‎.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 32 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -1,32 +1,32 @@
1-
---
2-
name: Bug Report
3-
about: Create a report to help us improve.
4-
title: "[BUG] "
5-
labels: bug
6-
assignees: ''
7-
8-
---
9-
10-
**Describe the bug**
11-
A clear and concise description of what the bug is.
12-
13-
**To Reproduce**
14-
Steps to reproduce the behavior:
15-
1. Go to '...'
16-
2. Click on '....'
17-
3. See error
18-
19-
**Expected behavior**
20-
A clear and concise description of what you expected to happen.
21-
22-
**Screenshots/Logs**
23-
If applicable, add screenshots or logs to help explain your problem.
24-
25-
**Environment (please complete the following information):**
26-
- Minecraft Version: [e.g. 1.21.1]
27-
- Fabric Loader Version: [e.g. 0.18.4]
28-
- Mod Version: [e.g. 1.0.0]
29-
- Other mods installed: [e.g. Sodium, Iris]
30-
31-
**Additional context**
32-
Add any other context about the problem here.
1+
---
2+
name: Bug Report
3+
about: Create a report to help us improve.
4+
title: "[BUG] "
5+
labels: bug
6+
assignees: ''
7+
8+
---
9+
10+
**Describe the bug**
11+
A clear and concise description of what the bug is.
12+
13+
**To Reproduce**
14+
Steps to reproduce the behavior:
15+
1. Go to '...'
16+
2. Click on '....'
17+
3. See error
18+
19+
**Expected behavior**
20+
A clear and concise description of what you expected to happen.
21+
22+
**Screenshots/Logs**
23+
If applicable, add screenshots or logs to help explain your problem.
24+
25+
**Environment (please complete the following information):**
26+
- Minecraft Version: [e.g. 1.21.1]
27+
- Fabric Loader Version: [e.g. 0.18.4]
28+
- Mod Version: [e.g. 1.0.0]
29+
- Other mods installed: [e.g. Sodium, Iris]
30+
31+
**Additional context**
32+
Add any other context about the problem here.

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,20 @@
1-
---
2-
name: Feature Request
3-
about: Suggest an idea for this project.
4-
title: "[FEATURE] "
5-
labels: enhancement
6-
assignees: ''
7-
8-
---
9-
10-
**Is your feature request related to a problem? Please describe.**
11-
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12-
13-
**Describe the solution you'd like**
14-
A clear and concise description of what you want to happen.
15-
16-
**Describe alternatives you've considered**
17-
A clear and concise description of any alternative solutions or features you've considered.
18-
19-
**Additional context**
20-
Add any other context or screenshots about the feature request here.
1+
---
2+
name: Feature Request
3+
about: Suggest an idea for this project.
4+
title: "[FEATURE] "
5+
labels: enhancement
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
13+
**Describe the solution you'd like**
14+
A clear and concise description of what you want to happen.
15+
16+
**Describe alternatives you've considered**
17+
A clear and concise description of any alternative solutions or features you've considered.
18+
19+
**Additional context**
20+
Add any other context or screenshots about the feature request here.

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,19 @@
1-
## Description
2-
Briefly describe the changes introduced by this Pull Request.
3-
4-
## Related Issue
5-
Fixes # (issue)
6-
7-
## Type of Change
8-
- [ ] Bug fix (non-breaking change which fixes an issue)
9-
- [ ] New feature (non-breaking change which adds functionality)
10-
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
11-
- [ ] Documentation update
12-
13-
## Checklist:
14-
- [ ] My code follows the style guidelines of this project.
15-
- [ ] I have performed a self-review of my own code.
16-
- [ ] I have commented my code, particularly in hard-to-understand areas.
17-
- [ ] I have made corresponding changes to the documentation.
18-
- [ ] My changes generate no new warnings.
19-
- [ ] New and existing tests pass locally with my changes.
1+
## Description
2+
Briefly describe the changes introduced by this Pull Request.
3+
4+
## Related Issue
5+
Fixes # (issue)
6+
7+
## Type of Change
8+
- [ ] Bug fix (non-breaking change which fixes an issue)
9+
- [ ] New feature (non-breaking change which adds functionality)
10+
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
11+
- [ ] Documentation update
12+
13+
## Checklist:
14+
- [ ] My code follows the style guidelines of this project.
15+
- [ ] I have performed a self-review of my own code.
16+
- [ ] I have commented my code, particularly in hard-to-understand areas.
17+
- [ ] I have made corresponding changes to the documentation.
18+
- [ ] My changes generate no new warnings.
19+
- [ ] New and existing tests pass locally with my changes.

‎.github/workflows/build.yml‎

Lines changed: 29 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -1,30 +1,30 @@
1-
# Automatically build the project and run any configured tests for every push
2-
# and submitted pull request. This can help catch issues that only occur on
3-
# certain platforms or Java versions, and provides a first line of defence
4-
# against bad commits.
5-
6-
name: build
7-
on: [pull_request, push]
8-
9-
jobs:
10-
build:
11-
runs-on: ubuntu-24.04
12-
steps:
13-
- name: checkout repository
14-
uses: actions/checkout@v4
15-
- name: validate gradle wrapper
16-
uses: gradle/actions/wrapper-validation@v4
17-
- name: setup jdk
18-
uses: actions/setup-java@v4
19-
with:
20-
java-version: '21'
21-
distribution: 'microsoft'
22-
- name: make gradle wrapper executable
23-
run: chmod +x ./gradlew
24-
- name: build
25-
run: ./gradlew build
26-
- name: capture build artifacts
27-
uses: actions/upload-artifact@v4
28-
with:
29-
name: Artifacts
1+
# Automatically build the project and run any configured tests for every push
2+
# and submitted pull request. This can help catch issues that only occur on
3+
# certain platforms or Java versions, and provides a first line of defence
4+
# against bad commits.
5+
6+
name: build
7+
on: [pull_request, push]
8+
9+
jobs:
10+
build:
11+
runs-on: ubuntu-24.04
12+
steps:
13+
- name: checkout repository
14+
uses: actions/checkout@v4
15+
- name: validate gradle wrapper
16+
uses: gradle/actions/wrapper-validation@v4
17+
- name: setup jdk
18+
uses: actions/setup-java@v4
19+
with:
20+
java-version: '21'
21+
distribution: 'microsoft'
22+
- name: make gradle wrapper executable
23+
run: chmod +x ./gradlew
24+
- name: build
25+
run: ./gradlew build
26+
- name: capture build artifacts
27+
uses: actions/upload-artifact@v4
28+
with:
29+
name: Artifacts
3030
path: build/libs/

‎.gitignore‎

Lines changed: 22 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,22 @@
1-
# Build output
2-
build/
3-
run/
4-
logs/
5-
*.log
6-
7-
# Gradle
8-
.gradle/
9-
10-
# IDE
11-
.idea/
12-
.vscode/
13-
*.iml
14-
15-
# OS
16-
.DS_Store
17-
Thumbs.db
18-
19-
# Local secrets
20-
.env
21-
*.key
22-
1+
# Build output
2+
build/
3+
run/
4+
logs/
5+
*.log
6+
7+
# Gradle
8+
.gradle/
9+
10+
# IDE
11+
.idea/
12+
.vscode/
13+
*.iml
14+
15+
# OS
16+
.DS_Store
17+
Thumbs.db
18+
19+
# Local secrets
20+
.env
21+
*.key
22+

‎CODE_OF_CONDUCT.md‎

Lines changed: 43 additions & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -1,43 +1,43 @@
1-
# Contributor Covenant Code of Conduct
2-
3-
## Our Pledge
4-
5-
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
6-
7-
## Our Standards
8-
9-
Examples of behavior that contributes to creating a positive environment include:
10-
11-
* Using welcoming and inclusive language
12-
* Being respectful of differing viewpoints and experiences
13-
* Gracefully accepting constructive criticism
14-
* Focusing on what is best for the community
15-
* Showing empathy towards other community members
16-
17-
Examples of unacceptable behavior by participants include:
18-
19-
* The use of sexualized language or imagery and unwelcome sexual attention or advances
20-
* Trolling, insulting/derogatory comments, and personal or political attacks
21-
* Public or private harassment
22-
* Publishing others' private information, such as a physical or electronic address, without explicit permission
23-
* Other conduct which could reasonably be considered inappropriate in a professional setting
24-
25-
## Our Responsibilities
26-
27-
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
28-
29-
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
30-
31-
## Scope
32-
33-
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
34-
35-
## Enforcement
36-
37-
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
38-
39-
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
40-
41-
## Attribution
42-
43-
This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
6+
7+
## Our Standards
8+
9+
Examples of behavior that contributes to creating a positive environment include:
10+
11+
* Using welcoming and inclusive language
12+
* Being respectful of differing viewpoints and experiences
13+
* Gracefully accepting constructive criticism
14+
* Focusing on what is best for the community
15+
* Showing empathy towards other community members
16+
17+
Examples of unacceptable behavior by participants include:
18+
19+
* The use of sexualized language or imagery and unwelcome sexual attention or advances
20+
* Trolling, insulting/derogatory comments, and personal or political attacks
21+
* Public or private harassment
22+
* Publishing others' private information, such as a physical or electronic address, without explicit permission
23+
* Other conduct which could reasonably be considered inappropriate in a professional setting
24+
25+
## Our Responsibilities
26+
27+
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
28+
29+
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
30+
31+
## Scope
32+
33+
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
34+
35+
## Enforcement
36+
37+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
38+
39+
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
40+
41+
## Attribution
42+
43+
This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

0 commit comments

Comments
 (0)