.gitignore

@@ -0,0 +1,84 @@
+# Ignore all files
+*.*
+
+# File Types
+!*.mps
+!*.dat
+!*.json
+!*.txt
+!*.project
+!*.js
+!*.zip
+!*.7z
+!*.csv
+!*.ain
+!*.fnl
+!*.ks
+!*.tjs
+!*.yaml
+!*.rb
+!*.rvdata2
+
+# Other Needed Files
+!.gitignore
+!README.md
+!patch-config.txt
+!GameUpdate*
+!patch.bat
+!Game.dat
+
+# Ignore
+previous_patch_sha.txt
+kabe3_save.dat
+kabe3_system.dat
+psbpack.dat
+Save*
+
+# Images
+!1P_erosute_haikei.png
+!1P_erosute_serihu1_019.png
+!1P_erosute_serihu2_2039.png
+!1P_erosute_serihu3_4059.png
+!1P_erosute_serihu4_6079.png
+!1P_erosute_serihu5_8099.png
+!1P_erosute_serihu6_100.png
+!2P_zukan1_kaihou.png
+!2P_zukan1_kaihou_serihu1.png
+!2P_zukan1_kaihou_serihu2.png
+!2P_zukan1_kaihou_serihu3.png
+!2P_zukan1_mikaihou.png
+!2P_zukan2_kaihou.png
+!2P_zukan2_kaihou_serihu1.png
+!2P_zukan2_kaihou_serihu2.png
+!2P_zukan2_kaihou_serihu3.png
+!2P_zukan2_mikaihou.png
+!2P_zukan3_kaihou.png
+!2P_zukan3_kaihou_serihu1.png
+!2P_zukan3_kaihou_serihu2.png
+!2P_zukan3_kaihou_serihu3.png
+!2P_zukan3_mikaihou.png
+!2P_zukan4_kaihou.png
+!2P_zukan4_kaihou_serihu1.png
+!2P_zukan4_kaihou_serihu2.png
+!2P_zukan4_kaihou_serihu3.png
+!2P_zukan4_mikaihou.png
+!2P_zukan5_kaihou.png
+!2P_zukan5_kaihou_serihu1.png
+!2P_zukan5_kaihou_serihu2.png
+!2P_zukan5_kaihou_serihu3.png
+!2P_zukan5_mikaihou.png
+!2P_zukan6_kaihou.png
+!2P_zukan6_kaihou_serihu1.png
+!2P_zukan6_kaihou_serihu2.png
+!2P_zukan6_kaihou_serihu3.png
+!2P_zukan6_mikaihou.png
+!2P_zukan7_kaihou.png
+!2P_zukan7_kaihou_serihu1.png
+!2P_zukan7_kaihou_serihu2.png
+!2P_zukan7_kaihou_serihu3.png
+!2P_zukan7_mikaihou.png
+!70_ui_左枠.png
+!71_ui_右枠.png
+!71_ui_右枠_バステ.png
+!mapUI_test.png
+!71_basute_sitazi.png

GAMEUPDATE.bat

@@ -0,0 +1,14 @@
+@echo off
+setlocal
+
+REM Copy GAMEUPDATE.bat to a new file
+copy patch.bat patch2.bat
+
+REM Run the new file
+call patch2.bat
+
+REM Delete the new file
+del patch2.bat
+
+endlocal
+@echo on

GameUpdate_linux.sh

