Closed StuBlad closed 1 year ago
I can't remember which of many changes I ended up doing fixed that particular error, but I got it working, as far as I can tell! Client connects and is presented with the Immigration locale, and I can wander about, open and close the door, etc. :) https://github.com/AmandaJonesAway/neohabitat
I got it working, as far as I can tell! Client connects and is presented with the Immigration locale, and I can wander about, open and close the door, etc. :)
Wow, amazing, great job!
I can't remember which of many changes I ended up doing fixed that particular error, but I got it working, as far as I can tell! Client connects and is presented with the Immigration locale, and I can wander about, open and close the door, etc. :) https://github.com/AmandaJonesAway/neohabitat
Fantastic, it does indeed work now! I can build everything, run the containers and connect the client. However, as soon as I move the avatar outside the door in the immigration locale the client disconnects:
`
date | stream | content |
---|---|---|
2023-03-28T21:05:07.555197304Z | stdout | warn: Error [ERR_STREAM_WRITE_AFTER_END]: write after end |
2023-03-28T21:05:07.389179996Z | stdout | warn: Error [ERR_STREAM_WRITE_AFTER_END]: write after end |
2023-03-28T21:05:07.220085576Z | stdout | - 2023/03/28 21:05:07.219 EVN comm-cli : TCP(1) died: java.io.EOFException |
2023-03-28T21:05:07.219699162Z | stdout | - 2023/03/28 21:05:07.218 EVN comm-cli : TCP(1) remote disconnect |
2023-03-28T21:05:07.211882865Z | stdout | debug: Disconnecting Habiproxy connection on: 172.18.0.4:42686 (unknown) |
2023-03-28T21:05:07.211563863Z | stdout | debug: {Bridge being shutdown...} |
2023-03-28T21:05:07.211217945Z | stdout | debug: Elko port disconnected... |
2023-03-28T21:05:07.210396183Z | stdout | debug: Client disconnected for Client 172.18.0.4:42686 (unknown), moving session to ASLEEP |
2023-03-28T21:05:07.208191736Z | stdout | debug: Habitat client disconnected. |
2023-03-28T21:05:07.207771886Z | stdout | - 2023/03/28 21:05:07.206 EVN cont (User.connectionDied:User.java:159) User 'user-testuser-2007421091341094457' connection died: TCP(0) |
2023-03-28T21:05:07.207393890Z | stdout | debug: Connecting: undefined:undefined <-> 172.18.0.4:42686 |
2023-03-28T21:05:07.206965341Z | stdout | - 2023/03/28 21:05:07.205 EVN cont : shutting down Context 'context-hatchery' |
2023-03-28T21:05:07.206444668Z | stdout | - 2023/03/28 21:05:07.204 EVN comm-cli : TCP(1) new connection from 172.18.0.4:49630 |
2023-03-28T21:05:07.206369407Z | stdout | - 2023/03/28 21:05:07.204 EVN cont : User 'user-testuser-2007421091341094457' exits Context 'context-hatchery' |
2023-03-28T21:05:07.206079289Z | stdout | - 2023/03/28 21:05:07.203 EVN cont (User.disconnect:User.java:186) exiting User 'user-testuser-2007421091341094457' |
2023-03-28T21:05:07.205175875Z | stdout | debug: Server connection established on: 172.18.0.4:42686 (unknown) |
2023-03-28T21:05:07.202711787Z | stdout | debug: Habiproxy client connected at: 172.18.0.4:42686 |
2023-03-28T21:05:07.202663584Z | stdout | debug: {Bridge being shutdown...} |
2023-03-28T21:05:07.202513559Z | stdout | debug: Elko port disconnected... |
2023-03-28T21:05:07.202096426Z | stdout | - 2023/03/28 21:05:07.201 EVN comm-cli : TCP(0) died: java.io.EOFException |
2023-03-28T21:05:07.200994418Z | stdout | - 2023/03/28 21:05:07.200 EVN comm-cli : TCP(0) remote disconnect |
2023-03-28T21:05:07.197832479Z | stdout | debug: Disconnecting Habiproxy connection on: 172.18.0.4:42674 (testuser) |
2023-03-28T21:05:07.197554390Z | stdout | debug: Destroying connection: 172.18.0.4:42674 |
2023-03-28T21:05:07.197408459Z | stdout | debug: Client 172.18.0.4:42674 (testuser) received changeContext, disconnecting... |
2023-03-28T21:05:07.197028347Z | stdout | debug: Processing Server message for Client 172.18.0.4:42674 (testuser): {"type":"changeContext","context":"context-Downtown_4d","immediate":false} |
2023-03-28T21:05:07.194725124Z | stdout | - 2023/03/28 21:05:07.193 MSG comm-cli : TCP(0) <- {"type":"changeContext", "context":"context-Downtown_4d", "immediate":false} |
`
At the time of writing, there is an issue writing to the database when you exit the hatchery/immigration region.
When you first connect to Habitat, your avatar is temporary and not written to the database properly until you exit the hatchery/immigration region. It's being looked at now to see why this is the case, but a place to look is in /bridge/Habitat2ElkoBridge.js
.
Specifically in
confirmOrCreateUser
enterContextAfterRegionChecks
I've not been able to check if you can login using one of the pre-existing users in the db
folder, but it would be good to see if that allows you to login and move around.
I'm closing this issue because it's been resolved on @AmandaJonesAway 's fork of NeoHabitat. There are still issues to be handled but I'll follow up with another issue for that.
Normally, I wouldn't mark an issue as closed until it is merged with the main branch.
On Fri, Mar 31, 2023 at 2:44 PM StuBlad @.***> wrote:
Closed #392 https://github.com/frandallfarmer/neohabitat/issues/392 as completed.
— Reply to this email directly, view it on GitHub https://github.com/frandallfarmer/neohabitat/issues/392#event-8902119230, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACM4EDCSPLDPJYCNXKNKQDW65F4DANCNFSM6AAAAAAWEKIJJM . You are receiving this because you are subscribed to this thread.Message ID: @.*** com>
As mentioned on the Slack and my Discord server, with the changes both @AmandaJonesAway and @hheimbuerger made to get the Docker container working again, we are still unable to successfully connect to the Habitat service.
When you launch the client, type your avatar name into the launcher and press return, a connection is established to the QLink reloaded service, but it fails out when you flip disks and press return.
This is a blocker to running a NeoHabitat server and for the eventual move to The MADE's infrastructure.
Here's the output from QLink Reloaded during this process.