|The Autumn logo competition is now open, please submit your entries via email to f4r. You must supply both a high-resolution PNG file and the original multi-layer source file, along with a qualifier version. Entries will be posted to the wiki as they are received, submissions will close 23:59:59 UTC on the 29th of September. This will be followed by a week-long poll. Cloverball logo: .ai .png .svg|
RigIt is another lame attempt at an Edit/save file editor for PES16 with some additional 4CC-specific options. This one is open source and should run on all platforms that are supported by Python 3 and PyQt5 (that means Windows, Linux, and Mac).
It is based on the findings collected in Edit file structure.
The current version is v0.4.0.
On the outside
Some notable features are:
- Opens/saves decrypted and encrypted Edit files.
- Allows editing every single player entry variable.
- Allows longer player names.
- Allows Editing appearance aspects that are not available in-game (e.g. glasses, transparent skin colors).
- Offers Gold/Silver Medal settings, including cards count.
- Allows batch editing medal stats across the whole Edit file.
On the inside
This might be interesting for anyone wishing to contribute or writing his own PES-related scripts:
- The underlying logic is separated from the GUI, allowing writing batch scripts and the likes.
- Designed to be extended in all kinds of ways.
- Released under the GNU GPLv3 to please the freedom loving man with the funny beard.
The following list is neither complete nor does it follow any particular order:
- Filter players by team.
- Import/export data for player stats and appearance.
- More 4CC related stuff.
- Native Edit file decrypting (currently uses pey16decrypter in a very ugly way).
- Slim down the code base and reduce need for listing the same attributes multiple times (the whole GameData structure concept looked better on paper).
- Research unknown values.
Stand-alone (slow updates)
The stand-alone releases (for Windows only) can be downloaded here.
Source (faster updates)
As building and uploading an *.exe is boring and tiresome, not every single addition or fix might be released right away. Instead, you might want to consider running the Python scripts directly.
You will need the following libraries:
- Python 3 (Python 3.4.4 was used for development)
- PyQt5 (PyQt5-5.5.1-gpl-Py3.4-Qt5.5.1 was used for development. Under Windows, you want the installer, not the 'Source Package'.)
Head over to the RigIt repository on GitHub and click Download ZIP (or, if you know what you are doing, use Git).
Now all you have to do is run the rigit.py from the RigIt directory. If you run it from the command line, you might also see additional information that gets written to the console.
Reporting Bugs / Requesting features
Please either use GitHub or the talk page.
You are free to contribute by fixing bugs, replacing ugly code, or adding your own modules. Either use pull requests on GitHub or communicate through other means, like the talk page.
Install the libraries mentioned above and get going. Use the Qt Designer (found within the PyQt installation) or Qt Creator to edit the *.ui files.
You can also just do research without writing a single line of code by completing the research on the Edit file.
Building a stand-alone .exe
The stand-alone .exe is built through py2exe (download). Run the following command from inside the RigIt directory:
python setup.py py2exe
The script will now try to pull all the necessary files from your system and create a folder with the stand-alone application. You may have to provide the pes16decrypter on your own as it is not part of the repository.
Unfortunately, the overall size is quite big. Some DLL optimizations might perhaps reduce it by a significant amount.
RigIt tries to follow PEP 0008 -- Style Guide for Python Code as closely as possible. However, probably only a fraction of its requirements are currently met.