Quote:
https://i.ibb.co/7CHh0RQ/peqdb001.jpg |
After some time, I reinstalled the entire server. I wanted to be sure I hadn't done something along the way, I didn't mean to, or hadn't known would screw me.
I've been playing about in the DB, using Heidi, and it's starting to make more sense to me. I now, see, however, that this is my problem: HTML Code:
[Update] No script update necessary... I've been attempting to point the eqemu_server.pl to my MariaDB folder, by editing the "get_mysql_path" lines, around about line 990. No matter what format I used, I couldn't get it to use the path I manually inserted. I suspect the problem is that my MariaDB folder is actually labeled "MariaDB 10.0". The server file is looking for "MariaDB/i". I realize the "i" is for the "include" folder, but as you'll see below, I was concerned by how the filepath was stated. I came to this conclusion, when I had changed my MariaDB folder name from "MariaDB 10.0" to "MariaDB", because I suddenly couldn't run MySQL.exe, nor could I find any way to alter the filepath (MySQL.exe) to the right one. What I believe is the offending code from eqemu_Server.pl: HTML Code:
sub get_mysql_path { For all I know, I'm doing this all wrong, but I wanted to try and figure it out, myself. After about 5hrs (plus the about 2 days, I've been stuck on this problem as a whole), I'm not sure what to do lol. EDIT: The more I look at the prompts for World, Zone, etc., the more I think I was in the wrong place. They appear to access the MySQL just fine; the server loads, and seems playable (although, i've only had a chance to run around and test the spawn points loc's). |
UPDATE: PARTIALLY SOLVED!
Ok, so as it turns out, I was missing Environmental Variables, for the Windows Command Prompt to work with. This post led me to that answer. But here's the short version! Fixing: [Error:eqemu_server.pl] MySQL path not found, please add the path for automatic database upgrading to continue...
HOWEVER, I'm still experiencing the problem with Starting Zones. I've seen a couple other posts but no answers. The server appears to be using the variable (peq>start_zones) player_choice (i.e. Gukta on the character creation screen for starting zone) to identify the starting zone, instead of zone_id. One person had an issue with expansions not being locked out, and it was simply about setting rules_values > World:UseClientBasedExpansionSettings > false. I've done this, and am still popping up in places, I shouldn't be. My quest continues. |
I'm way too tired at the moment to try this, but is it possible that the difference in DB and table entry names, could be to blame?
example: in char_create_combinations, it's listed as start_zone, where as, the DB file is labeled start_zones? |
Quote:
I know you may have difficulty understanding the database and (possibly), the problems you experience, but one thing I can assure you, the default server, as a whole, functions as intended. I am constantly goofing around testing (abnormal) things, then when I am done, I delete the whole database and download a fresh copy, which functions, as it should with all it's default settings. Sometimes, when there is updated source code (for the binaries), I will re-compile those as well. In most cases, the reason anyone has issues with part of a server not working properly, it's something that happened on their end.(on their computer). This could be anything from a needed app that wasn't installed correctly, to configs that were edited wrong, or databases that got edited and/or corrupt in some way that caused a malfuntion. I just installed a fresh database last night and it's working as expected, with all it's default settings. That whole process, including getting it fully updated only takes me about 10 minutes. But that's something anyone can do, once they have the knowledge and experience to work with these servers. It also helps to have some more advanced knowledge of your computer. (files, folders, apps, etc.). Believe me, 25 years ago, when I had absolutely no knowledge of computers, if I would of came to a site like this, I would of shut my puter off and went back to my nintendo ;) Before I did start monkeying with this project 9 years ago, I had never dabbled in anything related to perl, sql or databases. I had no experience at all. A lot of reading, trials and tribulations learning the basics of it all. But because this whole Emu project is forever improving and evolving, the learning never stops. It's a lot easier when someone stays on top of it, rather than going awol for awhile and coming back to a brand new chapter. For those simply using the installer and the updater, it's not a concern anymore, but for many doing custom work, manual installs and updates, it can be tedious reviving an old server and getting it up to date without breaking it. (custom content). |
Thanks for the big feedback. I thought I was using the wrong terminology, but I wasn't sure.
The table names thought, came to me while half-asleep, and having stared at the screen for something like 14hrs, and now makes more sense to me lol. I'm trying to recall, if I tried a new toon, on the fresh server, prior to fixing the Environmental issue, and making any changes. I don't think I did. I think now that one issue is out of the way, it's time to start a fresh folder (or perhaps, walk back some of the major changes I made), and see what happens. Suppose the best thing I should do, is make one change, then see how it affects the server. I think my frustration and, let's say, lack of knowledge, led me to overthinking and not slowing it down lol |
STATUS UPDATE
-Deleted the Server Folder -Uninstalled Perl -Uninstalled MariaDB -Deleted any left behind folders. -Restarted PC -Ran CCleaner directory cleaner -Unzipped server archive into folder on my D: drive (My SSD) -Ran installer -Installer eventually fails "MySQL path not found..." -Update Environmental Variables -Server install proceeds -> Complete -modify "login_server2" in config.json file to reflect LAN ip -Boot up server "t_start_server_with_loginserver" -error logging into loginserver (presumably because I've not inputted any login credentials) HTML Code:
[Login Server] Logging System Init. -make Froglok Warrior -spit out in South Qeynos >:| -"No start_zones entry in database, using defaults" under World.exe prompt HTML Code:
[World Server] Loading server configuration.. You also asked for PC specs: HTML Code:
Operating System: Windows 10 Home 64-bit (10.0, Build 17134) (17134.rs4_release.180410-1804) The only other server software I've ever run, to my knowledge, would be ASM (Ark Server Manager). It was a pretty dummy proof piece of software, where everything was handled in one single window. You simply filled out fields to alter the server, and input mod id's. I uninstalled it, about the time I decided to give this a shot. |
I knew I forgot something! Took this from the forementioned Froglok Warrior. This happened on all new toons.
https://oi32.photobucket.com/albums/...psfe22udes.png Is it possible this issue is Client-side? I just remembered that my Titanium folder has been altered to play in P99. |
Quote:
|
Sorry Stubbay, I hadn't used Titanium client in a long time, but I just fired it up and logged into that fresh install, and it's definately a client issue with the character creation. I got the same thing as you.
BUT, when I login with an RoF2 client it works as it should. Every toon has it's choice of the classic start zone or Crescent Reach, which is normal. (frogs in rathe mountains). This is with all expansions enabled, no db edits. I'm going to play with this for awhile and see what happens. |
Quote:
I have forgotten to say, thank you, for the immense amount of IT support you've been giving me. I've seen you all over the board, reading other related posts lol. Guess I'll take to poking about my client files, then; see if I find anything, in the meantime. |
Found this, in Everquest\logs\dbg.txt:
HTML Code:
2019-06-22 22:22:10 Just updating the post, I suppose. EDIT:Against my better judgment, I decided to take this issue to the folks over at P99. Hopefully, they won't mind my non-P99 issue. I'm using Titanium to play just fine on their server; so, thought it wouldn't hurt to ask. |
Update: the P99 dbg.txt, shows the same "error". So, I'm guessing this absolutely has nothing to do with the issue. I'm trying to figure out what files/tables/etc., are responsible for communication between the client and server. I assume the issue may be there, but really, I'm taking what I assume are educated guesses.
EDIT:The patch_titanium.conf & opcodes.conf, look oddly similar. I thought "op" was for "other patcher" or something (swear I read that, somewhere). Wondering if this is the culprit; if I can simply steal OP_CharacterCreate from one of the other patch files, such as SoF. May try it. *shrug* EDIT: Tried the above... caused errors and a crash lol. I stared at the P99 files, for a while, and the only file that seems like it would have any real effect, was dsetup.dll. I threw this into my client folder, and it did nothing. I'm guessing the issues, have to be server-side, but with how it communicates with Titanium, specifically. At least, I feel like I'm narrowing things down. |
I've noticed something new, and am not sure if this is considered"normal".
HTML Code:
[Login Server] Logging System Init. |
Clients do not stay logged into the login server.
They are handed off to a world server..so, that's normal behavior. |
All times are GMT -4. The time now is 03:21 PM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.