search

RiotGames / developer-relations

Riot Games Developer Ecosystem Bug Reporting
http://developer.riotgames.com
746 stars 44 forks source link

v4 announcements were on old forum which is now dead. #34

Closed Pyrolistical closed 5 years ago

Pyrolistical commented 5 years ago

For example, we cannot read this https://discussion.developer.riotgames.com/articles/6579/player-universally-unique-identifiers-and-a-new-se.html which is critical for those moving from v3 to v4

Pyrolistical commented 5 years ago

Found the link https://www.riotgames.com/en/DevRel/player-universally-unique-identifiers-and-a-new-security-layer

The old url should redirect to new one

Pyrolistical commented 5 years ago

Another example is https://discussion.developer.riotgames.com/questions/4269/verification-system.html which is linked from https://developer.riotgames.com/api-methods/#third-party-code-v3

Pyrolistical commented 5 years ago

Also on discord:

Botty McBotFace: Hey there! I'm Botty, let me be the first to welcome you to the Riot API Discord :)

Here's some tips to help you on your way:

  1. There's a good chance the AnswerHub already has an answer for you. Be sure to search there, it will help you much faster. https://discussion.developer.riotgames.com/
Derpthemeus commented 5 years ago

Botty has been updated (https://github.com/Querijn/BottyMcBotface/commit/3bf77c9c3c729d4c3d00649e51385ccbf70ab3fc) and will be redeployed later

Querijn commented 5 years ago

Botty has been redeployed.

RiotTuxedo commented 5 years ago

Twitter and Discord are the most reliable places to hear about any recent announcements. Both these locations have been updated with the correct link.

The announcements themselves can be found here: https://www.riotgames.com/en/DevRel

I've posted a banner on the Developer Portal and each user will receive an update upon login. I've also added/updated the notes on the v3 APIs on the Reference page.

At this time, the old urls don't redirect to the new ones, however with the updates listed above I believe the deprecation announcement is easily discoverable. With that I'm closing out this issue as resolved. Let me know if you have additional concerns.