1. Home
  2. t0xic0der

T0xic0der's Projects

t0xic0der/gi-loadouts

Screenshots On GNU/Linux distributions Light mode - Dash Light mode - Result Dark mode - Dash Dark mode - Result On Microsoft Windows Light mode - Dash Light mode - Result Dark mode - Dash Dark mode - Result Disclaimer The "Loadouts for Genshin Impact" project, also known as "GI Loadouts", fully adheres to the terms of services and the regulations regarding third-party software established by MiHoYo for Genshin Impact. This ecosystem application is safe for users, as its unmodified usage strictly avoids any violations, including but not limited to those outlined below. This ecosystem application DOES NOT exploit the game This ecosystem application DOES NOT need Genshin Impact to be present on the computer on which this runs on. This ecosystem application DOES NOT help achieve artificial in-game progress This ecosystem application DOES NOT interact with Genshin Impact game assets or game process for facilitation. This ecosystem application DOES NOT help selling or exchanging accounts This ecosystem application DOES NOT explore beyond its primary purpose of helping manage custom player loadouts. This ecosystem application DOES NOT help topping up via unofficial channels This ecosystem application DOES NOT need an active internet connection for its intended functionality to work. With an extensive suite of over 1420 diverse functionality tests and impeccable 100% source code coverage, we proudly invite auditors and analysts from MiHoYo and other organizations to review our free and open source codebase. This thorough transparency underscores our unwavering commitment to maintaining the fairness and integrity of the game. The users of this ecosystem application can have complete confidence that their accounts are safe from warnings, suspensions or terminations when using this project. The ecosystem application ensures complete compliance with the terms of services and the regulations regarding third-party software established by MiHoYo for Genshin Impact. Download Optical Character Recognition The project depends on the Tesseract OCR project to be able to scan in-game screenshots using the Optical Character Recognition technology. As such, please ensure that the Tesseract OCR application is installed and configured properly. On GNU/Linux distributions Install Tesseract OCR from your default package manager. $ sudo dnf install tesseract Make note of the place where the Tesseract OCR executable binary is placed. /usr/bin/tesseract On Microsoft Windows Install Tesseract OCR from the UB Mannheim GitHub namespace. https://github.com/UB-Mannheim/tesseract/wiki Make note of the place where the Tesseract OCR executable binary is placed. C:\Program Files\Tesseract-OCR\tesseract.exe Releases Stable Releases for the general usability purposes can be found here. Nightly Releases for the testing debugging purposes can be found here. Package Releases that automatically update can be found here. Usage Select the vision from the dropdown menu to quickly locate the character that you wish to manage the equipment for. Select the character from the dropdown menu aligned with the element that was selected previously. Select the level of the character constellation from the dropdown menu and statistics of the character will be calculated automatically. Select the level of the character experience from the dropdown menu and the statistics of the character will be calculated automatically. Quickly switch over to either of the travelers, Lumine or Aether from the character menu using the VENUS or MARS buttons respectively. Once the character is selected from the dropdown menu, the compatible weapon type is automatically selected. Select the weapon of your choice from the dropdown menu that you want to equip. Select the rank of the weapon refinement from the dropdown menu and the statistics of the weapon will be calculated automatically. Select the level of the weapon experience from the dropdown menu and the statistics of the weapon like will be calculated automatically. Load the weapon equipment from your local storage by using the LOAD button beside the sections. Save the weapon equipment to your local storage by using the SAVE button beside the sections. Once the weapon has been configured, configure the artifacts by selecting the artifact set from the dropdown menu. Select the quality associated with the artifact sought from the dropdown menu so that the possible levels are populated. Select the level of the artifact experience from the dropdown menu. Select the primary stat of the artifact from the dropdown menu and the statistics of the artifact will be calculated automatically. Select the secondary stats of the artifact from the dropdown menu from each distribution area. Enter the value associated with the secondary stats of the artifact from the dropdown menu from each distribution area. Alternatively, import the statistics from artifact units from in-game screenshots by using the SCAN buttons beside the distribution areas. Load the in-game screenshot of the artifact units into interface using the LOAD button. Alternatively, the in-game screenshot of the artifact units can be inserted from the clipboard by pressing CTRL + V. Alternatively, the in-game screenshot of the artifact units can be inserted by using the drag and drop action. Please note that the supported image formats include, but are not limited to, the following. Bitmap [image/bmp] [BMP] Graphics Interchange Format [image/gif] [GIF] Tagged Image File Format [image/tiff] [TIF] Truevision TGA [image/x-tga] [TGA] Open Document Drawing [application/vnd.oasis.opendocument.graphics] [ODG] Icon [image/x-icon] [ICO] Portable Network Graphics [image/png] [PNG] Joint Photographic Experts Group [image/jpeg] [JPG] WebP Image [image/webp] [WEBP] Photoshop Document [image/vnd.adobe.photoshop] [PSD] Please note that the unsupported image formats include, but are not limited to, the following. Scalable Vector Graphics [image/svg+xml] [SVG] Encapsulated PostScript [application/postscript] [EPS] Confirm if the correct Tesseract OCR executable is selected by using the LOCATE button. Wipe the in-game screenshot of the artifact unit from the configuration area by using the WIPE button. Import the statistics of the detected artifact unit by using the IMPORT button. Wipe the statistics of the detected artifact unit by using from the configuration area by using the WIPE button. Wait for the statistics to be read from the in-game screenshot of artifact using Optical Character Recognition or OCR. Make corrections wherever the application was unable to correctly recognize statistics of the artifact before importing them. Confirm if better scanning results are obtained for the statistics of the artifact from the details screen. Confirm if better scanning results are obtained for the statistics of the artifact from the inventory screen. Confirm if better scanning results are obtained for the statistics of the artifact from the enhancement screen. Alternatively, load the artifact units from your local storage by using the LOAD buttons beside the distribution areas. Save the artifact units to your local storage by using the SAVE buttons beside the distribution areas. Wipe the artifact units from the configuration area by using the WIPE buttons beside the distribution areas. Read the artifact bonuses available to the character when using two pieces or four-pieces of a certain artifact set. Load the artifact sets from your local storage by using the LOAD buttons beside the distribution areas. Save the artifact sets to your local storage by using the SAVE buttons beside the distribution areas. Wipe the artifact sets from the configuration area by using the WIPE buttons beside the distribution areas. Calculate the character potential with the equipped artifact units or sets and weapon. View the calculations of the character potential on the newly created dialog box. View the help details about the application by clicking on the HELP button from the user interface. View the info details about the application by clicking on the INFO button from the user interface. View the homepage of the project by clicking on the FORK button from the user interface. Report software errors or feature requests by clicking on the REPORT button from the user interface. Donate to the project by clicking on the HEART button from the user interface. Development On GNU/Linux distributions Ensure that the necessary packages are available on the operating system installation. $ sudo dnf install git tesseract $ sudo dnf install python3 python3-pip python3-virtualenv poetry Clone your fork to the local storage and make it your current working directory. $ git clone https://github.com/gridhead/gi-loadouts.git $ cd gi-loadouts Create a virtual environment and activate it for installing project dependencies. $ virtualenv venv $ source venv/bin/activate Install the project dependencies after verifying the correctness of the configuration. (venv) $ poetry check (venv) $ poetry install Start the application after verifying that the dependencies have been installed. (venv) $ poetry show (venv) $ gi-loadouts Once done with making changes in a separate branch, make a pull request to contribute. On Microsoft Windows Ensure that the necessary packages are available on the operating system installation. Git - https://git-scm.com/downloads Tesseract - https://github.com/UB-Mannheim/tesseract/wiki Python 3 - https://www.python.org/downloads/ Poetry - https://python-poetry.org/ Clone your fork to the local storage and make it your current working directory. PS > git clone https://github.com/gridhead/gi-loadouts.git PS > cd gi-loadouts Create a virtual environment and activate it for installing project dependencies. PS > py -m venv venv PS > .\venv\Scripts\activate Install the project dependencies after installing the dependency management tools. (venv) PS > py -m pip install poetry (venv) PS > poetry install Start the application after verifying that the dependencies have been installed. (venv) PS > poetry show (venv) PS > gi-loadouts.cmd Once done with making changes in a separate branch, make a pull request to contribute. Contribution You can help our efforts by Star the project repository Starring our project repository on GitHub not only helps us witness your support and boost the visibility for the project but it also motivates us to continue improving and expanding our efforts. Report the experienced errors If you encounter any errors that should be taken care of, please file them as issue tickets on our issue tracker to help us identify problems as it is when we will be able to address the problems. Propose the intended features If you have any ideas that should be introduced in the project, please file them as issue tickets on our issue tracker to help us understand the direction you want the project to take in the future. Document the project repository Facilitating a comprehensive project documentation not only enhances the project repository but it also vital for the project's growth among users and project's approachability among developers. Write the project codebase Consider opening a pull request against the project repository to contribute to the project codebase whether it is for fixing errors, adding features, amending documentation or modifying assets. Sponsor the project maintainers By providing financial support, the maintainers have the means to dedicate more efforts into the development of the project codebase and ensure compatibility from each upcoming Genshin Impact release. Disclaimer All rights to Genshin Impact assets used in this project are reserved by miHoYo Ltd. and Cognosphere Pte., Ltd. Other properties belong to their respective owners.
  • Fedora 42 : aarch64, x86_64
  • Fedora 43 : aarch64, x86_64
  • Fedora rawhide : aarch64, x86_64

