prk/issues
19
3
Fork 0
Code Issues 241 Pull requests Projects 2 Releases Packages Wiki Activity Actions

Ammo Count Desync After FA/Burst Without Auto-Reload #1161

New issue
Closed
opened 2024-10-28 12:15:20 +00:00 by kajori · 2 comments
kajori commented 2024-10-28 12:15:20 +00:00
Member
Copy link

Report link

Reproduction steps

  1. Create a character
  2. Buff yourself up .ncu run 216864
  3. Equip a weapon with sufficient ammo .item 272045 272046 50
  4. Reduce your ammo count so that your next Full Auto will empty the magazine.
  5. Use FA
  6. Ensure the enemy dies instantly, ending combat and skipping the auto-reload.
  7. Use Burst and observe the ammo count during subsequent attacks and special abilities.

Expected results

The ammo counter should update immediately after using FA or Burst, reflecting the correct ammo usage.

Actual results

The ammo count does not update correctly when using specials. The ammo counter only updates on the next auto attack, potentially leading to negative ammo values under certain conditions.

Bug prevalence

Description & Attachments

### Report link - ### Reproduction steps 1) Create a character 2) Buff yourself up `.ncu run 216864` 3) Equip a weapon with sufficient ammo `.item 272045 272046 50` 4) Reduce your ammo count so that your next Full Auto will empty the magazine. 5) Use FA 6) Ensure the enemy dies instantly, ending combat and skipping the auto-reload. 7) Use Burst and observe the ammo count during subsequent attacks and special abilities. ### Expected results The ammo counter should update immediately after using FA or Burst, reflecting the correct ammo usage. ### Actual results The ammo count does not update correctly when using specials. The ammo counter only updates on the next auto attack, potentially leading to negative ammo values under certain conditions. ### Bug prevalence - ### Description & Attachments <video src="/attachments/d164c227-21c1-404a-a469-8fd6b5337dec" title="2024-10-28 12-35-26.mp4" controls></video>
2024-10-28 12-35-26.mp4
26 MiB
kajori added the
type
bug
priority
2
 labels 2024-10-28 12:15:20 +00:00
kajori added this to the Season 2 Launch project 2024-11-25 15:23:17 +00:00
drake added the
state
fixed
 label 2024-12-22 11:58:43 +00:00
drake commented 2024-12-22 11:58:58 +00:00
Owner
Copy link

This has been somewhat fixed, though there is a client-side bug with this apparently.

This has been somewhat fixed, though there is a client-side bug with this apparently.
drake self-assigned this 2024-12-22 12:15:02 +00:00
Raggy commented 2024-12-22 15:07:33 +00:00
Member
Copy link

Confirmed it is somewhat fixed. The client doesn't seem to keep up with the fact the weapn has been reloaded server-side following a full mag dump from FA into a dead mob. However, it's tracking ammo correctly otherwise. Closing this one as (somewhat) fixed as of 22/12/2024.

Confirmed it is somewhat fixed. The client doesn't seem to keep up with the fact the weapn has been reloaded server-side following a full mag dump from FA into a dead mob. However, it's tracking ammo correctly otherwise. Closing this one as (somewhat) fixed as of 22/12/2024.
Raggy closed this issue 2024-12-22 15:07:33 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
470-items-duplicate-during-trade
No results found.
Labels
Clear labels   
area
blabot
Related to NPC dialog/conversations

  
area
client
This issue is (or appears to be) client-side

  
area
encounters
Related to scripted encounters

  
area
launcher
Related to the launcher

  
area
missions
Related to randomly generated missions

  
area
npc-behavior
Related to NPC/monster behaviour

  
area
performance
Caused by or related to server performance issues

  
area
portal
Related to the player portal website

  
area
quests
Issues relating to quests

  
area
rdb
Caused by RDB issues

  
area
teams
Issues relating to teaming with other players

  
area
trading
Related to trading with vendors and/or other players

  
area
zone

  
priority
1
Crashes playfield/server/other players or is game-breaking in a major way

  
priority
2
Crashes/breaks a character, significant gameplay impact with no workaround

  
priority
3
Standard or significant gameplay impact with workaround

  
priority
4
Trivial or minor gameplay impact, with or without workaround, or visual only

  
shadowlands

Related only to Shadowlands content

  
state
cant-reproduce
Can't be recreated by another tester

  
state
duplicate
This issue or pull request already exists

  
state
fixed
Developer has rolled out changes, needs re-tested to confirm fixed

  
state
new
Needs to be (re-)tested to ensure the issue is reproducible

  
state
unrefined
Needs more detail, repro steps or to be cleaned up

  
state
verified

  
state
wontfix
This will not be worked on

  
type
bug
An implemented feature is not working correctly

  
type
enhancement
Unimplemented feature, new feature / request

No labels
area
blabot
area
client
area
encounters
area
launcher
area
missions
area
npc-behavior
area
performance
area
portal
area
quests
area
rdb
area
teams
area
trading
area
zone
priority
1
priority
2
priority
3
priority
4
shadowlands
state
cant-reproduce
state
duplicate
state
fixed
state
new
state
unrefined
state
verified
state
wontfix
type
bug
type
enhancement
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Season 2 Launch
Assignees
Clear assignees
No assignees
drake
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: prk/issues#1161
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?