Teamfight Tactics Dev Tracker

Yeah, my bad here, I forgot we'd swapped Rod of Mages out :(

Yep

Uh, sure, nailed it.

Definitely good call to send in that ticket. I also use the Blitz App and just confirmed that it's all good on our end.

That's a Rod of Mages, not a Rod of Ages. I'll give you one guess what it does to the unit it's put on!

Edit: Apologies folks, I'd forgotten we'd swapped Rod of Mages out as the Mage spatula item :(

Ah, I'm not the person to answer then, will have to leave that to the LoR team :)

There's been a ton of smaller stat changes on PBE, but I'm not going to start cataloging those until they are changed from something on live servers. Expect patch notes to get back to normal with patch 9.23.

Patches will roll out region by region over the next couple of days. We typically patch in the very early morning hours outside of peak play times. In NA for example, it's typically live the morning after the patch notes (Wednesday).

This is pretty much exactly the reason :)

Also just to be clear, if you tied a round both players will display with the red cross.

Combat states go away from scoreboard once the player transitions back to board after combat. The brief pause in between allows the last-to-finish players just a bit of time to evaluate the scoreboard still.

Hey all! We know that these UX and quality of life improvements not being in the patch notes has been a pain point. Going forward the UX / UI crew is making a much more concerted effort to actively get changes into patch notes so you don't have to discover them. Please poke me in the future if you feel like after some time we're still not doing a good job of raising visibility!

Oftentimes this is a matter of how pipelines and priorities for things work. What gets released to players and what is player-facing is ultimately only a certain percentage of the work we're focusing on. Some things also have a higher priority to get released earlier on, or some projects tend to be way meatier and we have to dedicate ample resources to getting those things done.

There are TONS of us who want to be able to work on the QoL stuff or fix all of the bugs. And sometimes we do get time to do these things, or people choose to spend their own time fixing up stuff that we can. The thing that is for sure is that each one of us definitely dedicates all of our work time to our players, whether visible or not! So thanks for sticking with us :)

Kinda answered this here, but tl;dr is maybe.

Same caveat as the other response I put here. We're kind of wandering out of my area of expertise here, you're asking game designer questions and I'm not the best person to ask about this. That being said the goal isn't to obscure this data, in an ideal world I'd like to see Riot be even more transparent about this. From my perspective, this isn't something I think we're trying to hide, a lot of the game designers are on Twitter talking about their thoughts on the current state of the meta. I think in an ideal world there's complete transparency about what's too strong and too weak, it's constantly updated, and there's an ongoing narrative about what the current state of the meta is and what's being done to balance the game. I think the team already does this but I'd personally like to see it done even more so. Like I mentioned before, the devs constantly talk about the balance and in the patch notes there's rational for what's changing (whether or not we as player agree is another...

We're kind of wandering out of my area of expertise here, you're asking game designer questions and I'm not the best person to ask about this. However, I think the goal is for products that use the API to promote diversity in games. There's a lot of area where we think community products can go a long way toward improving the player experience and that's where we'd like to see effort focused. There are some examples of this already; composition builders, the overlays with the rules of the game, apps that highlight the matches won, apps that show your ranked journey. These are the kinds of apps that extend the experience and make TFT more enjoyable.

EDIT: I want to clarify a bit after re-reading your question. I think players will always form an opinion of what's good and bad and likely stick to those decisions. There's nothing wrong with that. But if an app is sending a message to player that anything but Nobles is a mistake, that's an issue for us. We'd li...

Good question. If you read the article, we dive into some of the policy we're creating for community sites making tools for TFT. You'll notice a lot of what we talk about is how tools can start to change the way the game is designed to be played. At a high level, in the article, we discuss reducing diversity, giving competitive advantages, and making decisions for players. All these things are bad from a gameplay perspective so we want to make sure we're exposing data so that community sites can make cool things for players while also ensuring these policies are being adhered to.

Your question was asked in the Developer Dis...

Hmm are you finishing in 8th?

Oh there's a lot to this question, I'll try and his the high level parts. All good questions though.

I don't necessarily think there's one right way to do things, as in most of software engineering there are tradeoffs to everything so it really just depends on your circumstances/constraints to determine which path you take to creating an API. You might ETL all this data into a separate data store for the API if isolation is a concern. You might make two separate APIs if you need to. It all kind of depends on your requirements.

Theory first. I personally like it when the client or primary product uses the same APIs as as made available to the public and the only difference is the permission set (in something like OAuth this means scopes). In general, creating a product that is API first ensures that the API is never an after thought and the product is designed in way for the data to be sharable while still meeting the product needs. If you do take a different approac...

There are a couple teams involved in making TFT match history a thing. My team focuses on making this data available through the API so that community sites can make tools that are useful to players while still remaining conscience of the gameplay (hence some of the policy in the announcement).

We're aiming to have this data in the API soon, so we're sharing the schema but the priority will be making sure it's stable in the client before it gets added to the API. I'm happy we're finally getting match history as well, the TFT team is moving at an incredible pace from what I've seen. They got a lot of plates spinning and I'm just happy to help where I can to get the value to you all, the players.

Ooh something I'm working on is on reddit. My day has come. Lmk if you have any questions related to the Riot Games API.