So the price for a ship will go way down (20000CR), but the price to fully upgrade a ship will go up.  So the cost to fully upgrade ships will be higher than before.  Also I will add a new currency Rep, that will work like experience (eg. it cannot be spent, but can be required to unlock things) that will determine a players position on the leaderboards, which will be view-able in-game.

Basically, the game has been missing a lot of essential features.  Once those are in place I have plenty of ideas to make the game more interesting.  --wj

the game will send offers to players only if teams are unbalanced. players will not initiate the process (except indirectly, eg. lots of players on the other side quit).  I don't want to ever move a player more than once a game.  And the chance of this happening will depend on the score difference and/or player difference.  

Wings would be moved as a group, and only the leader would get offers.  I might add a voting system within the wing latter, but I assume wings will be able to work things out without much help. 

Players in a wing will always be on the same team.  Wings will not necessarily stay with the same battle-group each round however. --wj

the game will offer credits to players on teams that are winning (unless the scores are close).  This will happen automatically, not based on the actions of players on the losing team.  --wj

Custom call signs are fine, as long as they fit a basic model (no numbers or special characters, 1 or 2 words, pronounceable).

I am intending to push a build to a beta server next week, not necessarily live.  

3) I could also flag individuals to be lose chat rights (without informing them, so it would seem like everybody is just ignoring them).  I might make it so that new accounts can only use global chat until they have played a few games.  That would prevent smurf accounts from being used for harassment.  

--wj

yes.  I intend to offer players on winning teams cred bribes to switch to a losing team.  --wj

So there are several issues here.

1) Annoying/Profane names.

2) Malicious behavior (trolling)

3) Chat

4) Banning

Regarding 1)

I want to use Call Signs instead usernames.  Call Signs will be auto-generated from a list.  Players will be able to periodically re-roll the name or pay to get a specific name from the list.  I'll even add a system to add new call signs (with a vetting process).  Players will be able to toggle the display of call signs or usernames in game.  I might just make the call signs mandatory...  All leaderboards and clan listings will use the call sign.

Regarding 2)

Whenever this occurs it is a game design problem.  In the future (sigh...) He-3 containers will be neutral (both teams can capture them).  Also only a sub-set of players will be able to pick-up canisters, and the ability to do so will be awarded based on previous performance (with a random chance that anyone will get it).  So players will be able to troll both teams, but not affect a single team.  Also there will be multiple flags active, and no game will only be about flag captures.  Instead the game will be about completing missions (given to each player).  So if somebody screws up the flag capture mission, it won't stop the seach and destroy players or carrier assault players from succeeding.

Regarding 3)

I am working on the ability to sign into/out of chat channels, and the ability to ignore certain players.

Regarding 4) 

I can ban the player, but I can't stop him/her from creating a new account.  The only way to really stop the behavior is to flag the account, and send the player into empty matches (or matches with other flagged players) so that trolling is less fun.  The player obviously need attention so I think 1) 2) and 3) above will help starve them.  It is very important not to feed the trolls.

I am working as fast as I can to solve these problems.  I am intending to push changes next week.  I apologize for the delays, but the engine had accrued massive amounts of technical debt.

Some random good news... My parent company, has just had some significant financial success, and intends to build up the Moonbreakers engine for use in other games (with real budgets).  This means that I will be able to pull in technical improvements and design tools that Moonbreakers wouldn't otherwise get.

If it is *critical*, I can ban the player.  But it won't solve the problem, and they will just continue with a new account (encouraged by the fact that their actions were important enough to warrant getting banned).

--wj

Well, that would be a fundamental, engine level problem.  While I cannot immediately address your complaint, I will definitely work to fix the security problem.  

Please use the private message feature to discuss details about hacking methods.  I have edited your post.  It is likely that anyone capable of doing what you suggested doesn't need much help, I would prefer not to leave any help in the public forum.

There is very little chance of an aimbot in this game.  Aimbots are more a problem for games based on standardized engines, which this definitely isn't.  

However, it is possible that other hacking methods are used, which I don't want to discuss in a public forum.  

I will look into the logs on this player.  Thanks for reporting the problem.  --wj

So, the game was released too quickly.  There are lots of hidden problems that I have had to fix to get the game to the point where it can do all the things it needs to do.  A lot of the hardest stuff has now been done, but I still need to finish the UI (which involves artwork and layout, things that take me longer than coding).  

As for the bad rep, I understand the feeling.  I was brought on just before the steam release.  So I have been dealing with the aftermath of decisions that were made before I had any control.  After the UI changes (which will include leaderboards/squadrons/wings) and ship rebalance, I'll start trying to round of support for the game.  --wj

Inside of 2 weeks at most.  I have the back-end ready, but I don't have the UI ready.  There was no UI system in place (everything was hard coded in C++), so I have had to create one from scratch.  The old UI caused me intense pain... so I am re-doing all of it so it actually looks good. --wj