Unreal Engine Gameplay Mechanics Fix

@bojans9

Hello, I can debug and fix both gameplay systems in your Unreal Engine 5.3 project without unnecessarily rewriting the existing Blueprint architecture. I will investigate and resolve: * Input mapping and character movement issues * Movement component and Blueprint node chains * Acceleration, deceleration and direction changes * Dropped or delayed input behavior * Melee and ranged hit detection * Line traces and overlap checks * Damage event registration and combat logic * Regression issues against your QA checklist * Blueprint comments/change log for the fixes I can first reproduce the issues from your repository and walkthrough, identify the actual root causes, then make targeted fixes. If a C++ conversion provides a clear benefit, I can discuss it before changing the existing approach. I will return the updated project files ready for verification. Bid: INR 12,500 fixed Timeline: 3-5 days

@PolyPeak3D

Yo! I'd love to take a look into the char blueprint to see what's wrong. I assume you meant that you were still using the default CharacterMovementComponent when you wrote "Everything is still running in the original Blueprint setup; no changes were made in C++ recently"? It's odd tho, but let's see what we can do. As for the inconsistent damage registering, that surely is a frame dependent trace calculation issue. Both of these don't require C++ to be optimally fixed. So I'll try to keep it within Blueprint as much as possible. Plus its much easier for both of us to visually understand and comment there lol. Hit me up once you're ready. Cheers!

@Mou192

I will trace and fix the two failing systems in your Unreal 5.3 project: unresponsive movement input and unreliable combat hit detection. I will pinpoint the broken Blueprint node chains and input mappings, correct the line trace and overlap logic so melee and ranged hits register, keeping it compiling in 5.3 or C++ where it helps. I will add a clear change log and comments in the blueprints, then share updated files that pass your input latency and dummy-enemy QA checklist without regression.

@mohamedhosdegwii

Hello, I can take this on as a focused Blueprint debugging task. I will first reproduce both issues from your walkthrough before changing nodes, so the fixes target the real cause rather than masking symptoms. My approach: • Trace Enhanced Input mapping/context, pawn/controller possession, and Movement Component settings to identify why input is dropped or delayed • Review combat trace/overlap execution paths, collision channels, hit actors, damage events, and any gates or cooldowns preventing valid hits • Apply targeted fixes, then retest against your input-latency and dummy-enemy checklist • Return updated project files with a concise change log explaining every Blueprint change I will keep the work Blueprint-first and will only recommend C++ if it is clearly necessary and agreed with you first. My background is in diagnosing production software issues, event-driven systems, APIs, and reliable delivery. This would be my first project on Freelancer, so I am offering an introductory bid and close communication throughout the task. Please share the repo and screen recording. I can start by confirming the reproduction steps and exact fix plan immediately.

@shreshthm0

Hi I am shreshth Maurya and d I am a student . For your project you should need a person wo knows about gaming I am also a gamer of bgmi . Bgmi also made on unreal engine so I will be useful to you

@humakiai

Hi — Team Humaki reviewed "Unreal Engine Gameplay Mechanics Fix". We matched this to our c programming, game design, c# programming skills and can keep scope tight. Plan: (1) confirm acceptance criteria and any repos we need; (2) ship a working slice you can verify; (3) hand off working changes plus a short note. We will flag anything outside the stated scope before coding. Delivery in 1 day. — Team Humaki (@humakiai)

@sanm27

Hi, I can help diagnose and fix both issues in your Unreal Engine 5.3 project. I have hands-on experience with Unreal Engine gameplay systems, including Character Movement, Blueprint input handling, collision/overlap logic, line traces, combat systems, damage events, and debugging gameplay issues. For the movement issue, I would trace the input flow from the mapping/context through the Blueprint logic and Character Movement Component to identify whether the problem is caused by input configuration, execution flow, movement settings, or an overlooked node chain. I’ll focus on restoring responsive and predictable acceleration, deceleration, and direction changes. For combat, I’ll trace the complete hit pipeline—from line traces/overlaps and collision channels through hit results and damage events—to identify why valid hits are being missed and make the melee/ranged detection reliable. I’ll also document the changes directly in the Blueprints and provide the updated project for your QA testing. Since the project must remain compatible with UE 5.3, I’ll prioritize fixing the existing Blueprint architecture rather than converting systems to C++ unless there is a clear benefit. I’m comfortable working from an existing Git repository and using your recorded walkthrough to reproduce the issues before making changes. Best regards, Shreif

@kshitijt18

Hi, for the first part I think it could be a configuration issue. For the second issue it is mostly bullet paper problem, I do have experience with this. As a part of my corrections or improvements, I will add comments for the flow and also document the change for you. If you want more please let me know.

@RavenClaw0980

I am well versed with unreal trace sessions allowing me to figure out the exact cause of the delays in both the input and hit traces. The reason i have put the bid this high is I am confident in delivering you the project to your satisfaction.