Quest Hand-ins Broke all the sudden.
For some reason quest item handins broke out of nowhere.
Behavior 3 days ago (tested): Working as intended. Npc quests fully working. Behavior now: Hand quest npc item; quest npc faces player; npc eats item. Things I have checked. Checked the check_handin.pl plugin, hasn't been touched, looks ok. Tried multiple npc's (20 or so) Checked npc's that verified worked 3 days ago Checked logs folder for _quest.log and found this several times: --------------------------------------------- [01.24. - 11:56:39] Starting Log: logs/eqemu_quest_zone_10156.log [01.24. - 11:56:39] Tying perl output to eqemu logs [01.24. - 11:56:39] Creating EQEmuIO=HASH(0x64a9d8) [01.24. - 11:56:39] Creating EQEmuIO=HASH(0x658f7c) [01.24. - 11:56:39] Loading perlemb plugins. [01.24. - 11:56:39] Unable to read perl file 'plugin.pl' [01.24. - 11:56:39] in quest library [01.24. - 11:56:39] done with quest library [01.24. - 11:56:39] Use of uninitialized value in string eq at plugins/quest_test.pl line 26. [01.24. - 11:56:39] Loading perl commands... [01.24. - 11:56:39] Unable to read perl file 'commands.pl' Then I checked the plugin.pl, and other plugin .pl and don't see anything wrong. Anyone know what this could be? Re-install Active perl? Why all the sudden? Nothing has changed in the quest department? Update: I have now also re-installed perl, and restarted the server. Still eats the items. Also for plugin dbaccess.pl, does the db.ini that it refers to need to be defined and put in the c:\eqemu\db.ini folder? |
Quote:
|
Thanks for quick help.
The line you told me to look at. Quote:
Code:
if($ARGV[0] eq "-nodb") { Code:
[Database] Next post shows my new log since I have made the corrections but hand ins are still broke. |
What is perplexing is I haven't changed any of this and never had an issue, well I mean there is obviously issues with say globals but hand ins were fine. Grr.
|
Okay. I guess I have fixed all the errors. Handins are still totally broken. Everything else is fine.
Generating this log now. Code:
--------------------------------------------- |
FIXED. Replaced quests with restore from 1 year ago. Must be something I opened in regular notepad on accident.
Rule of thumb. Never open anything to do with a quest with regular notepad. Use Notepad++ or Notepad2 Thanks for the help. |
Issues like this will happen even to most disciplined developer. I recommend some form of version control system over all your files so you can see with ease if anything has changed.
|
I am having the same issue. After using the newest build with Cmake my tomes and soulbinders are broken. Plus there is other random things im finding as well.
|
Quote:
|
Did you guys have working servers before?
I have to copy the entire source directory to my home computer every day when I get home and rebuild the entire thing from scratch. In addition, I copy all eight *.conf files and search for any sql updates. If there are changes to the 'quests' svn, I delete my existing files and copy over the entire quests folder, then do the same for my plugins. I have not had a problem with any script-related activities as yet, though my last build was revision 2460. You could still be having viable issues, but you will need to give more diagnosable information. |
Quote:
|
I tried the #bind command and it worked for me on the current rev, and a slightly older one (didn't note which one).
I don't normally use #bind, just #cast <whatever the spell id for bind affinity is> but I noticed #bind doesn't produce any output by design and /charinfo doesn't reflect your new bindpoint after using it until you zone. Anyway, #bind simply updates your bind point in the player profile and doesn't use Perl or rely on spell casting, so there is nothing that has changed that could have broken it for you and not for everyone else that I am aware of, unless it is a 64 bit compile issue (I tested on a 32 bit system). I doubt very much it is a 64 bit issue after having a quick look at the structs involved. |
Yes I had a working server. I went to rebuild my server box and my old source directory got corrupted on the backup. So I had to use a new build. I did compare my old quests/scripts vs new svn for handin and soulbinders and everything looked identicle.
I just checked the #bind command and it doesnt work for me either. |
i have the latest build and keep up to date with the quest repository. the #bind command works, as do soul binders, as do turn-ins.
do you have the appropriate permissions to use #bind? is your plugins directory in the correct location (in your server directory, not in the quests directory)? |
I just compiled the newest, 2466, and it works fine now. Not sure what the issue was before. I am using Mercs if that helps.
|
All times are GMT -4. The time now is 05:38 AM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.