Installing and updating the Ashita v4 beta using Git is considered more advanced. If you are not familiar with or comfortable with using Git, you can instead install (or update) using the latest repository snapshot.
See Install via Zip for more information.
Currently, the recommended method of installing the Ashita v4 beta is by using a Git client. At this time, the latest beta release is maintained in a single GitHub repository which makes it easy to find the main project files and first-party addons/plugins in one place. By using a Git client, you can easily keep your installation up to date as well by pulling the latest changes. You can either use Git via the command line or install your personal favorite Git client or shell integration. There is no ‘best’ client or means of using Git, that is entirely personal choice on which you prefer to use.
Please note: When using a Git client to install and update, it is wise to not make use of any of the default included configuration files to avoid overwriting them when updating!
Some recommended free solutions are:
When picking a folder to install Ashita to, it is important that you DO NOT break the following guidelines:
Ashita should NOT be installed into a system protected folder.
This means it should not be put into folders (or folders within) such as:C:\Program Files (x86)\
, C:\Program Files\
, C:\Windows\
Ashita should NOT be installed into the game client folder!
You should never install Ashita into the game client folder for safety reasons.
It should be in its own separate folder entirely!
A recommended and safe installation location would be something such as:
C:\Ashita\
C:\Users\Your_Username_Here\Desktop\Ashita\
Z:\Some\Other\Folder\Ashita\
Please note, because there are many different Git clients available, it is not possible for us to write a full guide for each one. Instead, this guide will demonstrate how to install using three different methods. Two UI based clients and the command line.
If you install Git for Windows
, it is important to choose Checkout as-is, commit as-is
when installing for the line endings
configurations. This will avoid issues when any future usage of Git on your system with Ashita and other projects. The other configuration options while installing can all be left default unless you wish to change them.
GitHub Desktop
GitHub Desktop
client. Once installed, launch it and either sign in with your existing GitHub account, or skip the sign in step. (Note: You do not need to sign in to clone the Ashita beta repository, so you can skip the sign in step if you do not want to or do not wish to create an account with GitHub.)File
then Clone Repository...
URL
tab at the top, then enter the repository URL: https://github.com/AshitaXI/Ashita-v4beta.git
For the local path, ensure you follow the guidelines above and place Ashita into a valid path. For example, C:\Ashita\
Clone
.If everything was successful, you’re done and should have Ashita now installed to the selected folder!
TortoiseGit
Git for Windows
and TortoiseGit
. Follow the various prompts to fully install both tools.TortoiseGit
is a shell extension.)C:\
Git Clone..
(Be sure you are not right-clicking on a folder!)https://github.com/AshitaXI/Ashita-v4beta.git
For the Directory
ensure the path is correct. In this example, it should be C:\Ashita-v4beta
by default, but you can edit this to be C:\Ashita
instead.OK
to clone.If everything was successful, a second window should show with some information about the clone and that it was successful. If so, then you’re done and should have Ashita now installed to the selected folder!
Git Command Line
Git for Windows
. Follow the various prompts to fully install.cd C:\
git clone https://github.com/AshitaXI/Ashita-v4beta.git Ashita
If everything was successful, you’re done and should have Ashita now installed to the selected folder!
One of the advantages of using a Git client to install the Ashita v4 beta is that you can easilly pull updates with little effort. In order to do this, you should avoid altering/editing any included file with the beta installation otherwise you may cause merge conflicts when pulling the latest update.
Things to avoid editing and using are:
Assuming you have not made any edits to files that will cause conflicts, you can update using the below methods based on how you installed or use which ever client you prefer.
GitHub Desktop
GitHub Desktop
.Current Repository
block and make sure your Ashita v4 beta repo is selected.Repository
from the menu and choose Pull
. (Or click the Fetch origin
button.)Your installation should now be up to date if there were no conflicts.
TortoiseGit
Git Sync...
from the menu.Pull
button.Your installation should now be up to date if there were no conflicts.
Git Command Line
cd C:\Ashita\
git pull
Your installation should now be up to date if there were no conflicts.