d07RiV
Multiplayer
Multiplayer says game exist when creating but doesn't exist when trying to join.
Seems like @d07RiV just suspended both the development and hosting. I would say, You have to wait for another developer and probably hoster.
It's still up but still unable to connect to multiplayer. I would actually like to host it locally for myself on my server.
I forked it and made at least WebRTC working: https://knotschi.github.io/diabloweb/ It is using now the default WebRTC server from https://peerjs.com/ which seems to work fine.
I've also added a PR #113 for this change in case the @d07RiV is not planning to bring his server back up
edit: this seems to be a bit buggy. If the creator of the game leaves: the game crashes. If anyone else leaves and tries to join the game it seems to not always work. If you leave a game you need to quit the game and start it again in order to join again.
It worked for me fine using my local network. Through the internet it lagged a lot for me, most of the time it was not even possible to join a game. But maybe the internet connection was just not good enough. I am not sure. It also works fine on the same computer with different browsers (e.g. for exchanging gear between chars)
I also realized that sometimes, when it was not working anymore I had to restart the game (reload the browser) and than it was working again.
please try it out and let me know if it works for you
@kermitdafrog8 wrote:
It's still up but still unable to connect to multiplayer. I would actually like to host it locally for myself on my server.
By stopped hosting I meant WebRTC, the multiplayer service. The files are present, yes, that's why this repo is receiving reports about failing multiplayer mode.
Going to try the @Knotschi fork.
Yep, just tried his and it's working. Tested with 2 devices (mobile and desktop), 2 players WebRTC. You need to have your own MPQ otherwise it fails. I have the full one but I'm assuming the shareware might work as well.
AH, gotcha. It only works if the devices are within the same subnetwork. AKA all connected to the same wifi. Websocket was the option to make it work across devices on separate networks. But that doesn't work.
You might be able with a Virtual network. Could try "Logmein" or make your own VPN server + client.
Having to both run a server and VPN seams to deafat the point of webdiablo, woudn't using DevilutionX make more sens at that point? There are still several unsolved issues in webdiablo and the maintainer appears to have abandoned the project. If you are on Android/iOS maybe the time would be better spend finishing the native ports for those platforms as you would get a better interface and widescreen support. https://github.com/diasurgical/devilutionX
WebRTC should actually also work the same way over the internet as inside a local network. I am not sure if a virtual network would help here. I could imagine that the problem is just related to the higher latency over the web. But this would need to be tested, I don't know what the actual issue is. If I find some time for it I would like to do some further digging and maybe also try out to get the websocket version running but currently I have not time for that.
you need a signaling server if u wanna use webRTC over internet, https://www.webrtc-experiment.com/docs/WebRTC-Signaling-Concepts.html
@Knotschi I have some issue playing the Shareware version on your fork. Should it be reported?
I see knotschi/diabloweb doesn't allow creating issues in the repo.
@cojmar Yes, this is why the version from @d07RiV wasn't working anymore, he shut down his server which was used as the signaling server. In my version I am using the default server from https://peerjs.com/ (which is a js library for webRTC which was used, it provides a default signaling server that you can use instead of setting up your own) This signaling server is not only used when you use webRTC over internet, also for creating connections in the local network to the computers can find each other.
@sskras you are right, I haven't tried that before. It should be fixed now. I've also enabled issues on my repo now
@tiehr You mean over the internet? At least local network multiplayer works now fine for me on https://knotschi.github.io/diabloweb/
@tiehr I know it's been a while, but if it helps, I successfully played Knotschi's fork with 3 other friends over the internet (no VPN/Hamachi service etc) yesterday. This was using Chrome with the full MPQ.
Thanks for your fix @Knotschi , I've had a blast so far!
@tiehr I know it's been a while, but if it helps, I successfully played Knotschi's fork with 3 other friends over the internet (no VPN/Hamachi service etc) yesterday. This was using Chrome with the full MPQ.
Thanks for your fix @Knotschi , I've had a blast so far!
What configuration did u use? Windows? Wifi? Phone hotspot? What os? What device? What internet provider? Thank you :)
What configuration did u use? Windows? Wifi? Phone hotspot? What os? What device? What internet provider? Thank you :)
OS: Windows 10 on desktop PC Connection type: ethernet (but my friends were on WiFi at their houses)
All of us are on stable fibre connections in Australia/New Zealand.
One of us hosted using WebRTC peer (or whichever the top option is in the multiplayer), and the others simply entered the game name. The time to connect was about 5-10 seconds.
What configuration did u use? Windows? Wifi? Phone hotspot? What os? What device? What internet provider? Thank you :)
OS: Windows 10 on desktop PC Connection type: ethernet (but my friends were on WiFi at their houses)
All of us are on stable fibre connections in Australia/New Zealand.
One of us hosted using WebRTC peer (or whichever the top option is in the multiplayer), and the others simply entered the game name. The time to connect was about 5-10 seconds.
Thank you very much, will try again. My suspicious now is that phone network providers block something . . .
What configuration did u use? Windows? Wifi? Phone hotspot? What os? What device? What internet provider? Thank you :)
OS: Windows 10 on desktop PC Connection type: ethernet (but my friends were on WiFi at their houses) All of us are on stable fibre connections in Australia/New Zealand. One of us hosted using WebRTC peer (or whichever the top option is in the multiplayer), and the others simply entered the game name. The time to connect was about 5-10 seconds.
Thank you very much, will try again. My suspicious now is that phone network providers block something . . .
Out of curiosity, I just tried to connect between my Macbook and my Android mobile (both using Chrome). It worked on WiFi, but failed (joined, then timed out) when my phone was on the mobile network (off WiFi).
I think a lot of providers (especially mobile network) block port 443 that the public PeerJS server relies on.
What configuration did u use? Windows? Wifi? Phone hotspot? What os? What device? What internet provider? Thank you :)
OS: Windows 10 on desktop PC Connection type: ethernet (but my friends were on WiFi at their houses) All of us are on stable fibre connections in Australia/New Zealand. One of us hosted using WebRTC peer (or whichever the top option is in the multiplayer), and the others simply entered the game name. The time to connect was about 5-10 seconds.
Thank you very much, will try again. My suspicious now is that phone network providers block something . . .
Out of curiosity, I just tried to connect between my Macbook and my Android mobile (both using Chrome). It worked on WiFi, but failed (joined, then timed out) when my phone was on the mobile network (off WiFi).
I think a lot of providers (especially mobile network) block port 443 that the public PeerJS server relies on.
Same, pc on wifi + android on mobile network
Guess im little late but ill give it a shot if any kind soul has the time to help me out.
When im selecting multiplayer it gives me the following error:
Does anyone know what i have to configure on my server end?
Many thanks in advance!
@eden-lecomte maybe you can show me the right way to do it?
