A custom tool which allows you to tinker with your FF8 gameplay experience in real time.
- Edit your team
- Edit your party
- Edit your inventory
- Manipulate enemies in battle
- Disable field battles
Works with Steam English version FF8_EN.exe.
Swap characters into your party at any time...even characters you do not have access to yet.
Edit your character's level, hp, inventory, and more.
Setup and run:
- npm install
- npm run dev
Notes:
Project will automatically recompile after changing files
CTRL+R to refresh the window
Build only:
- npm run pack
Build and create installer:
- npm run dist
Notes:
Your install files and setup.exe file will be found in the /dist folder
If you just want to run the app exe directly, it can be found in /dist/win-unpacked (this is what will be installed when users run Setup.exe)
If you want to install the app, run /dist/ff8-battle-mod Setup 1.0.0.exe
Looking for a shareable component template? Go here --> sveltejs/component-template
This is a project template for Svelte apps. It lives at https://github.com/sveltejs/template.
To create a new project based on this template using degit:
npx degit sveltejs/template svelte-app
cd svelte-appNote that you will need to have Node.js installed.
Install the dependencies...
cd svelte-app
npm install...then start Rollup:
npm run devNavigate to localhost:5000. You should see your app running. Edit a component file in src, save it, and reload the page to see your changes.
By default, the server will only respond to requests from localhost. To allow connections from other computers, edit the sirv commands in package.json to include the option --host 0.0.0.0.
If you're using Visual Studio Code we recommend installing the official extension Svelte for VS Code. If you are using other editors you may need to install a plugin in order to get syntax highlighting and intellisense.
To create an optimised version of the app:
npm run buildYou can run the newly built app with npm run start. This uses sirv, which is included in your package.json's dependencies so that the app will work when you deploy to platforms like Heroku.
By default, sirv will only respond to requests that match files in public. This is to maximise compatibility with static fileservers, allowing you to deploy your app anywhere.
If you're building a single-page app (SPA) with multiple routes, sirv needs to be able to respond to requests for any path. You can make it so by editing the "start" command in package.json:
"start": "sirv public --single"