ZDoom

Aim Assist Mod v0.8.1
by Jay


Universally (hopefully) compatible Aim Assist made with ZScript, primarily intended for controllers, but can also be used with mouse and keyboard. Configurable Settings in Options Menu. Now with Multiplayer Support and Custom Presets!

Aim Assist in Action
(These were recorded using an xbox one controller)

Spoiler: v0.3 Debug Mode

---

Spoiler: v0.1 Gameplay

---

Download v0.8.1
Get Source

Spoiler: Changelog

---

10/23/24 - v0.8.1

• Internal Refactoring
• New Feature: Enable Mode

01/05/23 - v0.8.0
!!IMPORTANT!! - CVAR names have changed, to keep using your old settings port them to the new format using the Presets->Load Old Format Config option.

• New Settings Preset system
• Minor Fixes
• New debug option: Trace Debug
• More performant default settings

06/17/21 - v0.7.5 - v0.7.5-legacy (for GZDoom 3.x)

• Prevent mod from getting into a bad state when loading savegame
• (legacy) Add support for GZDoom 3.x

05/22/21 - v0.7.4

• Fix compatibility with GZDoom 4.6.0

04/11/21 - v0.7.3

• Fix recenter not working while Aim Assist is toggled Off
• Added "Recenter Always Enabled" option

04/07/21 - v0.7.2

• Fix bug/crash when player connects in the middle of a multiplayer session
• Improve Menu formatting
• Add option to simple menu

04/07/21 - v0.7.1

• Fix Multiplayer RNG Desync with Debug Markers enabled.

04/07/21 - v0.7

• Added Multiplayer Support
• Added Center View button
• Added Recenter by request

03/29/21 - v0.6.1

• Fixed Menus on newer versions of GZDoom

01/20/19 - v0.6

• Fixed bug where obstruction marker would show even when "debug markers" was off
• Added "On Obstruction" options to menu, "Aim Correction" is the new method, "Target Closest" is the previous method, "Don't Aim" skips aiming if target point isn't visible

12/21/18 - v0.5

• Greatly Improved aim height configuration, separated into its own menu (some CVAR names changed, you may need to reconfigure)

12/21/18 - v0.4

• Fixed bug with portals
• Fixed crouch bug
• Improved pitch calculation
• Added obstruction indicator to debug markers

12/19/18 - v0.3

• General code clean-up and added more comments
• Split options menu into submenus
• Added debug options menu ( + debug markers )

12/15/18 - v0.2

• Added "hold" key to options menu
• Improved sliders in options menu

12/14/18 - v0.1

• Initial upload

Very nice, looks like the kind of thing that would work well on a mobile port.

Seems cool (I still didn't try it, that's why I used seems) and this might make a recreation of the Metroid Prime series' Lock-On feature possible!

PhantomDoom741 wrote:Seems cool (I still didn't try it, that's why I used seems) and this might make a recreation of the Metroid Prime series' Lock-On feature possible!

That was already pretty possible - in fact, something like that is almost certainly a lot simpler than this, since that just involves finding a target that the player is close to pointing at, then forcing the player to point at it while they hold down a button. This has aspects of that, sure, but it also has to predict player intentions and make the "latching on" feel natural, so that the player doesn't get stuck on an enemy while trying to turn 180 degrees or lose the sensation of control while trying to play the game normally.

This is a very useful mod.

Pro tip : instead of you can use which then you can use later like Its because findCVar function too slow to call to it every tick.

Apeirogon wrote:Pro tip : instead of

Code: Select all

enabled=CVAR.findCVar("AIM_ASSIST_ENABLED").getBool();

you can use

Code: Select all

class test : eventhandler
{
transient cvar enabled;

override void onregister()
{
enabled = CVAR.findCVar("AIM_ASSIST_ENABLED");
}

}

which then you can use later like

Code: Select all

aimbot_enabled.getbool();

Its because findCVar function too slow to call to it every tick.

I could change it later, but it isn't called every tick, or even much at all, only on save load and when you click "update" on the options menu, so it isn't really a priority.

I found a few issues with this:
1) the player angles slightly up/down towards enemies that are very close to them, leaving the view uncentered once they're dispatched.
2) it does not play well with portals at all, tending to point down and to the left of where the enemy actually is.

Other than that, it's been a very good way to test maps without putting strain on my wrists.

Jaxxoon R wrote:I found a few issues with this:
2) it does not play well with portals at all, tending to point down and to the left of where the enemy actually is.

Can you point me to a simple map with portals for testing so that I can try to fix that bug? I don't really know which maps use them.

I've attached a simple test map containing two portals.

Jaxxoon R wrote:I've attached a simple test map containing two portals.

That was actually surprisingly easy to fix, will update in 0.4, just had to use level.Vec3Diff(), also, for the angle up/down issue, did you try increasing sensitivity in performance settings?

Excellent, thank you very much! It works great with portals now. Unfortunately, I tried to edit the sensitivity setting like you suggested, but it made no apparent difference.

pitch i'm left with after killing this imp:

pitch centered with the "center view" button:


The player still pitches up towards monsters. And it gets worse the taller the monster is, with enemies like the cyberdemon pitching up so high it can be hard to see where you're going. I feel like it would help things if, within a certain distance, it tried to keep the player's view centered as much as it could without straying too far away from the monster's center of mass.

Jaxxoon R wrote: The player still pitches up towards monsters. And it gets worse the taller the monster is, with enemies like the cyberdemon pitching up so high it can be hard to see where you're going. I feel like it would help things if, within a certain distance, it tried to keep the player's view centered as much as it could without straying too far away from the monster's center of mass.

that's probably because currently the aim works at a fixed offset subtracted from the monster height (it's configurable, default is 12, but still a fixed value), i'll add some other height calculation options for 0.5, they should fix it for you.

This is genial! Would you be able to implement an option that once you aim (either manually/freelook or by autoaim) so that it also fires the weapon?

PixelWAD wrote:This is genial! Would you be able to implement an option that once you aim (either manually/freelook or by autoaim) so that it also fires the weapon?

AFAIK it's not really possible to simulate player input in ZScript. You can intercept key presses and cancel them, but not really add new ones. My mod, for example, doesn't simulate mouse input, it just alters player pitch and angle directly.