OsirisAndExtra
OsirisAndExtra copied to clipboard
Recommandations for your cheat <3
Hi developer! I am here for you and for your cheat. I will be giving you suggestions for your cheat that will help us alot
- Penetration crosshair ( ik thats on your to do list )
- ESP FLAGS
- Custom legitbot not based on the aimbot.cpp and aimbot.h
- Force Safe points (by bind)
- Force BODY aim (by bind)
- Min dmg over ride (by bind)
- Custom menu style If you can add this, i will donate 5 euros to you. Thanks!
2. ESP FLAGS I know of c4 but what more flags? 3. Custom legitbot not based on the aimbot.cpp and aimbot.h What do you mean? 4. Force Safe points (by bind) Cpu intensive, im thinking of multithreading setupbones 5. Force BODY aim (by bind) Can do 6. Min dmg over ride (by bind) Can do 7. Custom menu style I dont know how to do menus
2. ESP FLAGS I know of c4 but what more flags? .like fake duck, armor, money 3. Custom legitbot not based on the aimbot.cpp and aimbot.h What do you mean? .nvm 4. Force Safe points (by bind) Cpu intensive, im thinking of multithreading setupbones .great idea 5. Force BODY aim (by bind) Can do 6. Min dmg over ride (by bind) Can do 7. Custom menu style I dont know how to do menus .like in osiris where u have the style menu
For ESP flags, would it be feasible to have a "Resolved" tag once the player's desync has been resolved (since you are also developing the resolver now)?
For ESP flags, would it be feasible to have a "Resolved" tag once the player's desync has been resolved (since you are also developing the resolver now)?
of course, that can be a flag
@notgoodusename how about thirdperson when spectating
?
else if (localPlayer->getObserverTarget() && (localPlayer->observerMode() == ObsMode::InEye || localPlayer->observerMode() == ObsMode::Chase))
{
memory->input->isCameraInThirdPerson = false;
localPlayer->observerMode() = thirdPerson[config->visuals.thirdPerson] ? ObsMode::InEye : ObsMode::Chase;
}
For ESP flags, would it be feasible to have a "Resolved" tag once the player's desync has been resolved (since you are also developing the resolver now)?
Not a good idea since resolving a player can never be accurate enough
For ESP flags, would it be feasible to have a "Resolved" tag once the player's desync has been resolved (since you are also developing the resolver now)?
Not a good idea since resolving a player can never be accurate enough
what about fake duck flag, scoped, etc. things like that