fhxngz Posted May 5 Posted May 5 (edited) Bug Type (Server:): Main Server Severity level (Low - Medium - High): High Evidence (if you can): (I have SSs listed below) Description of the bug (If it's a black screen issue, please provide your SteamID64): I’m bringing this to attention on behalf of CG and per the request of CMD WarMaster. Recently there has been a incident where I've tried to arrest an player and use the /AF Men on the DSL Stone whitelist but its logging the incorrect names. I want to be clear that I’ve been positively and absolutely 100% sure that I am clicking the RIGHT name when assigning via drop down menu to the offender. On 5/2 I arrested "Biggus" for RDM, and "SpandongoloidDan" for Breaking PTS on the same day and it copied His (Dan's name) and pasted it into Biggus's RDM (see attached screenshots for proof). I even went as far as to try the manual forum entry too and its not showing his (Biggus's) name properly, his battalion, or his arrest count on the public records. Its doing the same thing for others who've been entered manually and also I've even seen where it is not logging the arrest number correctly either it'll say N/A. This happened a few days ago too but I didn't get a screenshot of it then. Correct me if I’m dead wrong but I make sure I memorize the CTs Steam Name to their Steam64 (last four digits) and tie it correctly every time. I have zero clue why this is happening but it needs to be corrected ASAP so random people aren't being arrested for no reason. I have no malicious intent or carelessness when arresting or making arrests either. How can we recreate it: I honestly have no clue, first time I've seen it. Screenshot 1: Screenshot 1 (Incorrect Visual Log) Screenshot 2: Screenshot 2 (Public Arrest Records - Manual Forum Submission.) Screenshot 3: Screenshot 3 (Evidence for Biggus's Log not logging correctly) Edited May 5 by Mxysry Incorrect Format / Couldn't Navigate to find the Bug Report Forum Quote
Posted May 5 (edited) Bug Type (Server:): Main Server Severity level (Low - Medium - High): High Evidence (if you can): (I have SSs listed below) Description of the bug (If it's a black screen issue, please provide your SteamID64): I’m bringing this to attention on behalf of CG and per the request of CMD WarMaster. Recently there has been a incident where I've tried to arrest an player and use the /AF Men on the DSL Stone whitelist but its logging the incorrect names. I want to be clear that I’ve been positively and absolutely 100% sure that I am clicking the RIGHT name when assigning via drop down menu to the offender. On 5/2 I arrested "Biggus" for RDM, and "SpandongoloidDan" for Breaking PTS on the same day and it copied His (Dan's name) and pasted it into Biggus's RDM (see attached screenshots for proof). I even went as far as to try the manual forum entry too and its not showing his (Biggus's) name properly, his battalion, or his arrest count on the public records. Its doing the same thing for others who've been entered manually and also I've even seen where it is not logging the arrest number correctly either it'll say N/A. This happened a few days ago too but I didn't get a screenshot of it then. Correct me if I’m dead wrong but I make sure I memorize the CTs Steam Name to their Steam64 (last four digits) and tie it correctly every time. I have zero clue why this is happening but it needs to be corrected ASAP so random people aren't being arrested for no reason. I have no malicious intent or carelessness when arresting or making arrests either. How can we recreate it: I honestly have no clue, first time I've seen it. Screenshot 1: Screenshot 1 (Incorrect Visual Log) Screenshot 2: Screenshot 2 (Public Arrest Records - Manual Forum Submission.) Screenshot 3: Screenshot 3 (Evidence for Biggus's Log not logging correctly) Edited May 5 by Mxysry Incorrect Format / Couldn't Navigate to find the Bug Report Forum Quote
Mystic Posted May 5 Developer Posted May 5 Please follow the bug report format. Please list what job you're on. 1 Quote Longest Special Operations Member on the server. Current: Nothing l Senior Developer Former: Cin Drallig l First Yayax Squad Yover l Foxtrot Commando l 2nd GM BCMD Bacara l Serra Keto l Final SO Commander Jet l First & Last Devil Dogs Deadeye l Veteran Admin l Jedi General Plo Koon l 2nd Returning SO CMD Jet l Luminara Unduli l Wolfpack MAJ Boost l Kit Fisto l Trauma's Unit MED Mystic l Jedi Military Advisor l Omega 36 PVT Darman l High General Shaak Ti l Jedi Chief Instructor l Alpha 98 Nate l Actually Private Crosshair l Mace Windu l Final SO Blackout l Grand Master Yoda l CG DSO Thorn
Developer Posted May 5 Please follow the bug report format. Please list what job you're on. 1 Quote Longest Special Operations Member on the server. Current: Nothing l Senior Developer Former: Cin Drallig l First Yayax Squad Yover l Foxtrot Commando l 2nd GM BCMD Bacara l Serra Keto l Final SO Commander Jet l First & Last Devil Dogs Deadeye l Veteran Admin l Jedi General Plo Koon l 2nd Returning SO CMD Jet l Luminara Unduli l Wolfpack MAJ Boost l Kit Fisto l Trauma's Unit MED Mystic l Jedi Military Advisor l Omega 36 PVT Darman l High General Shaak Ti l Jedi Chief Instructor l Alpha 98 Nate l Actually Private Crosshair l Mace Windu l Final SO Blackout l Grand Master Yoda l CG DSO Thorn
Bleach Posted May 5 Posted May 5 22 minutes ago, Mystic said: Please follow the bug report format. Please list what job you're on. Yeah you tell him Mystic!!! 1 Quote I am Best Canadian on the Server Caterpillar smoking a cigarette.
Posted May 5 22 minutes ago, Mystic said: Please follow the bug report format. Please list what job you're on. Yeah you tell him Mystic!!! 1 Quote I am Best Canadian on the Server Caterpillar smoking a cigarette.
Azara Posted June 16 Posted June 16 This has been marked as acknowledged and marked as a bug that is being looked into. This will remain unlocked in the case that more information becomes present. // MOVING TO ACKNOWLEDGED REPORTS Quote Current: ❌ Former: ✔️
Posted June 16 This has been marked as acknowledged and marked as a bug that is being looked into. This will remain unlocked in the case that more information becomes present. // MOVING TO ACKNOWLEDGED REPORTS Quote Current: ❌ Former: ✔️
Recommended Posts