I have been working on this for about two weeks now and getting momentum so I will be posting pictures and will be taking feedback. The project is in Laravel with a few additional things like Angular and Jquery. The program is completely reactive, there is no update button and few page postbacks. For most things it is saved every few seconds or during particular events. Grids are fed via Ajax. I have no idea how long it will take me, there are a shitload of pages left to be done still. I am not rushing so hopefully I will catch many of the bugs before it is released to the public.

A few screenshots.

this looks awesome, thanks for all your hard work

just curious, when you say public
will it be something that we use a common one, and it connects to our db
or something we would install on our own website

I will have a git repository for everyone. I could not imagine trying to host multiple copies as a service and go back to your database, the latency would ruin the experience. Right now it is insanely fast doing complex things. The beauty will be the utility tab when it is done. I cannot imagine the cool shit that I will put in there. Removing duplicate spawns, removing all pets in the database with one click, things like that. It has a long way to go but most of my big hangups were figuring out structure and figuring out Angular UI grid. For some reason Angular documentation on the UI Grid is sparse at best. There will have to be two different copies maintained, well possibly. My database is structured different than official. I will figure out how I am doing that during release.

It will be up to the higher ups if they use this or stick with what they have. I am just going to offer it up, what everyone does with it is up to them.

what will the host need to be and software needed to support it so i can get prepared with a new VM

I am doing the write up on Debian. I have been a Debian guy for 10+ years now. I will have a step by step installation available for the latest release when I am done. Maybe even a script, I like scripts. I may do a build for Docker in the future, not sure.

The big plus here is that right after it is done I will be using it like crazy. So any bugs that are found will probably be by me from tons of use.

Did this one today, the waypoint page. My waypoints are a bit different, I store them in the database. Do not mind the random coordinates.

when you refer to waypoint is that for the movement loops

No. I still use scripts for those. I am talking for designated movement, not so much as generic random loops. Imagine you have a guard that patrols a city, that type of thing.

This was my solution.

viewtopic.php?f=3&t=4031&p=30794&hilit=waypoint#p30794

This one was a little challenging. Again, my database is a bit different. I added a way to search for existing loottables and add your current spawn to it. You can lookup the item right on the page and add it, it searches as you type.

This looks amazeballs! Thank you for doing this. EQ2DB Editor 1.0 is 11 years old, and was never quite done right (nor ever finished hah) so it's cool to see new dev toys available in 2019.

I should be done in around 4 weeks. I am estimating it a little high so I can do a security scan on it.

Cleaning up some of the code today, doing refactoring. I do not know how well this works for everyone, but the appearance list is quite long. I am not sure how everyone finds an appearance now other than doing a raw query, but my solution was some input boxes. Basically just type in your filter terms and the dropbox (marked in red), filters down to match your filter text. The dropbox is filtered as you type via AJAX query.

Spawn script editor.

Editor looks great.

For scripts I would recommend a syntax highlighter. Personally I use ace in eq2db2 as it was simple to set up and can even do simple error checks on the scripts.