RPCS3 trophies

[Richtoon]

Just got this from RPCS3 Discord, they seem have improved the trophy system and now we can search players and view their trophies on website, so I thought Exophase should add RPCS3 trophies on here as well?

 

[PoshestPoro]

I agree, I was just about to post the same thing. Would be cool to see I just worry about duplicating already existing achievements so they may need to be marked with like rpcs3 in the title - depends how the current database works.

 

[NoHeroes94]

Again, about to post the same thing. This would be really awesome to see as I'd heavily consider hunting on RPCS3

 

[Retodon8]

Neat. Mentioned on their blog as well. Seems to work with RPCN, their PSN replacement. I haven't tried this yet... I should. A very quick search doesn't give me anything about an API, which would be great if it existed, because scraping is... more complicated.

Exophase could start with adding links to RPCN profiles on our Exophase profiles. URLs look like: https://rpcs3.net/rpcn-profile?username=Ani

 

[PoshestPoro]

I will ask in the RPCS3 discord if there is an api for RPCN.

 

[PoshestPoro]

Here's some slop summarizing the endpoints:Based on the code, here are the accessible endpoints for the stats server:

Stat Server Endpoints​

The server listens on a configured path (default: /{config.stat_server_path}) and supports these GET endpoints:

1. Usage Endpoint
   • /{path}/usage
   • Returns JSON with current game tracker statistics (number of users, PSN games, ticket games with name hints)

1. Score Endpoints
   • /{path}/score/{com_id}
     • Returns JSON array of all score tables for a given communication ID (game)
   • /{path}/score/{com_id}/{table_id}
     • Returns JSON object with scores for a specific game and leaderboard table

1. Trophy Endpoints
   • /{path}/trophy/{comm_id}
     • Returns JSON with trophy statistics for a game (unique player count and earner counts per trophy)
   • /{path}/user/{npid}/trophies
     • Returns JSON array of all trophies earned by a specific user (NPID)

Key Features​

• Caching: All endpoints (except user trophies) support configurable cache TTL via cache_life setting
• Request Validation:
  • Communication IDs must be exactly 20 characters
  • NPIDs must contain only alphanumeric characters, hyphens, and underscores
  • Only GET requests are accepted
• Response Format: All responses are JSON with Content-Type: application/json header
• Response Sanitization: String fields are sanitized to escape special JSON characters (quotes, backslashes, control characters)
  
  Here is what I could find in the discord already. I don't know how reliable this information is as it is described as "slop" but it could be worth experimenting with.
  
  Seems mostly useless from what I can see, at least through web requests.