@@ -0,0 +1,75 @@
+#!/bin/bash
+
+function check_dependency() {
+  if ! command -v "$1" &> /dev/null; then
+    echo "Error: '$1' is not installed. Please install it."
+    exit 1
+  fi
+}
+
+# Check for jq and unzip
+check_dependency jq
+check_dependency unzip
+
+CONFIG_FILE="patch-config.txt"
+
+# Check if CONFIG_FILE exists
+if [ ! -f "$CONFIG_FILE" ]; then
+    echo "Config file '$CONFIG_FILE' not found! Assuming no patching needed."
+    exit 0
+fi
+
+# Convert line endings to Unix format
+sed -i 's/\r$//' "$CONFIG_FILE"
+
+# Read configuration from file
+source "$CONFIG_FILE"
+
+# Get the latest hash
+echo "Getting latest commit SHA hash"
+latest_patch_sha=$(curl -s "https://gitgud.io/api/v4/projects/$username%2F$repo/repository/branches/$branch" | jq -r '.commit.id')
+
+function download_extract() {
+    # Download zip file
+    echo "Downloading latest patch..."
+    curl -sL "https://gitgud.io/$username/$repo/-/archive/$branch/$repo-$branch.zip" -o repo.zip
+
+    # Extract contents, overwriting conflicts
+    echo "Extracting..."
+    unzip -qo repo.zip
+    echo "Applying patch..."
+    if [ -d "$repo-$branch/"www ]; then
+        cp -r "$repo-$branch/"* .
+        jq --arg repo "$repo" 'if (.name | test("^[[:space:]]*$")) then .name = $repo else . end' package.json > package.json
+    else
+        cp -r "$repo-$branch/"* ./www
+    fi
+
+    echo "Cleaning up..."
+    rm repo.zip
+    rm -rf "$repo-$branch"
+    rm latest_patch_sha.txt
+
+    # Store latest SHA for next check
+    echo "$latest_patch_sha" > previous_patch_sha.txt
+}
+
+# Check if previous_patch_sha.txt exists
+if [ ! -f previous_patch_sha.txt ]; then
+    echo "Previous SHA hash not found!"
+    echo "Assuming first time patching..."
+    download_extract
+else
+    # Read the stored SHA from previous check
+    previous_patch_sha=$(<previous_patch_sha.txt)
+
+    # Compare trimmed SHAs
+    if [ "$latest_patch_sha" != "$previous_patch_sha" ]; then
+        echo "Update found! Patching..."
+        download_extract
+    else
+        echo "Patch is up to date."
+    fi
+fi
+
+exit 0

README.md

@@ -1,93 +1,58 @@
-# Renalith Saga
+# Apply Patch
+1. Click Code
+2. Click Download ZIP
+3. Extract to game folder and Replace All.
+4. Download and extract images to game folder https://pixeldrain.com/u/JBkrJe9Z
 
+## Future Patching
+1. Run GAMEUPDATE.bat to auto patch.
 
+# Troubleshooting
+**GAMEUPDATE.bat doesn't update and closes immediately**
+1. Make sure your path doesn't contain any Japanese characters or lots of whitespace.
+2. Make sure you actually have permissions in the folder
 
-## Getting started
+# Edit/Contribute
+TLDR 3 steps.
 
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+    Fork the repository.
+    Make the changes.
+    Submit a pull request to the project owner.
 
-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)!
+If everything looks good and doesn't break things I'll merge it in.
 
-## Add your files
+Longer Version:
 
