Hi, I have encountered an issue regarding the maintainability of the 2006Scape Client folder: some of the classes, methods and variables do not have proper names that describe their functionality (having names such as "Class18", "method10" or "anInt273" for example). I am aware that this is due to them being decompiled. However, in the event that any issue there had to be fixed or a new feature implemented, it would be nigh impossible considering the great difficulties in understanding them.
Originally created by @Yabarta on GitHub (Feb 25, 2025).
Original GitHub issue: https://github.com/2006-Scape/2006Scape/issues/665
Hi, I have encountered an issue regarding the maintainability of the 2006Scape Client folder: some of the classes, methods and variables do not have proper names that describe their functionality (having names such as "Class18", "method10" or "anInt273" for example). I am aware that this is due to them being decompiled. However, in the event that any issue there had to be fixed or a new feature implemented, it would be nigh impossible considering the great difficulties in understanding them.
Not a trivial job at all :) But in all seriousness, the idea itself is maybe good, but I think it could require quite a lot of debugging and coming up with various names for the variables, etc.. and even then, nobody would be sure, whether the responsibility of said "Class18" or whatever would actually make sense and would be responsible just for that named thing (my opinion)
<!-- gh-comment-id:3141456755 -->
@AugustasK commented on GitHub (Jul 31, 2025):
Not a trivial job at all :) But in all seriousness, the idea itself is maybe good, but I think it could require quite a lot of debugging and coming up with various names for the variables, etc.. and even then, nobody would be sure, whether the responsibility of said "Class18" or whatever would actually make sense and would be responsible just for that named thing (my opinion)
<!-- gh-comment-id:3142142809 -->
@Ddemon26 commented on GitHub (Aug 1, 2025):
i have already Finished with this request, just got to finish breaking down the Game.java class from 14k lines to 2k lines. (only took a month xD)
https://github.com/Ddemon26/2006Scape/tree/Game-Class-Breakdown
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Yabarta on GitHub (Feb 25, 2025).
Original GitHub issue: https://github.com/2006-Scape/2006Scape/issues/665
Hi, I have encountered an issue regarding the maintainability of the 2006Scape Client folder: some of the classes, methods and variables do not have proper names that describe their functionality (having names such as "Class18", "method10" or "anInt273" for example). I am aware that this is due to them being decompiled. However, in the event that any issue there had to be fixed or a new feature implemented, it would be nigh impossible considering the great difficulties in understanding them.
@Ddemon26 commented on GitHub (Jul 1, 2025):
i got you
@AugustasK commented on GitHub (Jul 31, 2025):
Not a trivial job at all :) But in all seriousness, the idea itself is maybe good, but I think it could require quite a lot of debugging and coming up with various names for the variables, etc.. and even then, nobody would be sure, whether the responsibility of said "Class18" or whatever would actually make sense and would be responsible just for that named thing (my opinion)
@Ddemon26 commented on GitHub (Aug 1, 2025):
i have already Finished with this request, just got to finish breaking down the Game.java class from 14k lines to 2k lines. (only took a month xD)
https://github.com/Ddemon26/2006Scape/tree/Game-Class-Breakdown