t0xic0der/syncstar-test

syncstar-test
  • Centos-stream 10 : aarch64, ppc64le, s390x, x86_64
  • Fedora 41 : aarch64, ppc64le, s390x, x86_64

t0xic0der/syncstar

SyncStar Guest operated service for creating bootable USB storage devices at any community conference kiosk Screenshots Features For development Minimal command line interface based configuration with wide range of customizable options Stellar overall codebase quality is ensured with 100% coverage of functional backend code Over 34 checks are provided for unit based, end-to-end based integration based codebase testing GitHub Actions and Pre-Commit CI are enabled to automate maintenance of codebase quality For consumption Asynchronous multiprocessing allows for flashing multiple storage devices simultaneously Programming standards and engineering methodologies are maintained as much as possible Frontend is adaptive across various viewport types and browser-side assistive technologies Detailed documentation for both consumption and development purposes are readily provided Installation For development Install the supported version of Python, Virtualenv, Poetry, Redis and CoreUtils on your Fedora Linux installation. $ sudo dnf install python3 python3-virtualenv poetry $ sudo dnf install redis coreutils Clone the repository to your local storage and make it your present working directory. $ git clone https://github.com/gridhead/syncstar.git $ cd syncstar Establish a virtual environment within the project and activate it for installing dependencies. $ virtualenv venv $ source venv/bin/activate Check the validity of the project configuration and install the dependencies from the lockfile. (venv) $ poetry check (venv) $ poetry install For consumption Install the supported version of Python, Python Package Installer Redis CoreUtils on your Fedora Linux installation. $ sudo dnf install python3 python3-pip $ sudo dnf install redis coreutils Elevate the privileges to the superuser level and install the syncstar package from Python Package Index. $ sudo -s # pip3 install syncstar Configure the service unit files for the endpoint service and worker service to the system services directory. $ sudo wget https://raw.githubusercontent.com/gridhead/syncstar/main/syncstar/system/endpoint.service -O /etc/systemd/system/ss-endpoint.service $ sudo wget https://raw.githubusercontent.com/gridhead/syncstar/main/syncstar/system/worker.service -O /etc/systemd/system/ss-worker.service Enable the service unis for the endpoint service and worker services. $ sudo systemctl enable ss-endpoint.service $ sudo systemctl enable ss-worker.service Initialization Download the Fedora Linux live images to a certain directory and make the images archive configuration file. $ wget https://download.fedoraproject.org/pub/fedora/linux/releases/40/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-40-1.14.iso $ cp Fedora-Workstation-Live-x86_64-40-1.14.iso /etc/syncstar/images/Fedora-Workstation-Live-x86_64-40-1.14.iso Download the images archive configuration file and make changes to include the recently downloaded image files. $ wget https://raw.githubusercontent.com/gridhead/syncstar/main/syncstar/config/images.yml -O /etc/syncstar/images.yml $ nano /etc/syncstar/images.yml Set the value of the following environment variable as the present location of the images archive configuration file. $ nano /home/$(whoami)/.bashrc $ export SYNCSTAR_ISOSYAML=/etc/syncstar/images.yml Enable the Redis service unit and check the status of the service. $ sudo systemctl enable redis.service $ sudo systemctl status redis.service Execution For development Ensure that the Redis service unit is active and check the status of the service. $ sudo systemctl start redis.service $ sudo systemctl status redis.service In a separate terminal session, execute the following command to start the endpoint service in an activated virtual environment. $ source venv/bin/activate (venv) $ syncstar --port 8080 --repair false --period 2 --images $SYNCSTAR_ISOSYAML This will start the endpoint service on port 8080 available across all network interfaces of the host device. The debug mode for the endpoint service will be disabled and the information would be refreshed after 2 seconds. The images archive configuration file mentioned previously will be used as a source for the live images. Dictionaries consisting of task schedules will not persist after a live reload when using the debug mode. In a separate terminal session, execute the following command to start the worker service in an activated virtual environment $ source venv/bin/activate (venv) $ sudo SYNCSTAR_ISOSYAML=/etc/syncstar/images.yml celery -A syncstar.task.taskmgmt worker --loglevel=info This will start the worker service that would accept tasks requested by the users of the endpoint service. The debug mode for the worker service will be disabled and there will be a default concurrency of 12 processes. The images archive configuration file mentioned previously will be used as a source for the live images. Dictionaries consisting of task schedules will not persist after a live reload when using the debug mode. Visit the homepage of the endpoint service using the browser of your choice to get started with using SyncStar. For consumption Ensure that the Redis service unit is active and check the status of the service. $ sudo systemctl start redis.service $ sudo systemctl status redis.service Start the endppint service unit and check the status of the service. $ sudo systemctl start ss-endpoint.service $ sudo systemctl status ss-endpoint.service Start the worker service unit and check the status of the service. $ sudo systemctl start ss-worker.service $ sudo systemctl status ss-worker.service Visit the homepage of the endpoint service using the browser of your choice to get started with using SyncStar. Organization The images archive configuration file stores an unordered dictionary of images archives available for usage. $ cat /etc/syncstar/images.yml The identifier for the images archives is the message digest text which can be found out using the following command. $ cat Fedora-Workstation-Live-x86_64-40-1.14.iso | sha256sum The second line per images archive entry stores the location of the file which is validated on every task run. path: /home/archdesk/Downloads/Fedora-Workstation-Live-x86_64-40-1.14.iso The third line per images archive entry stores the name that would be displayed to the users on the service frontend. name: Fedora Linux 40 Workstation rc1.14 The fourth line per images archive entry stores the type that would be used for metadata generation purposes. type: fedora The images archive that have not been provided with one of the supported types would be provided with the generic type. type: common The images archive should be verified for their consistency by the service administrators before consumption. $ wget https://download.fedoraproject.org/pub/fedora/linux/releases/40/Workstation/x86_64/iso/Fedora-Workstation-40-1.14-x86_64-CHECKSUM The following types of images archive are supported for metadata generation purposes used on the service frontend. | # | Name | Identity | Icon | |----|--------------------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------| | 1 | Android | gdroid | | | 2 | Arch Linux | archlx | | | 3 | CentOS Stream | centos | | | 4 | Debian Linux | debian | | | 5 | Fedora Linux | fedora | | | 6 | Kodi or XBMC | kodimc | | | 7 | Linux Mint | lxmint | | | 8 | Manjaro Linux | mnjaro | | | 9 | Red Hat Enterprise Linux | redhat | | | 10 | OpenSUSE Linux | opsuse | | | 11 | Ubuntu Linux | ubuntu | | | 12 | Generic | common | | Appreciation If you like the efforts made here and want to support the development of the project, please consider giving a star to the project and forking it your namespace. I appreciate all kinds of contributions - ranging from small sized bug fixes to major sized feature additions as well as from trivial documentation changes to awesome codebase refactoring. Even if you do not have the capacity to take the development for a spin, you can help me out by testing out the project and getting in touch with me on the issue tracker with the things that must be fixed and the things that should be introduced.
  • Fedora 41 : aarch64, ppc64le, s390x, x86_64
  • Fedora 42 : aarch64, ppc64le, s390x, x86_64
  • Fedora 43 : aarch64, ppc64le, s390x, x86_64
  • Fedora rawhide : aarch64, ppc64le, s390x, x86_64