-- [ ] [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:
+Things that are needed:
+* [VSCode](https://code.visualstudio.com/) Make sure you check all the boxes for context menus. ![image](https://github.com/DazedMTL/Dungeon-With-Girl/assets/96628874/7a84b624-32fe-4845-a0f6-2b9f39795070)
+* The Game
+* [Git](https://git-scm.com/downloads) (Use the default for everything. Just keep clicking Next)
+* Motivation to learn
 
-```
-cd existing_repo
-git remote add origin https://gitgud.io/dazed-translations/renalith-saga.git
-git branch -M master
-git push -uf origin master
-```
+Installation:
+1. Fork the repo using the fork button at the top. Click Code > HTTPS > Copy URL.
+2. Right click on the game folder and click 'Open with VSCode' (Shift+Right_Click if you are on Windows 11)
+3. Click on the Source Control Button and click initialize repository.
 
-## Integrate with your tools
+![image](https://github.com/DazedMTL/Dungeon-With-Girl/assets/96628874/61e818e6-11f9-450d-9d7d-263d109dbf56)
 
-- [ ] [Set up project integrations](https://gitgud.io/dazed-translations/renalith-saga/-/settings/integrations)
+4. At the top click on Terminal > New Terminal. Enter the following: `git clone [URL_YOU_COPIED_ABOVE]`.
+5. Copy the contents of the new folder created with git clone into the game folder and replace all.
+6. Your source control menu should be good to go and look like this.
 
-## Collaborate with your team
+![image](https://github.com/DazedMTL/Dungeon-With-Girl/assets/96628874/c19787a0-172d-4a08-a37a-e3b56e70e86a)
 
-- [ ] [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)
+Now you are all setup, all you need to do is play the game and look for any changes that need to be made. Stuff like spelling errors, wrong names, inconsistencies, spacing issues, etc.
 
-## Test and Deploy
+7. Use the FIND functionality to search for what you are trying to fix. For example if a character's name is wrong, type that into the search menu and start looking, then make the change. Try not to mess with any scripts or variables you might see.
 
-Use the built-in continuous integration in GitLab.
+![image](https://github.com/DazedMTL/Dungeon-With-Girl/assets/96628874/589eccaf-7f86-43f7-a917-7e6e477b381a)
 
-- [ ] [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)
+8. After you are satisfied with your changes it's time to put in a PR. Go to source control to see all your changes. Add a message and click the `Commit` button to save them all.
 
-***
+![image](https://github.com/DazedMTL/Dungeon-With-Girl/assets/96628874/a9a8973b-bc01-4184-bea9-63a925d961a2)
 
-# Editing this README
+8. Click Sync to push your changes to your fork. Now all that's left is to put in a pull request.
+9. Go to Pull Requests > New Pull Requests. Look at the arrow, your fork should be pointing to the original repo (mine). Add in details on what you fixed and Submit. If everything looks good I'll merge it in and you would have successfully contributed.
 
-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!). Thanks 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.
+Got questions? Just shoot me a message, more than happy to walk you through any of the tools.

patch-config.txt

@@ -0,0 +1,3 @@
+username=dazed-translations
+repo=renalith-saga
+branch=main

patch.bat

@@ -0,0 +1,105 @@
+@echo off
+setlocal EnableExtensions EnableDelayedExpansion
+
+echo Checking for pwsh...
+set _my_shell=pwsh
+
+REM Check if pwsh.exe exists
+where /q !_my_shell!
+if !errorlevel! neq 0 (
+  echo pwsh not found. Falling back to powershell...
+  REM If pwsh is not found, set to powershell
+  set _my_shell=powershell
+
+  REM Check if powershell.exe exists
+  echo Checking for powershell...
+  where /q !_my_shell!
+  if !errorlevel! neq 0 (
+    echo.Error: Powershell not found!
+    pause
+    exit /B 1
+  ) else (
+    echo powershell found.
+  )
+) else (
+  echo pwsh found.
+)
+
+echo Using !_my_shell! for script execution.
+
+REM Check if patch-config.txt exists
+if not exist patch-config.txt (
+    echo "Config file (patch-config.txt) not found! Assuming no patching needed."
+    pause
+    exit /b
+)
+
+REM Read configuration from file
+for /f "tokens=1,2 delims==" %%a in (patch-config.txt) do (
+    if "%%a"=="username" set "username=%%b"
+    if "%%a"=="repo" set "repo=%%b"
+    if "%%a"=="branch" set "branch=%%b"
+)
+
+REM Get the latest hash
+echo "Getting latest commit SHA hash"
+!_my_shell! -Command "(Invoke-RestMethod -Uri 'https://gitgud.io/api/v4/projects/%username%%%2F%repo%/repository/branches/%branch%').commit.id" > latest_patch_sha.txt
+
+REM Read the latest SHA from the file
+set /p latest_patch_sha=<latest_patch_sha.txt
+
+REM Check if previous_patch_sha.txt exists
+if not exist previous_patch_sha.txt (
+    echo "Previous SHA hash not found!"
+    echo "Assuming first time patching..."
+    goto download_extract
+)
+
+REM Read the stored SHA from previous check
+set /p previous_patch_sha=<previous_patch_sha.txt
+
+REM Trim whitespace from SHA strings
+set "previous_patch_sha=%previous_patch_sha: =%"
+set "latest_patch_sha=%latest_patch_sha: =%"
+
+REM Compare trimmed SHAs
+if "%latest_patch_sha%" neq "%previous_patch_sha%" (
+    echo "Update found! Patching..."
+    goto download_extract
+) else (
+    echo "Patch is up to date."
+)
+
+REM Delete latest_patch_sha.txt
+del latest_patch_sha.txt
+
+endlocal
+pause
+exit /b
+
+:download_extract
+REM Download zip file
+echo "Downloading latest patch..."
+!_my_shell! -Command "Invoke-WebRequest -Uri 'https://gitgud.io/%username%/%repo%/-/archive/%branch%/%repo%-%branch%.zip' -OutFile 'repo.zip'"
+if !errorlevel! neq 0 (
+    pause
+    exit /b
+)
+
+REM Extract contents, overwriting conflicts
+echo "Extracting..."
+!_my_shell! -Command "Expand-Archive -Path '.\repo.zip' -DestinationPath '.' -Force"
+echo "Applying patch..."
+xcopy /s /e /y "%repo%-%branch%\*" "."
+
+REM Clean up
+echo "Cleaning up..."
+del repo.zip
+rmdir /s /q "%repo%-%branch%"
+del latest_patch_sha.txt
+
+REM Store latest SHA for next check
+echo %latest_patch_sha% > previous_patch_sha.txt
+endlocal
+pause
+exit /b