Go Back   EQEmulator Home > EQEmulator Forums > Quests > Quests::Q&A

Quests::Q&A This is the quest support section

 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #24  
Old 10-19-2004, 02:12 AM
RangerDown
Demi-God
 
Join Date: Mar 2004
Posts: 1,066
Default

Lurker said it best.

The two arguments you give for a redo are: (1) some functions aren't there you believe should be there, and you aren't happy with the what some variables are named, and (2) you believe it is too complicated for some server ops to use.

(1) It's unreasonable to expect to predict everything a server op might want to do in quests. If you find some quest functionality in EQlive quests/encounters that we don't have Perl functions for, then point them out. Perhaps write the hooks in yourself and submit them for CVS consideration. Wanting to flag GM rank via quest is the first time I've heard of that, and for obvious security reasons there is no quest to do that in EQlive. But since our goal is to emulate EQlive, I'm quite certain that objective carries over into the quest system -- if EQlive does it, then eventually our quest system will do it too.

Nobody is going to want to overhaul the system based purely on semantics. You want $gmrank, I want it kept at $status. Either way, I don't think any variable names are worth overhauling. Too many quests have been written among the various servers to up and change variable names at this point and break all those quests.

(2) Perl was chosen because we wanted the flexibility and power of a scripting engine. We need to be able to evaluate complex conditions, take an indefinite number of actions, and be triggered from a variety of events. That's a pretty powerful scripting engine that would have to do that... and we have it, and best of all, we didn't have to mess around with the scripting engine itself, Larry Wall did that work for us

There are quest editors out there whose design is to present a more friendly interface to the user, and allow the user to design quests with said friendly interface, while the editor does the dirty work of making perl code behind the scenes. Having these editors is a great way to make quests easy enough for the perl-unsavvy, without compromising the power of the underlying quest engine. If you attempt to dumb down the quest engine itself, I guarantee what you're proposing will not be accepted by the user base.
__________________
<idleRPG> Rogean ate a plate of discounted, day-old sushi. This terrible calamity has slowed them 0 days, 15:13:51 from level 48.
Reply With Quote
 

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

   

All times are GMT -4. The time now is 03:40 PM.


 

Everquest is a registered trademark of Daybreak Game Company LLC.
EQEmulator is not associated or affiliated in any way with Daybreak Game Company LLC.
Except where otherwise noted, this site is licensed under a Creative Commons License.
       
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Template by Bluepearl Design and vBulletin Templates - Ver3.3