For best viewing experience, please use a markdown viewer that supports Github or Gitlab Flavored Markdown syntax.

Yes. There is no function limitation, but keep this in mind: you may encounter scalability or security issues which I probably won't focus on.

No. It's hardcoded inside a game and server can do nothing about it.

Yes. There will be no major consequences even without it.

• 80: ALL.Net, game endpoints and Aquaviewer
• 8443: Billing
• 22345: Aime

Here are some tips:

• ALL.Net and game endpoints can be proxied
• Billing endpoint can be proxied but with extra steps: enable deprecated TLS_RSA_* cipher and use self-signed ib.naominet.jp TLS certificate - or simply disable it
• DO NOT proxy Aime endpoint: it's TCP traffic, not HTTP
• DO NOT compress traffic: proxy as-is if you can
• DO NOT use CDN proxy: e.g. Cloudflare
• Set allnet.server.host in application.properties with your public IP or hostname
• You may change endpoint ports for internally (aqua <-> proxy), but external ports that are exposed needs to be the same as default (proxy <-> game)

Delete exclamation mark character(!) in your directory name.

You can add database entry by hand or your handmade tools. Currently Aqua doesn't have a way to do this automatically. I don't have timeframe for this either.

Read the changelog to check breaking changes before updating. Then follow one of these options:

• Take jar file (aqua.jar) from newer release and replace it
• Copy your current DB file (data/db.sqlite) and config file (application.properties) to newer release folder

Identity which process is using 80 port then terminate it. Game won't connect to Aqua server if port is different then 80 port, so it is necessary.

No. This is due to hardened security measures which SEGA made.

It'll be case by case basis. Open an issue if you want to suggest something.

I won't work on it myself, but merge request is welcome.

No, games will still work. However, new content probably not appear in game without so-called "force unlock" and Web UI will not work as intended when displaying new content.

Probably not without update, but who knows?

Some game have kill switch for prevent early run before release date (a.k.a "Flying Get"). In this case, BOTH client and server need to handle networking enable flag for avoid this problem. For client part, consult with your source. For server, wait for future Aqua update with new version support.

Convert application.properties text encoding to UTF-8 without BOM.

Yes.

While it may work, I can't give any support with it.

No.

I won't give any help on this repository.

It is because Aqua is using Spring Boot as a base. It's a upstream issue, not something that can be fixed on this project side.

I, the fork maintainer, am not affiliated with any public hosted instance. Contact to your server maintainer instead.

Please don't. I'm not hiding anything in the repository and currently no plan to give direct write access to anyone. However, merge request is always welcome.