t0xic0der/pagure-exporter

Simple exporter tool that helps migrate repository files, data assets and issue tickets from projects on Pagure to GitLab
  • Fedora 41 : aarch64, ppc64le, s390x, x86_64
  • Fedora 42 : aarch64, ppc64le, s390x, x86_64
  • Fedora 43 : aarch64, ppc64le, s390x, x86_64
  • Fedora eln : aarch64, ppc64le, s390x, x86_64
  • Fedora rawhide : aarch64, ppc64le, s390x, x86_64

t0xic0der/firmitas

Simple notification service for X.509-standard TLS certificate statuses
  • Centos-stream+epel-next 9 : aarch64, ppc64le, s390x, x86_64

t0xic0der/packaging-automation

Automating package testing and building using Packit and COPR
  • Centos-stream 8 : aarch64, ppc64le, x86_64
  • Centos-stream 9 : aarch64, ppc64le, s390x, x86_64
  • Custom 1 : i386, x86_64
  • EPEL 7 : ppc64le, x86_64
  • EPEL 8 : aarch64, ppc64le, s390x, x86_64
  • EPEL 9 : aarch64, ppc64le, s390x, x86_64
  • Fedora 41 : aarch64, i386, ppc64le, s390x, x86_64
  • Fedora 42 : aarch64, i386, ppc64le, s390x, x86_64
  • Fedora 43 : aarch64, i386, ppc64le, s390x, x86_64
  • Fedora eln : aarch64, ppc64le, s390x, x86_64
  • Fedora rawhide : aarch64, i386, ppc64le, s390x, x86_64
  • Mageia 8 : aarch64, i586, x86_64
  • Mageia cauldron : aarch64, i686, x86_64
  • openSUSE Tumbleweed : aarch64, i586, ppc64le, x86_64

