Anon Adventure OP pastebin

==LINKS TO THE BASE GAME AND ALL THE SIDE STUFF WILL FROM NOW ON BE IN THE FIRST POST, ALL ANONS WHO WANT TO ADD SOMETHING SHOULD ANSWER TO THE FIRST POST WHEN PUBLISHING A NEW VERSION==
==HOW TO ADD TO THE NEWEST VERSION WILL BE THE SECOND OR THIRD POST.==

Rules

>We create a video game in RPG Maker VX Ace together with other anons

>You download the game, open it in RPG maker VX Ace and build one location

>Your location can be whatever you want it to be

>If your location has plot material that is unfinished, or a quest that is unfinished, another anon can continue it in his own location

>You cannot tamper with the location of other anons unless you need to change something small so that the character can get into your location or add something really important. Like putting in a teleport for example In other cases just ask

>Fixing grammar mistakes and stuff like that is okay though

>You are free to add characters into inter-dimensional tavern.

>You have to first tell us that you want to create another map before doing it, the anon who says it first wins

>You can generaly change whatever you want or add whatever you want to the game settings unless the thread agreed on something beforehand or if you're overruling a change that another anon made first.

>You have to put the "credits" sequence at the exit of your location with your location added in into the credits. You can change the music if you want

>If you made a new version, make the post in which you're publishing it be a response to the first anchor post in the thread. It makes stuff less confusing.

The basics

>The main character is anon

>Anon's video games were stolen

>His game is about reclaiming his vidya

>The game ends with anon reclaiming his vidya

The rest is completely up to you.

Everything else is in the first/second/third anchor post of the thread.

---FIRST POST---
Current version of the game
https://gitgud.io/dankus10/anons-bizarre-vidya-adventure

RPG Maker VX Ace magnet

magnet:?xt=urn:btih:a05eb6eae518c41363aa7ed55dc1409469bfd1eb&dn=RPG+Maker+VX+ACE+1.01a+%28Already+Cracked%29&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&tr=udp%3A%2F%2Fzer0day.ch%3A1337&tr=udp%3A%2F%2Fopen.demonii.com%3A1337&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%2Fexodus.desync.com%3A6969

Side stuff

One anon made a side-story to the game, you should check it out it's really fun.

https://mega.nz/#!zcQAlZCB!39Wxol9ZrU6S2dGzhAXHCShbNSXqjwKn1iYu0_A9zRg

DLC packs for RPG maker by the courtesy of one of the anons, they're graphic packs, so if you need a sprite or a tileset, look through these before asking

volafile.org/r/HF33Go


---SECOND POST---
==HOW TO INTO GIT FOR BEGINNERS==

Install Git.

https://git-scm.com/book/en/v2/Getting-Started-Installing-Git

Install a GUI. I recommend Tortoise git because it's FOSS, but you can pick something else. You don't need a GUI, but unless you are comfortable in the command line you will want one.

https://git-scm.com/download/gui/linux

https://tortoisegit.org/

At this point I'll mainly be giving you keywords to plug into a search engine along with the name of your software and "git" so you can get specifics. Bold means it's a word that will make the search engine give you back something that's at the very least in the ballpark of what you want. If I don't mention a setting, just leave it at the default.

Figure out how to use your software to clone an existing repository. Pick somewhere on your computer for the directory, and for the URL use the following

https://gitgud.io/dankus10/anons-bizarre-vidya-adventure.git

Hit "ok", "do it", "confirm" or whatever else your software has that creates the local copy. It will now download from the remote repository and give you a local working copy. Those files are on your computer now. You just created a fork! Congratulations.

Whenever the remote repository, aka "the git", is updated you can pull from it. That just means you download any files added, remove any files removed and change and files that were changed. Basically you update your working copy on your computer.

Figure out how to use your software to preform a pull, set the remote you are pulling from to "origin", and set the remote branch you are pulling from to "master".

Confirm, hit OK, or whatever and your local copy is updated. You may notice that this happens really fast. That's because you are only downloading the changes, not the entire file, as was the case with mega.

If for whatever reason your software doesn't have a pull feature, preform a fetch from "origin", and a local merge. This is functionally the same as a pull'.

Using the https link means you will need to create an access token. So lets get into how to do that.

When logged into gitlab/gitgud click the Icon in the upper right-hand corner of the screen. That will bring up your profile. There's a list of links on the left side, and there should be an option called Access Tokens. Click that and it will take you to the Personal Access Token page.

Make sure API is checked and read_user is unchecked. The name can be anything. Set an expiration date more than one month in the future. I have mine set to December 31. Click "Create personal access token" and you will be brought to a new page. Copy the token and save it somewhere safe because you will have to create another one if you forget it.

This token acts as your password. When you push to your remote repository we'll get to that it will ask you for a username and password. Put your username in the username field and put the token in the password field.

Coming up next, how to commit changes and additions, push to the remote repository, and preform a pull request.


---THIRD POST---

Committing save a version of your project that you can go back on later. That's why git is called "version control software". This is great because if your current version is broken beyond repair you can revert to an earlier commit where it wasn't broken and resume from that point onward.

Search for how to commit changes using your software. It's good practice to commit frequently. Firstly you should check for modifications to the files, how exactly that is done differed from one piece of software to the next. Use a search engine for your special case. Some options to note.

Message: Put whatever you want in here. It's most commonly used to say what you did since the last commit, but you can just fill it with keyboard mash or shit-posts. It doesn't matter.

Branch: Sometimes you don't want to commit straight to the master branch. Sometimes you want to play around with your local version in a closed off and safer environment. While branches themselves aren't complex, there's a lot that goes into using them effectively. Here's the official documentation on branches. You can use a search engine to figure out how to do these specific things in your GUI.

https://git-scm.com/book/be/v2/Git-Branching-Basic-Branching-and-Merging

A push pushes your commits to the remote repository. Commits are on only your computer until you push them. A push only pushes commits, and won't save non-committed files or change, so be sure to commit before you push.

Set the local branch to "master" and the remote to "origin". If there's an option for a remote branch, pick "master" as well.

Confirm your choices. You will most likely be prompted for a user-name and password. Put in your gitgud username and the token you created earlier as your password. If you encounter any problems, use a search engine. If that doesn't work, come here and explain what you found and why that didn't work.

A pull request is a message that says "Hey, I finished up here, now put this thing right here into the main branch". For the start, you should have your remote origin master, and the url is the same as before,

https://gitgud.io/dankus10/anons-bizarre-vidya-adventure.git

The "end" is where you want them to stop pulling from. For example if you send a pull request and want to keep working before the pull request is accepted, you set the end to where you know it's stable and then keep working. To figure out what exactly to put there use your specific software's wiki/howto's and a Search Engine.