2/16/2018 12:31 AM Title: Reproduction Rate: Blocker? Details: Steps to Reproduce: User Specs: OS: Windows 10 (10.0.0) 64bit CPU: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (8) System RAM: 12212 GPU: NVIDIA GeForce GT 740 GPU RAM: 2018 SotA.EarlyAccess.QA.Win.64.628.Date.02.15.18 Area: Novia_R4_Hills01_VaubanPass Area Display Name: Vauban Pass Loc: (135.2, 27.4, -141.0) Debug: Tm92aWFfUjRfSGlsbHMwMV9WYXViYW5QYXNzfHwoMTM1LjIzLCAyNy4zOTcsIC0xNDAuOTUyKXwoMCwgLTAuNzg3LCAwLCAwLjYxNyl8MjU2LjIzNDF8MTUuMzc1Nzh8Ni4yMzk5OQ== A couple of releases ago, taming was being overhauled somewhat. There was a bug with resurrect pet, and that was fixed. The fix was to allow us to res the pet from a great distance as long as we were in the same zone. We were taught in the instructions that we merely had to target self and cast resurrect pet. This has been working fine. This saves the new pet user who has a dead pet in a very busy mob infested area to go on and res the pet from the zone entrance. But, now this is not working. For at least r50 and r51 this doesn't work. I didn't even test it in r49, so not sure when this broke. If you did this on purpose, can you please show me the detailed explanation in a release notes document? If you did not do this on purpose can you please fix it to work like the detailed notes we were given as to how to res the pet by targeting ourselves and casting res pet on ourselves.