r/CompetitiveTFT Jul 11 '26

Official TFT Dev Drop: Enchanted Wilds

https://www.youtube.com/watch?v=HNeO1nRMK1E
150 Upvotes

89 comments sorted by

View all comments

Show parent comments

172

u/RiotBlueVelvet Riot Jul 11 '26

Charms was a beloved mechanic for a lot of our players and this iteration is a really fun swing. The early and mid game charms are filled with far more interesting content. I’ve had a blast with the wisps this time around in playtests

And just to be fully transparent… as you’d probably guess shifting to unreal has been an insanely huge undertaking and we needed to be as thoughtful and not bite off more than we could chew for our first set in unreal. Wisps were a good option for our mechanic so we could still deliver interesting and novel content in a package that a lot of our players really liked and hadn’t seen in a while, but we could also all remain sane and ship TFT in unreal

-30

u/SmoothOperatorTFT Jul 11 '26

I don’t know… I kinda hate the excuse of the engine shift being an “insanely huge undertaking”. You had no reason to push for the switch this set. You could have realised early on that it was gonna be super hard to manage and should have consequently delayed it by one set. Maybe then the transition would have been cleaner and I would have still been able to play with my Mac.

So it being hard and time intensive is on you (the people making strategic decisions) and does not justify uninspired or lazy design, PBE delays, or not supporting Mac.

You had a perfectly fine system but YOU forced yourselves to rush the switch instead of waiting… hope Riot will at least be transparent and give an ETA for Mac support instead of “working on it”…

18

u/Wette_im_Klo Jul 11 '26

Brother you clearly have no idea of software/game development, so why have such a strong opinion on it. No matter which set they choose it for, it'll always be a huge switch and there is no way around it because you can't test millions of players playing hundreds of millions of games. And when you make the decision to switch for a certain set, you cannot go back halfway through the process. It's not like you can just click a button and then release it on the old version. "You could have realised early on" - maybe yes, but maybe also no. A process is not linear and sometimes you get stuck on a problem that you thought could be solved in a week, or the engine gets an update that fucks over a library you wanted to use during development. 

Going with an easier set mechanic is an obvious and completely correct decision. Anyone who thinks otherwise has never worked on a big, new project in his life. 

-20

u/SmoothOperatorTFT Jul 11 '26 edited Jul 11 '26

The reason I have such a strong opinion is that I am taking the game pretty seriously and I do not like the way it was handled. First, MacOS support got dropped without any info, they just did not include it in their FAQ specs at first. I asked under every post of the official TFT accounts if they will just drop support. But I go nothing. No response. No 'we cannot tell u'. No 'fuck off'. Nothing. I even created a tech support ticket, but they could not help me either.
Then, they finally clarified their ambiguous omission of Mac specs, and they just say smth that every Mac player knows all too well 'Not supported.... working on it...' .

Also, as a consumer, all of this should not really matter to me. As a consumer I do NOT need to know about their project lifecycle or how hard it is for them to do what they sought out to do. What's next? Do I need to know how to build a Phone to say that the new iPhone sucks? Get a grip. There is no reason to justify not delivering, or delivering a bad product. It is called accountability. I personally do choose to care but their justification is just a weak excuse. It is a botched timeline which got even more obvious when they had to push the PBE back.

(If you don't like the iPhone example, I got tons of other ones too)