Request old source code able to build for perfect world game

[supperfish]

Hi bros,

I really want a set of source code for version 1.3.1 of both server and client to study!

The source code should have enough resources (models, interfaces, configs..) to be able to build at least successfully.

Currently the source code of game has been updated to 1.5.3 and has been shared, so is there any way to build the older versions?

Thanks so much!

 

[junglerose]

There is no old source code , only you can do - downgrade 1.5.3 sources to 1.3.1 client , or what client you want.

 

[Bola]

I can send you the skills for 136 version, but your probably will have to work to make them compatible at 152 server

 

[jv90]

You can emulate the effects of 1.3.6 such as Insta-Cast, range bug, and individual skill bugs easier than you can find the files for it, then its just a matter of restoring the main map and monster names in Elements to be like MY-EN version naming and you are golden. I attempted this once before in 1.5.6 on pre-compiled binary before source code leaks and you can see my results here:


I since abandoned this project because the person I was making it for passed away but this technology can and does exist for new versions. you will just want to restore UI and game to the original status. Doing it this way is more secure and avoids the DUPE BUG from these versions.

There is a specific method to make the bug skills work again, and a specific method for Insta-cast.


The way I learned is by finding stock GS and ones that are modified and compare them to see what the developer changed using BeyondCompare and tools like this with IDA Pro. However now the change can be applied in source code and compiled if one wanted.


You can even customize if you want the max casting to be -99 -98 -97 or -96 version of insta-cast as well to prevent against packet senders.


If Bola has the versions of those skills already changed to how they used to be it wont be a problem but like he said you may find some compatibility issues and differences so be prepared for that. I am also interested in how the 1.3.6 skill stubs vary from the later ones.


I wanted to make a tutorial on how to do this but I forgot to back then

 

[jv90]

To follow up, I will provide here soon the method to replicate Insta-Cast as well as Skill Glitches in any version of PW for any specific skill, when I have some free time to go back in my work history and check back as to how I did it (I forgot it has been a while lol)

 

[jv90]

I have been very busy, but I will get this done soon I promise lmao

 

[hrace009]

I have been very busy, but I will get this done soon I promise lmao

Iam waiting

 

[junglerose]

there is not-full gs source code for v29 1.4.2 in pack of server side scr , if smb can add files from higher versions pls let me know.

check last posts on

Post in thread '(LF ¤SERVER¤ for) elements_13/tasks_59 (AND/OR) elements_27/tasks_68'

Nov 23, 2023

gs seems to be complete, you have to see if you have cnet and cskill, anyway you can downgrade from another version.
you will need to work on it.
Looking over it appears to have all the GS of these versions.
View attachment 243594

Can you help me with assembly gs 1.4.2 v29?

• junglerose

 

[jv90]

Iam waiting

Still very busy. I will find time this week to post a guide here in Ragezone

 

[jv90]

Iam waiting

[1.X.X]Insta-Cast

Dec 5, 2024

NOTICE: YOUR ASSEMBLY, PSUEDOCODE, AND LABELS MAY LOOK OR BE SLIGHTLY DIFFERENT, THIS DOES NOT MATTER!!!!!!!!!!!


Let's keep this as short as possible to actually achieve the effect in-game. I will go into the nuances of what our edits mean so that you can not only perform the edit but also learn how these sort of modifications work.

Note: If your GS binary file does not have debugging info aka function+variable names and **** like this when you load it into IDA you will have a very bad time, but it is still possible. I will...

• jv90
• Replies: 4
• Forum: Perfect World Tutorials

• 
• 

Test it for me and show footage if working. I wrote this from pure memory so if a few things are wrong please report them to me in the thread.

 

[jv90]

By the way, a while ago someone posted a password protected archive with 1.3.8 Source Code. Does anyone still have these files from mega? If yes, I can run some of my tools on the archives to work on processing removing the password in just 1 week or less then post on RageZone for free.

 

[tarrasque]

By the way, a while ago someone posted a password protected archive with 1.3.8 Source Code. Does anyone still have these files from mega? If yes, I can run some of my tools on the archives to work on processing removing the password in just 1 week or less then post on RageZone for free.

To view the content, you need to sign in or register

It should be this one, right

 

[jv90]

To view the content, you need to sign in or register

It should be this one, right

Thank you. I am already running my 9950x on 1/4 the RAR5 hash and 1/4 on 4090, then other pc 3900x on 1/4, and 3080 on 1/4. We will see if any results come. From the number of rar5 hashes generated it seems like a long one so we will be here at least a week.

 

[hrace009]

Thank you. I am already running my 9950x on 1/4 the RAR5 hash and 1/4 on 4090, then other pc 3900x on 1/4, and 3080 on 1/4. We will see if any results come. From the number of rar5 hashes generated it seems like a long one so we will be here at least a week.

any success yet?

 

[jv90]

any success yet?

I will post if it find anything, swapped them all to GPU after I compared gpu to cpu rates

 

[jv90]

Would any of you know why at only 4 password length, hashcat would just process only a tiny amount and then stop working?

 

[hrace009]

Would any of you know why at only 4 password length, hashcat would just process only a tiny amount and then stop working?

