Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Money Glitch with chopshop #318

Closed
numpty9989 opened this issue Apr 16, 2017 · 4 comments
Closed

Money Glitch with chopshop #318

numpty9989 opened this issue Apr 16, 2017 · 4 comments
Labels
needing-confirmation For issues that are awaiting verification that what they are reporting is a genuine problem.

Comments

@numpty9989
Copy link

Expected behaviour

Money Should Go In Bank

Actual behaviour

Money In Bank Duped into cash also got the Chop shop cash in cash

Steps to reproduce the behaviour

  1. https://youtu.be/30agb7ftfNs?t=61
    link to proof

RPT and/or extDB3 logs (if applicable)

No Errors
Chopshop File Stock 5.0 file


Mission version: <See core/init.sqf, briefingName in mission.sqm, or changelog in briefing.sqf for your mission version.>5.0

Launcher version: <In the Arma 3 launcher go to ⚙ OPTIONS and click the version info below to copy it to your clipboard.>Latest Launcher Version

Game version:

Branch:

@SalihCanBinboga
Copy link

`_nearVehicles = nearestObjects [getMarkerPos (_this select 3),_chopable,15];
_nearUnits = (nearestObjects[player,["Man"],500]) arrayIntersect playableUnits;
if (count _nearUnits > 1) exitWith {hint localize "STR_NOTF_PlayerNear"};

added > fn_chopShopMenu.sqf

@numpty9989
Copy link
Author

how does that fix the Bank Dupe

@numpty9989
Copy link
Author

oh soz xD

@Jawshy Jawshy added the needing-confirmation For issues that are awaiting verification that what they are reporting is a genuine problem. label Sep 9, 2017
@DomT602
Copy link
Member

DomT602 commented May 15, 2019

The money was intended to be paid as cash in hand (rather then the bank), this can be changed for your server relatively easily. As this is a non-issue, this will be closed.

@DomT602 DomT602 closed this as completed May 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needing-confirmation For issues that are awaiting verification that what they are reporting is a genuine problem.
Projects
None yet
Development

No branches or pull requests

4 participants