Yes, this would fix the problem for gem summons (and rendering them no longer demi-summons). It's absurd SE even made them on the demi system in the first place given this godawful mechanic has been infesting Summoner for five years by then.
You aren't understanding what the problem is. It's not because carbuncle exists. It wouldn't matter if you could have 2 pet entities active at a time, or if you deleted Carbuncle. Ghosting happens because a pet has a hard cut in its existence, which is how all demi/gem summons operate. They can only exist for a strict time period before dying, and any commands they have at that point are now lost.
I've lost banana/phoenix autos because it decided to walk 10 feet to me during a mechanic or because its current target died and it didn't relock until my next GCD. I've lost entire gem summons because the add in Hydaelyn died and the gem summon refused to relock onto the next one before despawning or gem summons in raids when the boss jumps and goes untargetable before the gem summon actually does it's attack well after you push the GCD. None of these have anything to do with Carbuncle.
Would making 2 pet entities make it easier to use Radiant Shield and stop carbuncle from ghosting? Yes.
Would it stop all ghosting from happening? No.
Ghosting is endemic to how Demi/Gem summons are designed. You cannot 'fix' it. Ghosting will always exist for as long as demisummon mechanic exists. You can see in my above reply the easiest way to prevent gem summons from ever having the ability to ghost is to... not make them work like demisummons. You can bend over backwards ripping out everythinig from Summoner to make it less likely to happen, but you can never fix it so that ghosting will not occur at some point.
Delete demisummoning. Replace it with something else that isn't infested with this problem.



Reply With Quote


