When will we see Eqadmin 4.7?

[dil]

I was curious about that because of the problems with the pop items etc

[Windcatcher]

I've begun working on it. I've found several bugs that still need fixing, though. I'm hoping to get something up this weekend, but no promises.

WC

[fnemo]

a huge bug : FQadmin open a ton of SQL connection but never close them ....

[dil]

Thanks Wind Was curious when it may be out wanted to make some new items and that was holding me back same textures over and over

[Edgar1898]

WC:

Feature Request: Could you change it so it doesnt load everything from the db when you load the program? I dont use it anymore, I mainly use mysqlfront, but one of the things I wished for when I did use it was for a way to turn off loading all the information from the database when I only needed to edit 1 item or 1 table.

[Windcatcher]

Point taken about setup time. I think you'll be pleasantly surprised by 4.7...

WC

[a_Guest03]

WC, you're a BA!

[Edgar1898]

Heh I really dont see how he has the time to work on all these programs AND create zones out of it, and I thought I was busy :P

[Drawde]

Will you be supporting the new 0.4.4 DB values for tradeskills, pathing grids, etc.?
I often use EQEmuAdmin to check that my DB data is set up correctly.

[Edgar1898]

oh just an fyi I added a new table called bugs to support the /bug command the format is:

+------------+-------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+------------+-------------+------+-----+---------+-------+
| id | int(11) | | PRI | 0 | auto_increment |
| type | varchar(16) | YES | | 0 | |
| name | varchar(64) | YES | | NULL | |
| account_id | int(11) | YES | | NULL | |
| bugtext | text | YES | | NULL | |
| flag | varchar(64) | YES | | NULL | |
+------------+-------------+------+-----+---------+-------+

not sure if you want to include it in your next version.

I'm also going to be adding tables for the /inquire and /report commands although I havent finalized a table for them yet.

[Trumpcard]

Take a look at my bugtrack code that I put in. It worked great , but we never implemented it.. It would upload all bug reports to a central data table, then we were going to make a BugView page so you could view them from the web on eqemu.net and we could assign developers to it.

We never followed through with it, but the idea was players on any server could submit bug reports directly to us...

[Edgar1898]

That wont work for a lot of servers because people make modifications specific to that server and not the original, but why not do both? Use /bug for server specific bugs and #bug for general eqemu bugs.

[Trumpcard]

My biggest concern was that we'd have a million bug reports of the form.. 'Mobs are jumping' and 'Why arent there any merchants in EC ? '

[Edgar1898]

Thats what you would get if you started uploading #bug reports to a central server though. Think of this scenario:

Bob says out of character, 'Does /bug work?'
Joe says out of character, 'try #bug'
Bob says out of character, 'OK Thanks'

and then you get bug reports that are server or db specific, buf if you have both:

You say, '#bug'.

and it displays:
Message(15,"#bug whatever usage you want here. NOTE: Use /bug for all server/db specific bugs. This is only for global eqemu bugs.");

everyone wins, the server admins do because they can track bugs and eqemu doesnt get 1000 bugs a day from users that dont know better.

[killspree]

The only problem with that is that people never read, so they'd use #bug for server-specific things.