Why not increase the DV shift for the hex in PvP?
Instead of getting a 1 DV shift for winning a PvP, make it 2 or 5?
That will encourage people to fight to the death, and make an hours worth of battle worthwhile.
It will also make the defeated party think twice about returning to the same hex as they have just cost there side a huge
DV shift in that hex.
Problem is for alot of the suggestions I *believe* you need a functional SQL server
or the source code.
Neither of which we have.
Features that were developed and implemented in a SQL-enabled server over 2 years ago...
1. Variable DV shift. Beat the AI = 1 pt shift. Beat another player = 10 pt shift. Gives a whole new meaning to PvP victories.
2. Custom shipyards. Races only build what they want and what they can afford economically. granted, you had to buy/sell ships using the chat system, which was clunky, bit it worked.
3. Bases could be set to destruct when their hex DV fell below a certain level. For example, a starbase would remain on the map until the DV fell to below 5.
4. Map enforced LOS. If you capture a hex for your race that does not border a hex already under your control, ownership of the hex stays neutral, but the DV automatically goes up to max. So, you may not capture the hex, but you deny the previous owner that hex as well.
Unfortunately, the max player load on any of the servers that used this stuff was 16. So, this cannot be considered a valid load test. It was also done using EAW, after the majority had moved on to OP, so it had virtually no support from this playerbase.
All of this was done
without the benefit of the source code. So...as Spock would say 'There are always possibilities.'