The "Mercenary failed to spawn!" error

[CruelCahal]

Is this just me, having this problem? Since before the Lua switch, they were working and I don't know if you dev guys know about it, are addressing it, have no problems with it, or whether it's just me.
I know the liasons are set at class_id "1" now and that the merc hire window doesn't even pop up unless reset back to the old "71" value, then that's when the error message comes up.
Recent compiles + daily peq build = error
Recent compiles + my old SVN-based PEQ = error
Pre-Lua compile + my old SVN-based PEQ = no error

I found this in an old post:

In the meantime, here's a list of valid merc status update IDs. The packet is used on the client and server, whereas the client sends different data than the server packet. It's not just used for hiring as you can see below:

// [OPCode: 0x5e78 (OP_MercenaryHire?)] On Live as of April 2 2012
/*
Valid response IDs:

0 - Hire me! (Assign Merc after sending this.)
1 - Insufficient money message.
2 - Mercenary-To-Hire does not exist in the server's DB.
3 - Mercenary failed to spawn. (this actually tells us the mercenary should spawn BEFORE recieving this packet.)
4 - Mercenaries not allowed in raids.
5 - You already have a mercenary request pending
6 - You must dismiss the mercenary before hiring a new one.
7 - You must dismiss your suspended one before hiring a new one.
8 - Group is full.
9 - Error creating mercenary
10 - Replacing mercenary(?!)
11 - Your mercenary has quit! You ran out of money to pay for your mercenary!
12 - Your mercenary waived an upkeep cost of %d plat, and %d gold and your mercenary upkeep cost timer has been reset to %s. <-- these values are for GM resets of mercenaries and are generated from the client's
mercenary info. NOT from the packet.
13 - Your mercenary is about to be quit due to insufficient funds! <--- Sent before the mercenary quits, unsure of time sent before.
14 - There is no mercenary liason nearby! <-- hacking attempt check if no mercenary merchant is in the zone!
15 - You are too far away from the liason! <-- Liason exists as type in the zone, but client is too far away. (position update happened)
16 - You do not meet the requirements for that mercenary! <-- For example, if a mercenary is 'unlocked' in some way, send this if they do not have the mercenary unlock.
*/

If it's an opcode issue, I have no clue whether it's my fault or not, I'm not a coder like you guys.
I'm sorry to be a pest, but I really prefer mercs to bots and I miss having them.