tavo/lawfulgood
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

test

Browse source
This commit is contained in:
tavo-wasd 2023-10-15 11:29:45 -06:00
parent db6c08e1fe
commit 999f4802e2
3 changed files with 85 additions and 73 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

99
README.md
View file

@ -1,92 +1,45 @@
# Lawful Good
## 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/tavo-wasd/lawfulgood.git
git branch -M main
git push -uf origin main
```
## Integrate with your tools
- [ ] [Set up project integrations](https://gitlab.com/tavo-wasd/lawfulgood/-/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/)
- [ ] [Set auto-merge](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.
## Synopsis
In a dystopian future,
## 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.
Download latest release, or browse releases page. @@@
## 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.
### Development
- [ ] Basic engine
- [ ] Load a scene
- [ ] Map
- [ ] Assets
- [ ] Characters
- [ ] Interactives
- [ ] Dialogues
### Story
- [ ] Setting (where, when)
- [ ] Characters (who)
- [ ] Conflict (why)
- [ ] (Plot)[./doc/story/plot.md] (how)
- [ ] Theme (goal)
## 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.
GPLv3
## 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.
@@@

0
doc/story/characters.md Normal file
View file

59
doc/story/plot.md Normal file
View file

@ -0,0 +1,59 @@
# Structure
- [] Exposition
- [] Rising action
- [] Climax
- [] Falling action
- [] Resolution
## Exposition
MAINCHARACTER is a regular law-abiding citizen living
in a dystopian future, where crime is at an all time
high. Governments control people through propaganda,
threats, power demonstration and market manipulation.
The proletariat while being the largest class, are also
the poorest and last in political relevance.
At the very beginning, MAINCHARACTER is boarding the
train to a marine attraction where he/she was supposed
to meet his/her "TENDR" match. However, after arriving
a few seconds late and watching the train leave, then
getting an unappealing text from the match, decides
to [go anyway]/[go back home].
Before taking an old-school taxi again, calls the new
rocket fueled taxi service. Then, learns one can also
visit other planets or regions within those that one
can't normally visit with public transport services.
In the middle of booking a trip, corrupt police arrests
the taxi driver for illegally transporting people from
the cities to areas "unprotected" by the government.
MAINCHARACTER [tells on]/[saves] the taxi driver, which
causes him to be [arrested]/[set free], and MAINCHARACTER
to be offered a [police academy]/[street fights] pamphlet.
## Rising action
ENEMY helps MAINCHARACTER reach a high position in
the state (police, politics, cybersecurity, health).
But could also make MAINCHARACTER to join an unlawful
group (drug trafficking, fraud, cybercrime). ENEMY is
also a law-abiding citizen, but one who would never
conspire against the state. Eventually, both views
oppose at some degree. This indirectly triggers an
event that could potentially destroy the earth.
In the middle of visiting other planets, MAINCHARACTER
watches a live stream where earth is subject to a
nuclear war and the surface becomes hell in minutes.
As FRIEND who was suspect of being the VILLAIN tries
to escape, MAINCHARACTER watches him die, and the true
VILLAIN, ENEMY is revelaed. ENEMY thinks she is doing
this "sacrifices" for the greater good, MAINCHARACTER
also watches as "the elite" argue in a table game as
if they didn't just commit genocide. Just when MAINCHARACTER
realizes he/she has a gun and could terminate one or many
corrupt leaders, he/she is mugged and the great leaders
pay the bar security to get everyone out since they can't
concentrate.