[Archive] [Solved] VIP 4.3.4 worldserver.conf broken?
[Archive] [Solved] VIP 4.3.4 worldserver.conf broken?
Original source
Hi, all. I just updated to the VIP versions, but I'm running into various problems. (The main one being that the Worgen zone isn't working for me which is why i bought it...)
The other is that changes that I make to the worldserver.conf file don't seem to have any effect on the game. Forexample, if I change the experience rates or set the starting player money, these don't have any effect in the game.
Is the data locked somehow? The changes are showing the text conf file but don't take effect in game?
rektbyfaith
11-04-2025, 05:12 PM #1Archived author: CraigShaw • Posted: 2025-11-04T18:12:27.522121
Original source
Hi, all. I just updated to the VIP versions, but I'm running into various problems. (The main one being that the Worgen zone isn't working for me which is why i bought it...)
The other is that changes that I make to the worldserver.conf file don't seem to have any effect on the game. Forexample, if I change the experience rates or set the starting player money, these don't have any effect in the game.
Is the data locked somehow? The changes are showing the text conf file but don't take effect in game?
Original source
Hi,
I am unable to reproduce the issue. Works just fine for me. I have tried to re-produce the issue, but without any changes.
We haven't locked anything
![[Image: 1f642.png]](https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png)
Make sure you're modifying the worldserver.conf, and not the worldserver.conf.dist, and tahat you actually restart the server afterwards.
rektbyfaith
11-04-2025, 05:12 PM #2Archived author: CraigShaw • Posted: 2025-11-04T18:12:27.522121
Original source
Hi,
I am unable to reproduce the issue. Works just fine for me. I have tried to re-produce the issue, but without any changes.
We haven't locked anything
Make sure you're modifying the worldserver.conf, and not the worldserver.conf.dist, and tahat you actually restart the server afterwards.
Original source
Quote:ExO said:Thanks. I'm definitely editing the conf and not conf.dist and then restarting the worldserver. Maybe something is residual in memory. I'll try again by flushing and restarting everything (not just worldserver) and see if it helps.
Hi,
I am unable to reproduce the issue. Works just fine for me. I have tried to re-produce the issue, but without any changes.
We haven't locked anything
Make sure you're modifying the worldserver.conf, and not the worldserver.conf.dist, and tahat you actually restart the server afterwards.
Click to expand...
rektbyfaith
11-04-2025, 05:12 PM #3Archived author: CraigShaw • Posted: 2025-11-04T18:12:27.522121
Original source
Quote:ExO said:Thanks. I'm definitely editing the conf and not conf.dist and then restarting the worldserver. Maybe something is residual in memory. I'll try again by flushing and restarting everything (not just worldserver) and see if it helps.
Hi,
I am unable to reproduce the issue. Works just fine for me. I have tried to re-produce the issue, but without any changes.
We haven't locked anything
Make sure you're modifying the worldserver.conf, and not the worldserver.conf.dist, and tahat you actually restart the server afterwards.
Click to expand...
Original source
For anyone following this post, I found the error. I run through Linux and it was caused by the runtime interpretation of WINE 6.4. Dropped down to WINE 6.0 and problem is gone.
rektbyfaith
11-04-2025, 05:12 PM #4Archived author: CraigShaw • Posted: 2025-11-04T18:12:27.522121
Original source
For anyone following this post, I found the error. I run through Linux and it was caused by the runtime interpretation of WINE 6.4. Dropped down to WINE 6.0 and problem is gone.
1 Guest(s)
1 Guest(s)