Fantastic idea without question. But doesn't work too well currently.
Anvil v1.1, USEnglish client/server, WoW 3.3 live. Enter a random dungeon queue. Accept and fail to get ported in because Blizzard's hamsters on the treadwheels have not been fed. Then enable Anvil via the slash command. Error is thrown up:
["message"] = "Anvil-1.1\\hammer.lua:13: bad argument #1 to 'format' (number expected, got nil)\nAnvil-1.1\\hammer.lua:13: in function <Interface\\AddOns\\Anvil\\hammer.lua:11>\n(tail call): ?:\n\nLocals:|r\nself = <unnamed> {\n 0 = <userdata>\n CHAT_MSG_SYSTEM = <function> defined @Interface\\AddOns\\Anvil\\hammer.lua:11\n}\nevent = \"CHAT_MSG_SYSTEM\"\nmsg = \"Additional instances cannot be launched, please try again later.\"\n(*temporary) = <function> defined @Interface\\AddOns\\Anvil\\hammer.lua:6\nprint = <function> defined @Interface\\AddOns\\Anvil\\hammer.lua:6\n_RETRY = \"Attempting to teleport again in %d |4second:seconds;. Write /anvil to disable.\"\n\n ---",
["type"] = "error",
["session"] = 86,
["counter"] = 2,
}, -- [87]
You get auto-ported back once. If it fails to get you in, Anvil stop trying after the first port.
Fantastic idea without question. But doesn't work too well currently.
Anvil v1.1, USEnglish client/server, WoW 3.3 live. Enter a random dungeon queue. Accept and fail to get ported in because Blizzard's hamsters on the treadwheels have not been fed. Then enable Anvil via the slash command. Error is thrown up:
You get auto-ported back once. If it fails to get you in, Anvil stop trying after the first port.