It is recommended to use Visual Studio 2022.
As well as setting up cheat-library
as startup project.
The following is a recommended procedure, but others may be used.
- Clone repository with
git clone --recurse-submodules https://github.com/Akebi-Group/Akebi-GC.git
- Open
Akebi-GC/akebi-gc.sln
- Build solution
akebi-gc.sln
.
- Head over to the releases page
- Download the latest binaries
- Head over to the action page
- Click Publish workflow
- Select most recent workflow with green checkmark โ
- Download Akebi-GC-release in Artifacts section
- Visual C++ Redistributable packages for Visual Studio 2015-2022 (x64)
- Visual C++ Redistributable packages for Visual Studio 2015-2022 (x86)
(1-2 are optional if you didn't build from source)
-
Open
/bin
-
Open Compiled version (debug, release)
-
Ensure that
CLibrary.dll
is in the same folder thatinjector.exe
. -
Run
injector.exe
. -
After the login page appeared, press F1 to open Akebi GUI.
- Protection Bypass
- In-Game GUI
- Hotkeys
- Notifications
- Invincible
- Attack Modifier
- No Cooldown Skill/Ultimate/Sprint
- Unlimited Stamina
- No Clip
- Auto Seelie
- Vacuum Loot
- Dumb Enemies
- Auto Destroy Objects
- Auto Loot
- Pickup Range
- Auto Talk
- Auto Tree Farm
- Auto Cook
- Fake Time
- Auto Fish
- Kill Aura
- Mob Vacuum
- Chest/Oculi Teleport (Teleports to nearest)
- Map Teleport (Teleport to mark on map)
- Custom Teleport (Teleport through list)
- ESP
- Interactive Map
- Elemental Sight
- No Fog
- FPS Unlock
- Camera Zoom
- Chest Indicator
- Hide UI
- In-game Embedded Browser
- Enable Peaking
- Profile Changer
- Free Camera
- Texture Changer
- Paimon Follow
- Entities Manager
- Position Info
- FPS Graph
- Packet Sniffer
- You Found a bug.
- write down what happened, as well as your first thoughts on what you think caused it.
- can it be reproduced? Yes or no. If yes: Explain in as much clear as possible. i.e what happens when the bug occurs and why it occurs.
- Tell us which version you are using. copy the
SHA
/ Version Number of the latest commit when you built the mod. For example:bd17a00ec388f3b93624280cde9e1c66e740edf9
/ Release 0.7
I found a bug in the feature enemy vacuum
.
I think it's caused by the filter functions that are defined in someFeature.cpp
.
Date Occured: 5/3/2022
Is it reproducible: Occasionally
Latest Commit used: bd17a00ec388f3b93624280cde9e1c66e740edf9
Release Version: 0.7
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature
) - Commit your Changes (
git commit -m 'Add some AmazingFeature'
) - Push to the Branch (
git push origin feature/AmazingFeature
) - Open a Pull Request
Open an issue with the title of the suggestion you want to make. In the description, make sure it is descriptive enough so our devs can understand what you want and how you want it.