README x Geyser (#74)

* Fix Geyser message in README

* Re-insert mention of GeyserConnect

* You don't actually need to set "all" the parameters; just the hostname

* Edit2: that service is not useful for this use-case anyway

(I got the name confused...)

* replace to how to use with geyserconnect

Co-authored-by: creeper123123321 <7974274+creeper123123321@users.noreply.github.com>
This commit is contained in:
James 2021-02-21 02:03:12 -06:00 committed by GitHub
parent 4ee964e31f
commit f998115b43
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -79,4 +79,11 @@ How to use IPv6?:
- To use IPv6 in backend address, you need to use a instance with IPv6 connectivity. The hostname parser currently doesn't support direct IPv6, but you can use a DNS name. - To use IPv6 in backend address, you need to use a instance with IPv6 connectivity. The hostname parser currently doesn't support direct IPv6, but you can use a DNS name.
How to use with Geyser? How to use with Geyser?
- Currently you need to use GeyserConnect - Currently you need to set the parameters (at least the hostname) in Geyser's `address` field:
```yml
remote:
# The IP address of the remote (Java Edition) server
address: 2b2t.org._v1_12_2.viaaas.localhost
```
- If you are using a public GeyserConnect instance: connect to a publicly available VIAaaS instance ```mc.example.com.viaaas.example.net```,
replace ```viaaas.example.net``` with the VIAaaS address. Set as a Java Edition server.