Anonymous
10/10/2025, 4:55:32 PM
No.2004243
>>2004130
The big hurdle with backporting champions is going to be getting them working on a 126 client.
Take Ahri for example. She's functional as far as the server is concerned, but she has a lot of visual issues. Her Spells don't render at all, and her little orb doesn't render correctly.
The server is targeting 126, which was released in October of 2011. Ahri was released in 131, which came out in December of 2011. So in a period of only two months, the client had received enough changes for compatibility to break.
That raises the question of approach to fix compatibility: Can we change Ahri's files to fix her rendering issues? Or does the client require modification to fix her rendering issues? Maybe it's easier to modify Ahri's files in the short term, but that's not going to be a feasible solution for all champions.
The client is going to require modification at some point. We have debug symbols for 126 so a decomp is definitely an easier task than flying blind but that's only part of the problem solved. The other half is figuring out what changed in future client versions and then backporting those changes to a 126 client without breaking existing compatibility.
The big hurdle with backporting champions is going to be getting them working on a 126 client.
Take Ahri for example. She's functional as far as the server is concerned, but she has a lot of visual issues. Her Spells don't render at all, and her little orb doesn't render correctly.
The server is targeting 126, which was released in October of 2011. Ahri was released in 131, which came out in December of 2011. So in a period of only two months, the client had received enough changes for compatibility to break.
That raises the question of approach to fix compatibility: Can we change Ahri's files to fix her rendering issues? Or does the client require modification to fix her rendering issues? Maybe it's easier to modify Ahri's files in the short term, but that's not going to be a feasible solution for all champions.
The client is going to require modification at some point. We have debug symbols for 126 so a decomp is definitely an easier task than flying blind but that's only part of the problem solved. The other half is figuring out what changed in future client versions and then backporting those changes to a 126 client without breaking existing compatibility.