From fa312010abd7c4337a19e05aaebcf696cba52621 Mon Sep 17 00:00:00 2001 From: Tim Pfeilschifter <tim.pfeilschifter@br.de> Date: Tue, 9 Jul 2024 11:40:49 +0000 Subject: [PATCH] Update file README.md --- README.md | 110 +++++++++++++++--------------------------------------- 1 file changed, 30 insertions(+), 80 deletions(-) diff --git a/README.md b/README.md index 20eb924..325fbb1 100644 --- a/README.md +++ b/README.md @@ -1,93 +1,43 @@ -# Alpcraft +Voraussetzungen: +- Du besitzt Minecraft in der Java Edition +- Du hast Minecraft Forge installiert +Solltest du diese beiden Voraussetzungen erfüllen, kannst du direkt zum Punkt „Alpcraft installieren“ springen. -## Getting started +Minecraft installieren: -To make it easy for you to get started with GitLab, here's a list of recommended next steps. +- Du kannst, wenn du Minecraft in der Java Edition besitzt das Spiel je nach Betriebssystem hier herunterladen (https://www.minecraft.net/de-de/download) +- Forge installieren: Du kannst Forge hier (http://files.minecraftforge.net/) herunterladen. +- Beachte, dass Minecraft, Forge und die Alpcraft Mod alle für dieselbe Version ausgelegt sein sollten +- Öffne Minecraft und wähle das Forge Profil aus -Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! +Alpcraft installieren : -## Add your files +1. Du kannst Alpcraft hier (https://gitlab.ard.de/minecraft/alpcraft) herunterladen +2. Speichere die Datei im Mods Ordner von Minecraft Forge +3. Wähle hierfür im Minecraft Hauptmenü den .Mods Ordner und drücke danach auf Mods-Ordner öffnen -- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files -- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: +- So findest du den Ordner bei Windows auch direkt + - Drücke gleichzeitig die Windows und „R“ Taste + - Gebe %appdata% ein und drücke enter + - Hier solltest du den Ordner .minecraft mit dem Unterordner mods finden + - Installiere Forge falls der Ordner nicht existierte + - Lege die Alpcraft.jar Datei im Mods Ordner ab -``` -cd existing_repo -git remote add origin https://gitlab.ard.de/minecraft/alpcraft.git -git branch -M main -git push -uf origin main -``` +- So findest du den Ordner bei MacOS auch direkt + - Klick auf den Desktop und drücke die Tastenkombination „Command + Shift + G“ + - Gebe ~/Library ein und drücke enter + - Öffne den Ordner „Application Support.“ Darin befindet sich der Ordner Minecraft mit dem Unterordner Mods + - Installiere Forge falls der Ordner nicht existierte + - Lege die Alpcraft Datei im Mods Ordner ab -## Integrate with your tools +4. Starte Minecraft neu nachdem du die Alpcraft Datei im Mods Ordner gespeichert hast -- [ ] [Set up project integrations](https://gitlab.ard.de/minecraft/alpcraft/-/settings/integrations) +5. Öffne Minecraft und wähle das Forge Profil aus -## Collaborate with your team +6. Erstelle eine neue Welt und wähle den Unterpunkt Datenpakete des Reiters „Mehr“ aus -- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) -- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) -- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) -- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) -- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) +7. Vergewissere dich, dass sich Alpcraft in der Spalte „Ausgewählt“ befindet -## Test and Deploy - -Use the built-in continuous integration in GitLab. - -- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) -- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) -- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) -- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) -- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) - -*** - -# Editing this README - -When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template. - -## Suggestions for a good README - -Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. - -## Name -Choose a self-explaining name for your project. - -## Description -Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. - -## Badges -On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. - -## Visuals -Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. - -## Installation -Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. - -## Usage -Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. - -## Support -Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. - -## Roadmap -If you have ideas for releases in the future, it is a good idea to list them in the README. - -## Contributing -State if you are open to contributions and what your requirements are for accepting them. - -For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. - -You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. - -## Authors and acknowledgment -Show your appreciation to those who have contributed to the project. - -## License -For open source projects, say how it is licensed. - -## Project status -If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. +8. Starte die Welt und beginne dein neues Abenteuer mit Alpcraft. \ No newline at end of file -- GitLab