t0xic0der/fedora-messaging

A library for sending AMQP messages with JSON schema in Fedora infrastructure

t0xic0der/obserware

An advanced system monitor utility written in Python and Qt
  • Fedora 41 : x86_64
  • Fedora 42 : x86_64
  • Fedora 43 : x86_64
  • Fedora rawhide : x86_64

t0xic0der/mote

A Meetbot log wrangler, providing a user-friendly interface for Fedora Project's logs. mote allows contributors to the Fedora Project to quickly search and find logs beneficial in keeping up to date with the project's activities.
  • Centos-stream 8 : x86_64
  • EPEL 7 : x86_64
  • EPEL 8 : x86_64
  • Fedora 41 : x86_64
  • Fedora 42 : x86_64
  • Fedora 43 : x86_64
  • Fedora eln : x86_64
  • Fedora rawhide : x86_64
  • Mageia 8 : x86_64
  • Mageia cauldron : x86_64
  • openSUSE Tumbleweed : x86_64

t0xic0der/nvidia-auto-installer-for-fedora

A CLI tool which lets you install proprietary NVIDIA drivers and much more easily on Fedora Linux (32 or above, ELN or Rawhide)
  • Fedora 41 : x86_64
  • Fedora 42 : x86_64
  • Fedora 43 : x86_64
  • Fedora rawhide : x86_64
  • 1
  • 2

News - Read All

Task Queue

14 Build Batches 0 Importing 62 Pending 5 Starting 117 Running

Recent Builds - View All

qelectrotech

Project: remi/qelectrotech

Build: 9701446

State: succeeded

Finished: 2 minutes ago

python-spyder-kernels

Project: @python/python3.12

Build: 9701460

State: succeeded

Finished: 5 minutes ago

python-spyder-kernels

Project: torsava/automatic-obsoletes

Build: 9701462

State: failed

Finished: 5 minutes ago

python-spyder-kernels

Project: @python/python3.14

Build: 9701461

State: succeeded

Finished: 6 minutes ago