ajout du kaykit dungeon et des personnages

This commit is contained in:
Philippe Roy 2022-02-24 14:50:19 +01:00
parent 71d868d409
commit 1fe81e217f
4 changed files with 44 additions and 90 deletions

View File

@ -1,92 +1,3 @@
# CodeTower
Code your tower defense
## Getting started
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
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)!
## Add your files
- [ ] [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:
```
cd existing_repo
git remote add origin https://gitlab.com/blender-edutech/codetower.git
git branch -M main
git push -uf origin main
```
## Integrate with your tools
- [ ] [Set up project integrations](https://gitlab.com/blender-edutech/codetower/-/settings/integrations)
## Collaborate with your team
- [ ] [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/)
- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
## 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!). Thank you 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.
**Code your tower defense**

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

View File

@ -0,0 +1,43 @@
# This is an Asset Catalog Definition file for Blender.
#
# Empty lines and lines starting with `#` will be ignored.
# The first non-ignored line should be the version indicator.
# Other lines are of the format "UUID:catalog/path/for/assets:simple catalog name"
VERSION 1
bf031f60-f2d0-4bbb-a67c-e069c583a3f3:Loot:Loot
dd1bd12b-f058-407d-b47a-3d46fd685ef2:Meubles:Meubles
980dcf9d-f1c2-4584-aed1-4e13b52ea58b:Mur bois:Mur bois
c338dd30-3e16-4232-b0e9-bffdfe0c4b59:Murs pierre:Murs pierre
5438a87a-f298-42af-9e4d-c184f2cd1be3:Objets:Objets
4845751c-8bcd-49fa-bada-287693d1c2d0:Personnage Humain:Personnage Humain
14187cd7-2782-42de-bb33-022d11ceee69:Personnage Humain/Barbare:Personnage Humain-Barbare
0b76381c-305f-4de7-ad5f-d583d24b7e49:Personnage Humain/Chevalier:Personnage Humain-Chevalier
ffd434bb-8b2a-4135-b908-0dcbbb78b395:Personnage Humain/Guerrier:Personnage Humain-Guerrier
d08a111a-2d80-485b-ae14-b7e9303654f0:Personnage Humain/Mage:Personnage Humain-Mage
00340e37-eec4-4727-8430-329e192ae418:Personnage Humain/Marchand:Personnage Humain-Marchand
69c6d9bc-734f-4909-a68d-9b13b7540393:Personnage Humain/Marchand/Boucher:Personnage Humain-Marchand-Boucher
1db914f5-3128-4828-8854-2ad03a1f90c6:Personnage Humain/Marchand/Forgeron:Personnage Humain-Marchand-Forgeron
0bf0fbdf-9058-49b3-9599-cf7a238ede93:Personnage Humain/Marchand/Marchande:Personnage Humain-Marchand-Marchande
6e95ae67-8c18-4cfa-b5d6-0a1c5be77ec8:Personnage Humain/Paysan Pecheur:Personnage Humain-Paysan Pecheur
37f7a854-e7f7-41ae-a19d-0e85dbf085d4:Personnage Humain/Pirate:Personnage Humain-Pirate
73a88ae7-2fff-4320-9670-ecc59926f5e4:Personnage Humain/Roi et reine:Personnage Humain-Roi et reine
1ea83ef6-0b1e-43df-8e7f-90d52b375ea0:Personnage Humain/Samourai:Personnage Humain-Samourai
523f417f-0f0d-4afa-8fc6-a2210050028a:Personnage Humain/Viking:Personnage Humain-Viking
990a3231-3267-49de-b6da-0e45910e36cf:Personnage Humain/Voleur:Personnage Humain-Voleur
42233994-a0ef-49a2-96d7-185022ea1050:Personnage Monstre:Personnage Monstre
0e1758ae-131d-47ca-b0d9-9fa4e62a997b:Personnage Monstre/Franck:Personnage Monstre-Franck
44bd13ed-75d3-49a3-a2b7-581bcb5e893e:Personnage Monstre/Yéti:Personnage Monstre-Yéti
719ef62e-a53d-4b21-9f00-afc2cfe215f7:Personnage Orc:Personnage Orc
3623861f-9690-4d24-8501-0266c6b112ef:Personnage Squelette:Personnage Squelette
85de5938-f931-4368-9bbf-fa8b5b5fd14e:Personnage Squelette/Archer:Personnage Squelette-Archer
16e0568a-778e-4d06-b047-40f134db64ef:Personnage Squelette/Guerrier:Personnage Squelette-Guerrier
6294045b-4c15-446d-85af-b85d73b4c67c:Personnage Squelette/King:Personnage Squelette-King
b5f0d3b4-9888-4c93-ad58-12f29479e63b:Personnage Squelette/Mage:Personnage Squelette-Mage
a748b50f-2c19-4d41-909a-c392ad86e43a:Personnage Squelette/Minion:Personnage Squelette-Minion
7c4a3c6d-c638-4e88-ba85-a68b6f21b936:Personnage Squelette/Objets:Personnage Squelette-Objets
ce6887fe-763c-441f-9ab2-edb79b905b6e:Personnage Squelette/Template:Personnage Squelette-Template
6649378e-4c2e-4965-b6bf-a511f7ef54bc:Pièges:Pièges
99175b61-294a-4116-8412-e13997902e12:Portes:Portes
8045b836-2a15-43a1-80ec-acb6a1bda91f:Potions:Potions

Binary file not shown.