That did it. Turns out I have a combination of issues to sort:
1) Desktop Short-cut was wonkie and was running the eqgame.exe from a UF client folder but looking for resource files in the RoF folder ... got that fixed up and the client appears to work the way it should (was able to log into PEQ w/ RoF client). 2) Discovered an issue w/ my server. It appears i may have missed a db update or two and might need to update my quests repo. |
well, i'm not sure what the deal is. It's now showing i have 0 character slots available, and my existing toons aren't allowed to zone in.
i'm tired. i'll give it another go tomorrow. |
progress yay!
I updated my source and used the new CMake system to compile the latest and i'm now able to get into the game env with both my UF and my RoF clients. now to get bots working... I set EQEMU_ENABLE_BOTS to ON during "cmake -i" but it appears that I may have missed something else, because i'm currently getting "You cannot spawn any bots" when i attempt to "#bot spawn <name>" in game. |
that's because you have the BotQuest rule enabled, your gm flag is off, and your bot_spawn_limit qglobal is set to 0.
|
Ah! It was the GM flag. Is there a way to disable the "#gm on" (that doesn't require changing source code?) requirement before spawning bots?
thanks for the help! |
no, it wasn't the GM flag. again, it's the Bots:BotQuest rule in the database. yours is set to 'true'. if you don't intend to require a quest to be completed to allow a client to spawn bots, you want to set this to 'false'.
|
No ... the DB has the settings you say I should have...
Code:
mysql> SELECT * FROM `rule_values` WHERE `rule_name` LIKE 'Bot%'; Despite having the settings that you say the DB should have I still had to use "#gm on" in order to spawn my bots. So, assuming that I shouldn't need "#gm on" to spawn bots with my settings, that must mean there's either something wrong with my compile or there's a bug in the source somewhere... I see more updates have been committed since i compiled earlier this morning. I'll recompile with the new commits to see if that changes anything. |
The only way to get that exact error is to have that rule enabled.
Code:
if(RuleB(Bots, BotQuest) && !c->GetGM()) { |
I'm compiling with gcc 64bit ...
when I run 'cmake -i' i also disable the -O2 and -O3 optimizations because the server borks and dumps clients like hot cakes on login if i don't (stringstream thing)... http://www.eqemulator.org/forums/sho...d.php?p=182629 Other people are experiencing the same -O optimization issues in Linux. A new thread popped up last week about it, and it has links to 2 other threads on the issue. Also, I'm compiling on Linux ... this thread was in the development area when I started posting in it... then it got moved to 'Windows Servers' some time today... |
There has been an issue with 64-bit and bool rules before. *shrug*
|
pretty sure those are all worked out.
|
well... I noticed I don't have a bot_spawn_limit entry in my quest_globals table.
I'm pretty sure i've never had it, but just in case i've started searching the sql files for the one that creates that entry in the quest_globals table, and so far the only "bot_spawn_limit" entries i'm finding are in the comments section of the rule_values table :\ bah... I just enabled the quest NPC and hailed him that created the "bot_spawn_limit" table entry for me. I got GM-less bots working again, not quite the way I expected, but it's working again. Thanks for the help everyone. |
Quote:
|
so you got to work by toggling the rule on and off because it created the bot_spawn_limit qglobal? weird. it shouldn't have even checked for the value of the qglobal if the rule was false. i'm assuming it's set to 0 still?
|
Not quite. I had no bot_spawn_limit entry in quest_globals, but it seems that my server was checking for it even though rule_values.Bots:BotQuest was set to false.
So, to make bots work without GM, I enabled the Quest NPC and started the quest to get the quest_globals.bot_spawn_limit entry. Then I manually edited the quest_global.bot_spawn_limit entry and set it to a non-0 value, because I didn't want to do the quest, and my server is still checking that entry even though rule_values.Bots:BotQuest is set to false. I did try setting rule_values.Bots:BotQuest to true and then back to false, but no matter what it's set to the server acts like it's always set to true. It was set to false at the start of this problem. It's set back to false right now. I tried removing the bot_spawn_limit entry after cycling the Bots:BotQuest back to false, and the server instantly gave me the "You cannot spawn any bots" error. It's definitely weird. |
All times are GMT -4. The time now is 05:23 AM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.