There are several reasons why Hashcat might process only a tiny amount of data and then stop working when dealing with 4-character passwords:

• Extremely Fast Cracking:
  
  • With only 4 characters, the potential password space is relatively small, especially if you're using common character sets (lowercase, uppercase, numbers, symbols).
  • Hashcat might crack all possible combinations within a very short time, leading you to believe it stopped working prematurely.
  • Solution: Monitor the output carefully. If the crack completes quickly, you might have missed the successful crack message.

• Resource Exhaustion (Less Likely with 4 Characters):
  
  • While less likely with such short passwords, resource exhaustion is still possible.
    • CPU/GPU Overload: If your system is under heavy load from other applications, Hashcat might not have enough processing power to continue efficiently.
    • Memory Issues: If your system has limited RAM, Hashcat might run out of memory during the cracking process.
  • Solution: Monitor system resource usage (CPU, RAM, GPU) during the Hashcat run. Close other resource-intensive applications.

• Incorrect Command-Line Arguments:
  
  • Typos or incorrect arguments in your Hashcat command can cause unexpected behavior.
  • Solution: Double-check your command-line arguments for any errors. Refer to the Hashcat documentation for the correct syntax.

• Hashcat Bug:
  
  • While rare, there might be a specific bug in the Hashcat version you're using that affects 4-character passwords.
  • Solution: Try updating to the latest version of Hashcat. If the issue persists, report it to the Hashcat developers.

• Hashcat Configuration Issues:
  
  • Incorrectly configured rules or wordlists can lead to unexpected behavior.
  • Solution: Review your rules and wordlists to ensure they are appropriate for 4-character passwords.

To troubleshoot effectively:

1. Monitor Hashcat Output: Pay close attention to the output on the console. Look for error messages, warnings, or any indication of successful cracks.
2. Check Resource Usage: Monitor CPU, GPU, and RAM usage during the Hashcat run.
3. Verify Command-Line Arguments: Double-check your command-line arguments for accuracy.
4. Test with a Simple Example: Try cracking a known 4-character password with a simple rule or wordlist to see if Hashcat works as expected in a controlled environment.

If you've checked these points and the issue persists, provide the following information for more specific assistance:

• Hashcat Version: The exact version of Hashcat you are using.
• Hash Type: The type of hash you are trying to crack (e.g., MD5, SHA1, NTLM).
• Command-Line Arguments: The exact command-line arguments you are using for Hashcat.
• Hardware Specifications: Your system's CPU, GPU, and RAM specifications.

I hope this helps! Let me know if you have any further questions.

 

[jv90]

There are several reasons why Hashcat might process only a tiny amount of data and then stop working when dealing with 4-character passwords:

• Extremely Fast Cracking:
  • With only 4 characters, the potential password space is relatively small, especially if you're using common character sets (lowercase, uppercase, numbers, symbols).
  • Hashcat might crack all possible combinations within a very short time, leading you to believe it stopped working prematurely.
  • Solution: Monitor the output carefully. If the crack completes quickly, you might have missed the successful crack message.

• Resource Exhaustion (Less Likely with 4 Characters):
  • While less likely with such short passwords, resource exhaustion is still possible.
    • CPU/GPU Overload: If your system is under heavy load from other applications, Hashcat might not have enough processing power to continue efficiently.
    • Memory Issues: If your system has limited RAM, Hashcat might run out of memory during the cracking process.
  • Solution: Monitor system resource usage (CPU, RAM, GPU) during the Hashcat run. Close other resource-intensive applications.

• Incorrect Command-Line Arguments:
  • Typos or incorrect arguments in your Hashcat command can cause unexpected behavior.
  • Solution: Double-check your command-line arguments for any errors. Refer to the Hashcat documentation for the correct syntax.

• Hashcat Bug:
  • While rare, there might be a specific bug in the Hashcat version you're using that affects 4-character passwords.
  • Solution: Try updating to the latest version of Hashcat. If the issue persists, report it to the Hashcat developers.

• Hashcat Configuration Issues:
  • Incorrectly configured rules or wordlists can lead to unexpected behavior.
  • Solution: Review your rules and wordlists to ensure they are appropriate for 4-character passwords.

To troubleshoot effectively:

1. Monitor Hashcat Output: Pay close attention to the output on the console. Look for error messages, warnings, or any indication of successful cracks.
2. Check Resource Usage: Monitor CPU, GPU, and RAM usage during the Hashcat run.
3. Verify Command-Line Arguments: Double-check your command-line arguments for accuracy.
4. Test with a Simple Example: Try cracking a known 4-character password with a simple rule or wordlist to see if Hashcat works as expected in a controlled environment.

If you've checked these points and the issue persists, provide the following information for more specific assistance:

• Hashcat Version: The exact version of Hashcat you are using.
• Hash Type: The type of hash you are trying to crack (e.g., MD5, SHA1, NTLM).
• Command-Line Arguments: The exact command-line arguments you are using for Hashcat.
• Hardware Specifications: Your system's CPU, GPU, and RAM specifications.

I hope this helps! Let me know if you have any further questions.

nah I've used hashcat a lot but this newest version with my new windows install seems to be behaving strangely