oh I know how it worked on live, I am saying doing it via flag rather than actual key is complitly unnesesary. The thing that realy matter that player need to kill the JD in order to get the Factory access. And whenever access is granted via key, flag or script- is complitly irrelevant 8)

But doing it any other way isn't Live Like, which is the aim of this project.

I know I know =)

All I am saying when mimicing the cover you don't have to mimic the engine 8)

How about lockable doors can't be manually closed? Otherwise the only other way to prevent a door key + door flag exception is to have a Doors::WasFlagOpened type of member variable that can be accessed via perl. And it would have to reset itself when the door auto-closes. Thats probably the better way to go. I promise I'll get the multi-key door thing coded (with the WasFlagOpened change) right after I get back from Chicago this Sunday.

I've come up with a solution in my head that doesn't require modification of any perl scripts, but it still includes a database improvement. I'll get to work on it today or later this week when I have a chance. Anybody know when the next release of eqemu is coming, for all of these changes to be included? I'd like to see all the combat changes included too.

I thought the new SVN that everyone's using was the solution to this problem.

Yes it is :)

http://www.eqemulator.net/forums/showthread.php?t=26376

Hmm. I got the impression from Cavedude that the SVN is the experimental/dev branch.

Well, it still isn't the official code release, but most of the builds on there are good ones. And if something does work, you should be able to easily go back a version or 2 and use one that does work. So far, there have been a ton of great changes that aren't in the 1129 code.

Agreed. I run r52 currently but will continue to aggressively upgrade. I've automated the update and build process, which makes me happy. I haven't figured out how to automate the DB changes yet, though. I think it's up to the devs when they want to push an "official" release out to the public site.

The official source is just as experimental as the SVN - I haven't seen anything go wrong yet with the new SVN except we got nice things like keyrings, Bot code, task system, etc. Not to mention the bundle of fixes made to bugs that are in the official source :). This is much better than foraging fixes off the forums, begging to get them in the source!

The only problem I see, is the Windows bins are not available, and at this point, with all the info and help posted, it is extremely easy learn how to compile your own exes. I'll help anyone to learn this if they are having problems. I'll try and update the bins I have posted tomorrow, I just am doing a million other things.

The PEQ SQL update I made, is very easy to do , on my 5x MySql you can run at the 'command line mysql -u(user) -p(password) -D(database) < pequpdateposted.sql'
It already has the DROP and CREATE table statements, so no need to run any other SQLs. I'll try and update that too, with the latest one.

From what I've seen, the binaries posted here on the GoogleCode page seem to work just fine as binaries, and don't lag too far behind the latest revisions. Pretty thrilled with it, actually.

Jaystonian -- You've been doing some great work here, the keyring is marvelous. Hopefully now that you've got the link to the SVN (from us all invading your thread =P), you'll get what you needed in order to continue.

We'll probably be updating official source soon too. I think where we are is stable enough for another release.