Yeah, any pet class at low levels doubles their DPS with a halberd, which isn't TOTALLY rare. Surprised it hasn't been removed for "#reasons".

Does anyone know if the gatorsmash works on pets in p99? I know they nerfed that giant axe or whatever to not be equipable but curious if any other high dam weapons got nerfed too.

Pet will do Double the Dmg of the weapon equipped or their base dmg for a normal hit whichever is higher. There are some exceptions to this rule for lower lvl pets on certain weapons but items like executioner axe(pet would hit for 50) or gatorsmash maul(pet would hit for 60) should work on any pet of any level and would certainly make your pet super OP, on blue the weapons with dmg over 25 were a crapshoot on whether they were nerfed or not and I do not have a comprehensive list. Maul May or May not work.

For thinking low lvl Summoned pets(you don’t get items back) is probably have an ogre blacksmith forge a couple Ogre War Mauls 18dmg for pet hits of 36 for relatively cheap.

Thanks for the replies, all. Necro pets absolutely used to have a bug where their attack speed was also changed by the weapons they were holding, but I guess that's just another thing that wasn't included even though it's classic. Ah well.

So pets don’t have damage caps at certain levels? They can just start hitting for that much even at lvl 1??

It’s weird, they would and wouldn’t depending on which weapons but on blue I had a lvl 8 summoned pet running train in crushbone hitting in the 40s lol

There may be limits, but I've seen level 1 pets hit for 20-22 with the rusty halberd drops.

Yes 100% correct. Used to give the lv 49 pet FS daggers and they would hit like a truck and super fast. People could literally clear Lguk with ease. You could send the pet on the lord and the pet would mow it down like it was a lv 20 mob. That lasted a long time before they nerfed it. Not sure why this is not in the game.

Because this server is ruled by the function: max_disadvantage_to_player(classic, GM_idea).

aka: "the neckbeard function"

Having worked with eqemu now for a bit, I think a big problem for classic mechanics, as opposed to classic data changes in the DB, is that you're basically stuck recompiling the server for every era, then having to deploy that whole new batch of binaries to "implement" the era. It's a pretty big headache.

(Idea for the p99 devs):

This is the reason I went with a Docker approach for my little test server, since you can just build multiple docker images of the code with whatever compile time constants you want, then deploy them on the fly just by changing the image tag. Takes like 60 seconds.

If you wanna see how I do it:

https://github.com/dbsanfte/eqemu-server-docker

You can use Docker build-args to pass in compile time constants to the compiler (admittedly I haven't put these in the Dockerfile yet but it's trivial), then do something like:

docker build --build-arg era=0 -t eqemu-server:march-1999 .
docker build --build-arg era=1 -t eqemu-server:april-1999 .
docker build --build-arg era=2 -t eqemu-server:may-1999 .

Etc.