Setup Dimentions failure

Question

Setup Dimentions failure

Opened this issue 7 months ago · 18 comments

Some people got it work but I cant. Used the commands said in the instructions: npm install --only=productionandnpm run start` in the folder with the Dimentions files. After
running these commands and got this output:

@popstarfreas/dimensions@5.10.0-beta.1 start
cd ./build && node ./index.js

I expected to get this output:

@popstarfreas/dimensions@5.10.0-beta.1 start
cd ./build && node ./index.js

[ any 4 digit number idk ] Server on port 1 started
[ any 4 digit number idk ] Server on port 2 started <

Thinking that maybe it shouldn’t show me that, I joined the server and tried commands like /dimensions , / _server name in config_ and even tried with /sudo . Nothing worked! Can somebody help me?

Answer 1 · 2024-04-20T18:45:28.000Z

What does your config look like?

Answer 2 · 2024-04-20T18:47:48.000Z

"use strict"
exports.ConfigSettings = {
servers: [
{
listenPort: 9000,
routingServers: [{
name: "lobby",
serverIP: " server ip ",
serverPort: 9000,
hidden: false,
}]
},
{
routingServers: [{
name: "world",
serverIP: " server ip ",
serverPort: 9001,
hidden: false,
}]
},
],
}

Answer 3 · 2024-04-20T18:51:22.000Z

By the way, where should the Dimensions files be? Like in the plugin folder in tShock or in any location.

Answer 4 · 2024-04-20T18:59:19.000Z

Dimensions is its own program so it doesn't need to be in the tshock folder, only the actual dimensions dll should be in the plugins folder.

With that config I think all logging is disabled that could be why you don't see any messages. It looks like you set listen port and server port to 9000. They should be different. Listen port is what you will use to connect and server port is what port your tshock server is using.

Answer 5 · 2024-04-20T19:25:57.000Z

I changed the listen port to one of the server ports because I thought it would work, and if I joined the server using the port 9000, it wouldn't redirect me to "lobby." It sounds stupid, but it was worth trying. Maybe this would help, I use Dimensions 5.10, but tried a little bit on 6.0.0.

Answer 6 · 2024-04-20T19:43:34.000Z

The latest version is the best though I've not built with all the recent changes yet. What happens when you change the listen port to something else and join using that port?

Answer 7 · 2024-04-20T19:45:05.000Z

Nothing. Maybe the problem is that I don't know how to setup the plugin.

Answer 8 · 2024-04-20T19:53:15.000Z

What do you mean by nothing? When you use your game to join that port what happens?

Answer 9 · 2024-04-20T20:06:35.000Z

Nothing different happens

Answer 10 · 2024-04-20T20:15:37.000Z

You get connected to the server still?

Answer 11 · 2024-04-20T21:08:35.000Z

Perhaps the example needs to be improved if it's not good enough

Answer 12 · 2024-04-21T05:00:40.000Z

You get connected to the server still?

If I use the listen port, it won't.

Answer 13 · 2024-04-21T08:03:21.000Z

It gets stuck on connecting or a different message?

Answer 14 · 2024-04-21T09:00:14.000Z

No! It says "Timeout connection", like the server doesn't exist

Answer 15 · 2024-04-21T09:09:15.000Z

And your plugin works with tShock servers hosted on pcs or laptops?

Answer 16 · 2024-04-22T08:26:05.000Z

The plugin itself should, yes. But the plugin only rewrites players' IP addresses to be correct when they connect through dimensions.

Answer 17 · 2024-04-22T09:06:13.000Z

I think that the plugin doesn't even know that my server exists. But can you sent me an screenshot that shows what the cmd window should output after running npm run start?

Answer 18 · 2024-09-02T09:20:24.000Z

I think that the plugin doesn't even know that my server exists. But can you sent me an screenshot that shows what the cmd window should output after running npm run start?

i have same problem too