One other thing I noted - I actually have newer opcodes and patches than you. Mine have a few more entries making the files slightly larger.
|
Quote:
|
Quote:
|
https://imgur.com/a/NeKRwlu
https://imgur.com/a/NeKRwlu This is how I did it since I wanted the installation self-contained like the windows version. I didn't want the separate eqemu user nor that folder. (I can't see the image and I'm not sure why so I pasted the url too) (also ignore bin-docker, it's just a backup of the executables built in the docker, I'm running the precompiled ones now) |
You can technically setup the bin folder anywhere, put the executables inside it, as long as your symlinks point to them. One time, I created a bin folder, right inside the server folder and put them in there to run them.
In the original linux install, it created a /home/eqemu/server_source and /home/eqemu/server_build (which also created a bin inside of that) when the binaries were compiled. If you follow the instructions for compiling, at the end of that readme-setup, whatever build directory is used for compiling, it will create a bin folder there. |
Quote:
|
Quote:
The docker install, I "think" was created by that Akkadius that left recently. I'm not sure. |
Quote:
I've only worked with Ubuntu personally. That was the last thing I could think of, that maybe this one quirk is related to running the newer 24.04, but who knows at this point lol. |
Ok, I got it working. I gotta own this one lol.
Creating the symlinks in the root of the installation, pointed at the bin folder right there in the installation, fixed the problem. I didn't think this could actually be the problem because everything else worked, but I was wrong. The only thing that makes any sense to me is I saw a snippet somewhere, not even related directly to this problem, where someone mentioned the executable point needs to be in the same folder as the eqemu_config.json file. I guess I proved everything else EXCEPT the dynamic zones works thru just a reference of the original calling folder lol. Oh well, it's fixed! Thanks for dealing with me LOL. |
Someday, maybe I will go to work on that install.sh script to turn it into a full auto-install, but I would need to secure download file links for it. It's still the original install script, all I did was edit a few lines to compensate for manual setup. Originally, in the script, it would download the eqemu_server.pl which the script would call at the end of it. So a big part of the install was in that .pl file
If I could get my hands on that original eqemu_server.pl file it would help build a new script. But the current one available is blank. |
Quote:
https://github.com/kevman5/Eq-Emulat...qemu_server.pl |
Quote:
|
Quote:
Another link, think this one is direct from Akk: https://github.com/EQEmu/Server/blob...qemu_server.pl |
Ok, I was having probs viewing the files right on github, but I downloaded it and YES, that's the file I need. Last time I did a windows install, (long ago) it downloaded a blank eqemu_server.pl file. Even the one's in my windows servers, have a blank one. But I think the installer gets it from elsewhere
But it's obviously still available. I just kept seeing a blank file on the github, must be my browser, lol |
In the source github changelog it shows:
### Deprecation * Remove eqemu_server.pl script and ties to server ([#4049](https://github.com/EQEmu/Server/pull/4049)) @Akkadius 2024-02-10 Obviously the modern code had no use for it anymore. It was also used for updates, etc, previously. |
All times are GMT -4. The time now is 06:49 PM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.