Yay patch. 
Linux has a decent chance in the future, Mac is improbable.
However… Since GameSparks deprecated their SDK, Unity 2019.1 will be our final version for Throne unless we port in the future. Porting will take months, cost more money, and have restrictions. I’d rather stay.
So… It depends if GS (now Amazon) decides to migrate their SDK to support .net 4.x+ (now required for Unity 2019.2+) – assuming that a future version of Unity will have better IL2CPP support for building from Windows.
1 Like
YAY FINALLY ! New classes ! New gameplay mechanics !
Oh wait… 
1 Like
We’ve mentioned multiple times the code we got was unreadable and we had to fix it making it more readable and scalable. We’re hoping we’ll be able to get a balance patch soon.
1 Like
He probably assumed that they are removed from the reaped players too - then if you scouted someone who was reaped you’d know he was reaped because you got a notification the scout was removed, even though the player seems alive.
But I’d assume that’s not the case and it happens on the “visible” death. Am I correct in that assumption? 
2 Likes
Sheriff and Mercenary receive a feedback on dead target and thus scout/shield wore off
Target is alive
There is a reaper
nice
1 Like
Sorry was busy and forgot to answer. No, it only removes it when the player is visibly dead.
Maybe it’s just me but throwing this much shade this constantly at the previous programmer is just in bad taste.
It doesn’t really matter how true it is or what else has happened internally - if an outside observer can look and see you blaming a past dev (who was known for fast balance patches) for an essential lack over a much longer period of time, that’s always going to just look bad.
I know you guys know where I stand on this past programmer, and I know the shakeup has caused understandable delays. But it’s just poor for your image to keep pushing this angle, and I know you’re all above that.
Just my two cents.
3 Likes
Thanks for your advise. It will or will not be followed.
It’s just really frustating for a junior dev to have to deal with this mess of a code.
I didn’t even mention the previous dev in the post you replied to. The only reason we do mention it when we do, is because people keep blaming us (mostly Dylan) about the delay, bugs etc, when in fact that’s not quite true. I don’t wanna drag this, but it’s only mentioned when people keep yelling at us for someone else’s mistakes.
That said, if you want to continue this conversation, message me, because it’s both irrelevant to the patch notes and doesn’t have to be public.
1 Like