There is a problem in the game right now with combat. The addition to the combat log timer was a huge positive for the game as it pretty much eliminated combat logging for the most part. But recently, a workaround has been found to bypass the combat log timer and that has brought combat logging back into the game. Just two days ago, a bounty combat logged on me 3 times in a row after they realized they were going to die in those three battles. There have also been other instances where I have seen this happen as well. It really has ruined the bounty hunting game loop a lot but also for any combat in general when someone combat logs using that exploit. Are the devs aware of this exploit? I'm also not sure if the combat log timer is working at all: https://issue-council.robertsspaceindustries.com/projects/STAR-CITIZEN/issues/STARC-97186 And that brings me to my next issue - ejecting and backspacing. This has existed when combat logging was a thing and it still exists now. This is a huge problem for bounty hunters. If a person ejects and then backspaces, they get teleported back to grim or if they have their spawn set at an 890 for example, they'll spawn there. They do this to avoid going to jail as their about to die by the bounty hunter. This should not be a thing as when they backspace near a bounty hunter, they should be sent to jail as this is the intended game-play loop. This was the case a few patches ago where the bounty goes to prison if they eject and then backspace after engaging in a fight but this disappeared as other patches came in for some reason. As most bounty hunters would agree, the bounty should be sent to jail if they die after a fight - not be sent to grim. I really think this is a fundamental logic error within the PvP bounty hunting game-play loop. Will this get fixed any time soon? Another minor issue that is related to this is if you incapacitate a bounty in FPS and then they backspace, the mission fails for the bounty hunter but they do go to jail. I think this is another logic issue as the bounty hunter have done their job and they should get paid whether they kill the bounty or they backspace on their own. Also, something unrelated to the combat logging and eject/backspace issue but still deserves a mention - there is a bug where if a bounty travels from system to system and stops halfway, the mission withdraws from anyone that has it but this does need more testing as it could be not common.