+
+It can start after you've done the daily free summon:
+
+
+
+Or, you can also start it from the summon results screen:
+
+
+
+This script won't start on Saint Quartz summon screen as a safeguard, unless you start from the summon results screen.
\ No newline at end of file
diff --git a/wiki/Game-Area-detection.md b/wiki/Game-Area-detection.md
new file mode 100644
index 000000000..32dab4fb4
--- /dev/null
+++ b/wiki/Game-Area-detection.md
@@ -0,0 +1,87 @@
+## How FGO should look with wide-screen update
+
+**JP, CN, KR, NA:** Should fill the entire screen including the notch.
+**TW:** Turn ON `More options/Advanced/Ignore notch calculation` if FGO doesn't leave the notch area black.
+
+Only use Ignore Notch on TW servers, otherwise it has no effect.
+
+There should be no black bars on the screen.
+
+## FGO looks different on my phone
+
+### CASE 1: Borders around FGO are black
+
+On some devices, FGO isn't covering the full screen. This could be because of system settings or because of Android 12 Gesture Navigation.
+
+This is an example which causes problems for FGA:
+
+
+If your device is made by Huawei, LG, Samsung or Xiaomi, you can fix the black bars with System Settings.
+
+Fullscreen settings per manufacturer:
+| Manufacturer | +Guide | +
|---|---|
| Huawei | +
+
|
+
| LG | +
+
|
+
| Samsung | +
+
|
+
| Xiaomi | +
+
|
+
| 
+
+The black border are for gesture navigation.
+
+To get rid of them:
+- Go to `Settings > System > Gestures > System Navigation`.
+- Change to `3-button navigation`.
+
+If that doesn't work, check the [Custom Game Area megathread](https://github.com/Fate-Grand-Automata/FGA/issues/1347).
+
+### CASE 3: Your phone is Android 7 or 8 and has a notch
+
+Notch detection is only possible on Android 9 and above. Either update your phone or find a way to disable notch in your phone's settings.
\ No newline at end of file
diff --git a/wiki/Gift-Box.md b/wiki/Gift-Box.md
new file mode 100644
index 000000000..2b63b6b94
--- /dev/null
+++ b/wiki/Gift-Box.md
@@ -0,0 +1,13 @@
+Gift Box script is just for receiving all Silver and some Gold embers from your present Box.
+
+
+
+___
+"Max Gold ember set size" setting explanation:
+___
+0 = For no gold ember (will only pick silver embers)
+Any number more than zero, will pick Gold embers that are lower or equal to the selected number.
+
+E.g. Based on the images posted above,
+FGA will select Gold (and silver) embers that are equal to or less than 10.
+
diff --git a/wiki/Home.md b/wiki/Home.md
new file mode 100644
index 000000000..1c7568387
--- /dev/null
+++ b/wiki/Home.md
@@ -0,0 +1,16 @@
+Welcome to the Fate-Grand-Automata wiki!
+
+WIKI IS UNDER CONSTRUCTION
+
+#### Things we're absolutely against
+
+This app is only meant to automate repetitive farming battles.
+We don't plan on supporting things that could possibly lead to the creation of bot accounts which need no supervision from users OR things that will be blatant violation of FGO's ToS.
+
+We won't provide support for:
+1. Re-rolling scripts
+2. Automatically logging in at the reset times
+3. Doing the story for you
+4. Messing with the game data or network connections
+5. Playing with screen turned OFF or FGO not in foreground
+6. Playing offline (someone did DM me for this if you're wondering)
\ No newline at end of file
diff --git a/wiki/Privacy-Policy.md b/wiki/Privacy-Policy.md
new file mode 100644
index 000000000..588ff648c
--- /dev/null
+++ b/wiki/Privacy-Policy.md
@@ -0,0 +1,8 @@
+We don't store your data. PERIOD.
+We don't even have a server to store them.
+
+What you do on your phone stays only on your phone or with the cloud backup providers you setup.
+
+The app doesn't have INTERNET permission either.
+
+For the crash reports on Google Play, we only get the Device model and the place in the code the error occurred and no other personal information that could be used to track you.
\ No newline at end of file
diff --git a/wiki/Running-on-Emulators.md b/wiki/Running-on-Emulators.md
new file mode 100644
index 000000000..b12aea531
--- /dev/null
+++ b/wiki/Running-on-Emulators.md
@@ -0,0 +1,32 @@
+## Nox
+
+On Nox, FGA needs Root to work since MediaProjection doesn't seem to work.
+
+- Make sure you're using an **Android 7** instance of Nox.
+ Use [MultiDrive](https://www.bignox.com/blog/how-to-run-multiple-android-instances-with-nox-app-player/) for managing/creating Nox instances.
+- Go to `More options` in the app and turn ON `Use Root for Screenshots`.
+- You also need to enable `Root` from Nox's settings. See [How to root Nox](https://www.bignox.com/blog/how-to-root-nox-app-player/).
+
+## Bluestacks
+
+These settings are tested, some other may also work:
+
+- Install Bluestacks X
+- Start the Multi-Instance Manager as Admin and create a 64-bit Pie instance in the
+- DON'T use root for screenshots
+- Change to High Performance mode:
+ - Open Bluestack's settings
+ - Go to `Performance` tab.
+ - Set `Performancer mode` to `High Performance`
+ - Save settings and Restart Bluestacks.
+- Install FGA from the Play Store, not from Github
+- In order to start the FGA service, rotate the screen to portrait mode first. See [this comment](https://github.com/Fate-Grand-Automata/FGA/issues/967#issuecomment-974652785) for more details.
+
+## MEmu
+
+- Enable Root Mode in the MEmu's `Engine` settings
+- Enable `Use Root for Screenshots` under `More options` -> `Advanced`
+
+## LDPLAYER
+
+- Works without needing any changes to ldplayer settings
\ No newline at end of file
diff --git a/wiki/Troubleshooting.md b/wiki/Troubleshooting.md
new file mode 100644
index 000000000..8f612b03c
--- /dev/null
+++ b/wiki/Troubleshooting.md
@@ -0,0 +1,136 @@
+## Step 1
+Force-stop FGA or restart your phone and see if that works.
+This is a quick-fix for battery optimization issues.
+
+## Other screen recorders
+Don't use other screen recorders with FGA, if you do, force-stop FGA if it doesn't work properly.
+When recording for bug-reports for FGA, use the inbuilt recorder from `More options/Advanced/Record screen`.
+
+## Where's 'Script Mode', Lottery, FP, Support Image Maker?
+The app automatically detects which script can be run on the current screen.
+It will show the relevant option when you click on the PLAY button.
+Support Image Maker shows up as a button on the bottom-left corner of the popup if you click on the PLAY button on the support screen.
+
+## Where's the PLAY button?
+The PLAY button only appears when you switch your phone to horizontal mode, for example when you start FGO. If it still doesn't appear you can try a combination of stopping and starting accessibility and force-closing FGA until it appears.
+
+If the button disappears overnight or when you lock your screen, then battery optimization is at fault. See [#314](https://github.com/Fate-Grand-Automata/FGA/issues/314).
+
+## The PLAY button is in the way when I watch videos
+
+On the FGA notification, press the arrow in the top right, then click Stop.
+If you want to enable the play button again, open the FGA app and start the service
+
+See [Example](https://discord.com/channels/1117873862500163684/1117932403571294228/1119641849032867971)
+
+
+## Having trouble on Emulators?
+
+See [Running on Emulators](Running-on-Emulators)
+
+## Can I run FGA on Apple devices?
+No, the app uses Android-only code. There are some auto-clickers for Apple, but it won't have the intelligence of FGA.
+
+If you still want to use FGA, run it on an emulator or use normal auto-clickers.
+
+Video guide for creating auto-clicker rules with voice controls: https://www.youtube.com/watch?v=JSFiys-j0JM
+
+## Why are newer FGA versions a different app on my phone?
+From now on, the canary APK is published under the package io.github.fate_grand_automata.debug on Github.
+
+This means you'll have to transfer your settings from the old app manually.
+
+The package change was required so I can publish the app as beta-only in the play store. Google doesn't allow me to publish the old app as beta unless I also make it publicly available, which attracts users who refuse to read instructions and leave 1-2 star ratings.
+
+If Google accepts the play store submission for the new app, it will be published with the package io.github.fate_grand_automata (no .debug at the end), which will fix problems with restricted accessibility permissions and will install new builds through the play store.
+
+Installing it through the play store is the only way to use FGA on Android 14 right now, that's the main reason why I had to trigger these major changes.
+
+## I'm trying to use FGA for the first time and I can't click OK after clicking on the PLAY button
+You need to select a battle config on the left to use.
+
+## Where did the "Stop after CE drop" feature go?
+It's now part of the window appearing after pressing the PLAY button in FGO and allows you to set it to stop after X amount of CE drops
+
+## Can I migrate my settings from the Quick icon version to the Buster icon one?
+No, such a functionality was not implemented, but you can do it yourself:
+
+- Install the Buster version from the play store, but keep the Quick version for now
+- Export all battle configs in the Quick app
+- Import them to the Buster app
+- Transfer the rest of the settings manually by checking all settings in the old app and configuring the new app the same way
+
+## Will I get banned for using FGA?
+FGO's Terms of Service contains this line, so everything could be banworthy to them:
+(17) Any other act which Aniplex considers inappropriate.
+
+However, nobody got banned yet for using 3rd party apps. They mainly ban for account trading.
+
+## Do I need root mode for FGA? My phone is not rooted.
+You don't need root, but you can't record videos of FGA in Android 13 without it.
+
+Some emulators need root mode to work and if you have a rooted phone, you should enable root mode because you'll get fewer issues.
+See https://youtu.be/iIjZPjDcZeM for how to record on android 13 and up without root
+
+## Can you use FGA to do story nodes?
+No, because of several reasons:
+- FGO requires you to search for and select the next story node on the map, which requires complicated swiping and tapping. There's no way a computer knows where to find it and how to navigate to it.
+- Starting with Camelot, Story chapters become difficult and can't be beaten with Level 120 Servants consistently. At that point you'll have to look up enemy patterns and build specialized teams.
+- The SKIP button in the top right can't be detected reliably, so FGA will get stuck at dialogue options (top or bottom answer)
+
+# IMPORTANT: Make sure the game looks as FGA wants it to
+
+If you're having trouble, this is mostly related.
+See [Game Area detection](Game-Area-detection)
+
+## Clicking on PLAY doesn't open the popup to start scripts?
+Game booster/Game mode or other app blocking notifications/popups when a game (FGO) is running.
+Turn them OFF. Known to happen on some LG, Samsung and Motorola.
+
+For LG:
+Turn OFF Game Tools since it has the feature to prevent ALERTS from showing up.
+This prevents the dialog which lets you pick AutoSkill config from showing up.
+https://www.lg.com/us/support/help-library/lg-g7-thinq-gaming-tools-CT10000027-20150726480680
+
+On other phones, if you have something like a Game Booster that blocks alerts from other apps when playing a game, turn it OFF.
+Instructions would vary depending on your device, so Google.
+
+## Worked before, doesn't work now
+
+See [#314](https://github.com/Fate-Grand-Automata/FGA/issues/314)
+
+## Keeps asking for Accessibility even after turning it ON
+
+See [#314](https://github.com/Fate-Grand-Automata/FGA/issues/314)
+
+## Uses skills on the wrong servant or doesn't use skills at all
+
+Do you have skill confirmation ON in FGO?
+If so, either turn that OFF or turn ON `More options/Skill confirmation` in FGA.
+
+## Not picking NP/cards on Attack screen OR Got stuck in some info screen
+
+Is it just your phone lagging badly? If so, either get a new phone or try increasing the delays in `More options/Fine-tune`.
+
+## Doesn't work on some screens
+
+1. Check that you're not placing the PLAY button in a weird place.
+ See [Where should I place the PLAY button?](#where-should-i-place-the-play-button)
+
+2. Is there some overlay on your phone/emulator screen that can screw up image matching?
+ For example:
+
+ 
+
+## Where should I place the PLAY button?
+
+Bottom-left corner is ideal. While you can drag the button around to other places, there is a possibility of screwing things up if it comes in the way of image matching.
+
+## Why is FGA opening Servant details at the start of the battle?
+
+That's an intended feature for detecting which face cards belong to which Servant.
+
+Every time a new Servant enters the field, FGA will also open up their details to take a screenshot of their face.
+
+It can be disabled in `More Options`, but you won't be able to use several features relying on face card matching.
+
diff --git a/wiki/_Footer.md b/wiki/_Footer.md
new file mode 100644
index 000000000..967ebbe67
--- /dev/null
+++ b/wiki/_Footer.md
@@ -0,0 +1,5 @@
+[Privacy Policy](Privacy-Policy) - [License](https://github.com/MathewSachin/Fate-Grand-Automata/blob/master/LICENSE) - [Donations](Donations)
+
+Google Play and the Google Play logo are trademarks of Google LLC.
+
+Fate/Grand Order is Copyright Aniplex Inc., DELiGHTWORKS, Aniplex of America and Sony Music Entertainment (Japan) Inc. All images and names owned and trademarked by Aniplex Inc., DELiGHTWORKS, Aniplex of America and Sony Music Entertainment (Japan) Inc. are property of their respective owners.
\ No newline at end of file
diff --git a/wiki/_Sidebar.md b/wiki/_Sidebar.md
new file mode 100644
index 000000000..98d033297
--- /dev/null
+++ b/wiki/_Sidebar.md
@@ -0,0 +1,6 @@
+- [Home](Home)
+- [Troubleshooting](Troubleshooting)
+- [Emulators](Running-on-Emulators)
+- [Scripts](Battle)
+- [Fine tune](Fine-tune)
+- [Donations](Donations)
\ No newline at end of file
diff --git a/wiki/img/StopGifts.png b/wiki/img/StopGifts.png
new file mode 100644
index 000000000..3736f61ea
Binary files /dev/null and b/wiki/img/StopGifts.png differ
diff --git a/wiki/img/fp-kr.png b/wiki/img/fp-kr.png
new file mode 100644
index 000000000..e4e33da5a
Binary files /dev/null and b/wiki/img/fp-kr.png differ
diff --git a/wiki/img/fp-new.jpg b/wiki/img/fp-new.jpg
new file mode 100644
index 000000000..ccac8490a
Binary files /dev/null and b/wiki/img/fp-new.jpg differ
diff --git a/wiki/img/fp.jpg b/wiki/img/fp.jpg
new file mode 100644
index 000000000..125f15afd
Binary files /dev/null and b/wiki/img/fp.jpg differ
diff --git a/wiki/img/free-summon.png b/wiki/img/free-summon.png
new file mode 100644
index 000000000..7a1a3dff2
Binary files /dev/null and b/wiki/img/free-summon.png differ
diff --git a/wiki/img/inside.jpg b/wiki/img/inside.jpg
new file mode 100644
index 000000000..1932180aa
Binary files /dev/null and b/wiki/img/inside.jpg differ
diff --git a/wiki/img/lg-v60.png b/wiki/img/lg-v60.png
new file mode 100644
index 000000000..e59663244
Binary files /dev/null and b/wiki/img/lg-v60.png differ
diff --git a/wiki/img/lottery.png b/wiki/img/lottery.png
new file mode 100644
index 000000000..6652e0aa4
Binary files /dev/null and b/wiki/img/lottery.png differ
diff --git a/wiki/img/notch-8.jpg b/wiki/img/notch-8.jpg
new file mode 100644
index 000000000..338895355
Binary files /dev/null and b/wiki/img/notch-8.jpg differ
diff --git a/wiki/img/outside-notchless.jpg b/wiki/img/outside-notchless.jpg
new file mode 100644
index 000000000..dbe79c6de
Binary files /dev/null and b/wiki/img/outside-notchless.jpg differ
diff --git a/wiki/img/outside.jpg b/wiki/img/outside.jpg
new file mode 100644
index 000000000..6dcc5f72d
Binary files /dev/null and b/wiki/img/outside.jpg differ
diff --git a/wiki/img/overlay.jpg b/wiki/img/overlay.jpg
new file mode 100644
index 000000000..2f82ac044
Binary files /dev/null and b/wiki/img/overlay.jpg differ
diff --git a/wiki/img/pixel-4L.png b/wiki/img/pixel-4L.png
new file mode 100644
index 000000000..d1fda560c
Binary files /dev/null and b/wiki/img/pixel-4L.png differ
diff --git a/wiki/img/samsung-black.jpg b/wiki/img/samsung-black.jpg
new file mode 100644
index 000000000..c3c522c85
Binary files /dev/null and b/wiki/img/samsung-black.jpg differ
diff --git a/wiki/img/xperia-jp.png b/wiki/img/xperia-jp.png
new file mode 100644
index 000000000..f377902c9
Binary files /dev/null and b/wiki/img/xperia-jp.png differ
diff --git a/wiki/scripts/Battle.md b/wiki/scripts/Battle.md
new file mode 100644
index 000000000..8dd5bb705
--- /dev/null
+++ b/wiki/scripts/Battle.md
@@ -0,0 +1,169 @@
+# Introduction
+First and foremost, if you are new to FGA - you have come to the right place.
+
+This battle section is strictly for FGA Battle Configuration.
+
+## Video Introduction
+Please be warned it is a bit outdated, but it should give you a general idea of how to setup FGA for yourself.
+
+ FGA Tutorial - Build 1437
+
+## Battle Configs
+Assuming you have watched the video introduction, this section will go more in-depth tutorial on setting up a battle config.
+
+This in-depth tutorial will cover on creating scripts that will use 'Skills', 'NP', 'Command Cards' and 'Pick Supports'.
+
+### Step 1
+Find the below icon and label and select it.
+
+### Step 2
+Create new script by tapping this icon
+
+### Step 3
+Give your script a name
+
+You can also add a special note (optional) to your script.
+
+The note can be anything like which servants are apart the team you use this script on and so on
+
+### Step 4
+This is where you'll create your commands that FGA will use in battle.
+
+When creating a battle script, you have to remember that servant positions are important.
+
+Each servant in your party will be given a number from 1 to 6, first to last.
+
+
+
+1) For your reference, look at the images below on how to map with FGA.
+
+
+
+
+2. a) When creating scripts 'Skills' and 'NP', you create by basing on your servant positions with each skill is represented by a letter on the command creator.
+
+
+
+
+2. b) Skills that are targetable will use the servants position number to apply the skill to them
+
+
+
+
+3) Like your servants, enemies also have a number and can be targeted too.
+
+
+4) Noble Phantasm (NP) use your servants position.
+
+**Note:** NP can be used in any order.
+Keep in mind, they will be __*used in the order you choose*__ them.
+
+
+
+5. a) Master skills is handled the same way for all 'Mystic Codes' with an exception to the plugsuit.
+
+
+
+
+5. b) The `l` command should not be used when using the plugsuit mystic code. Instead, the plugsuit order change command should be used with
+
+
+7. This step will cover both wave and turn options.
+
+
+A wave or battle that's displayed in the top right corner
+
+
+After settings your skills or NPs for a wave you can switch to the next wave by pressing this "Next Wave" button.
+
+
+Take note of the symbol above. This will indicate that you've skipped to the next wave.
+
+By wave skipping, you're telling FGA that you don't want do anything else until you're on the next wave.
+
+Be warned that if you use the next wave button then any skill you use after that will only activate during the next wave so make sure you check over your script to see if you have made any mistakes.
+___
+
+
+Turns are indicated by this symbol
+
+Turn skipping can't be use to switch to the next wave and vice versa.
+___
+#### Example of FGA Battle Config setup and used
+I recommend opening the video below for reference before continuing this FGA Battle Config guide.
+ FGA Config setup and used video
+
+Example command from video:
+
+## Additional Battle Config (optional)
+1) Materials is use in combination with another setting in the pop up menu that will be covered later for when you want to farm a specific material.
+
+
+
+2) How the spam option works
+[https://github.com/Fate-Grand-Automata/FGA/issues/510](https://github.com/Fate-Grand-Automata/FGA/issues/510 "https://github.com/Fate-Grand-Automata/FGA/issues/510")
+
+3) If you play in multiple servers you can make your scripts only show up only for that specific server in the pop up menu when you're in-game.
+
+
+
+4) You can assign one of the party slots to your scripts so that whenever you start FGA, it will check if your last use party is on the right slot and switch to the right one if it's not.
+
+
+
+5) Card Priority is an optional feature.
+Please note, you do not have to set them everytime you're making a new script.
+
+
+For those uninterested in Card Priority, please search for the text "End Card Priority explanation" (Ctrl + F) and proceed forward.
+
+___
+Card Priority is used to tell FGA how to handle face cards.
+
+With cards in the high will have priority usage over cards on the low end (WB = Weak Buster, WA = Weak Art, RB = Resist Buster, RA = Resist Art, RQ = Resist Quick)
+
+Cards can be changed around for different use case eg:
+- For Buster cards priority: 
+- For charging NP with face cards (Arts cards priority):
+
+- For stars (Quick cards priority):
+
+
+If you want to have different card priority for different waves, then you can add more waves and rearrange the card priority to your liking.
+
+Otherwise, the default will be used throughout all waves, so if you want the same priority, you will only need to just setup the wave 1 priority option OR leave it as it is.
+
+Hence, there is no reason to add more if you're not gonna use it for something different.
+
+___
+
+ - [Servant Priority](https://github.com/Fate-Grand-Automata/FGA/issues/730 "Servant Priority link") is an optional feature under Card Priority.
+
+For more details on how Servant Priority works - https://github.com/Fate-Grand-Automata/FGA/issues/730
+___
+
+
+- Brave Chain
+There are only 3 options for brace chains unless you use Servant Priority.
+
+
+___
+- Rearrange Cards feature
+
+FGA reads face cards from left to right, starting from the right corner to the left.
+
+
+
+Turning on 'Rearrange cards' will flip the order of how FGA reads cards from left > right to right < left
+
+
+
+
+Then, FGA will pick the first card that matches the settings in card priority in that order.
+
+___
+End Card Priority explanation.
+___
+
+ - Support Selection
+
diff --git a/wiki/scripts/Lottery.md b/wiki/scripts/Lottery.md
new file mode 100644
index 000000000..91f6e1a10
--- /dev/null
+++ b/wiki/scripts/Lottery.md
@@ -0,0 +1,11 @@
+> **WARNING:** Better avoid using the Lottery script on Boxes 1-10. If you don't have enough tickets, it can reset the box as soon as you receive the Grand Prize.
+
+To make lottery script work, 2 images are needed per server
+
+1. `lottery.png`
+
+ 
+
+2. `StopGifts.png`
+
+ 
\ No newline at end of file
diff --git a/wiki/scripts/Support-Image-Maker.md b/wiki/scripts/Support-Image-Maker.md
new file mode 100644
index 000000000..697e0f55f
--- /dev/null
+++ b/wiki/scripts/Support-Image-Maker.md
@@ -0,0 +1,60 @@
+## Default Images
+The app comes with images of a few common Support servants and CEs like Waver, Castoria, Lunchtime, etc.
+They should extract automatically when you create your first Battle config.
+But, in case they didn't, you can extract them from 'More options/Storage'.
+
+## Where to put Servant/CE images?
+Assuming `FGA` is the folder you chose for storage.
+
+Under `FGA/support/` folder, put:
+- Servant images in `servant` folder
+- CE images in `ce` folder
+- Friend name images in `friend` folder
+
+The app has some common Servant/CEs inbuilt.
+If you want to use any other preferred servant or CE, you have to create their images using `Support Image Maker` script.
+
+Instead of having to select multiple ascension images for a servant, you can put all the images of a servant in a folder and select the folder in settings.
+
+Here's what a typical directory structure looks like:
+
+```
+FGA/
+-- support/
+-- -- servants/
+-- -- -- ozy4.png
+-- -- -- melt4.png
+-- -- -- Merlin/
+-- -- -- -- merlin1.png
+-- -- -- -- merlin2.png
+-- -- -- -- merlin3.png
+-- -- -- -- merlin4.png
+-- -- -- -- merlin_c.png
+-- -- -- Waver/
+-- -- -- -- waver1.png
+-- -- -- -- waver2.png
+-- -- -- -- waver3.png
+-- -- -- -- waver4.png
+-- -- ce/
+-- -- -- kscope.png
+-- -- -- black_grail.png
+-- -- friend/
+-- -- -- mathew.png
+-- -- -- recon.png
+```
+
+## How to use Support Image Maker?
+
+`Support Image Maker` automatically creates images from the Support screen that can be used with the script.
+You can also use it from the Friend List which is easier since you don't have to keep refreshing till the desired Servant/CE shows up.
+
+> Support Image Maker is calibrated for NA and JP. It might not work correctly on other servers where an older format of support screen is still used.
+
+1. Start the service.
+1. Open F/GO. Go to support selection or friend list screen and ensure that the Servant/CE you want is visible (It is important that the complete Servant + CE region is visible).
+1. Click on PLAY button. A dialog shows up
+2. Click on `Support Image Maker` on the bottom-left corner of the dialog.
+5. Check the images you want to keep. Type a name for the image (NO NEED for file-format like `.png`).
+ For servant images, you can use a folder like: `Nero/asc1`. This will save an image named `asc1.png` in `FGA/support/servant/Nero` folder. By grouping in a folder, you can pick a single entry in settings to match with all ascensions and costumes.
+6. Click on `Done`. The selected images are saved to the correct folders.
+5. You can now use the images in your battle configs.
\ No newline at end of file
diff --git a/wiki/scripts/_Sidebar.md b/wiki/scripts/_Sidebar.md
new file mode 100644
index 000000000..01ade4f64
--- /dev/null
+++ b/wiki/scripts/_Sidebar.md
@@ -0,0 +1,7 @@
+[Home](Home) > Scripts
+
+- [Battle](Battle)
+- [FP Summon](Friend-Point-Summon)
+- [Lottery](Lottery)
+- [Support Image Maker](Support-Image-Maker)
+- [Gift Box](Gift-Box)
\ No newline at end of file