Yet another thread which wails about a small detail which is out of wack.
Contrary to what often is suggested in these threads, things like this don't happen because Frontier managers or developers are idiots.
When we're playing this game, there are literally thousands/millions of separate bits of data and formulas and executing scripts swirling around hour virtual existence at any given moment. These data bits and calculations control things such as the state and position of every, ship, station, outpost, accepted mission, where they are positioned and where they are headed just to name a few.
The slavery counter offer value being out of proportion to the original offer is only out of proportion when you have destination stations which are extremely far away from the arrival point. This is because in formulas in the mission script, the distance from the arrival didn't always play a big roll in calculation of the mission reward but now it does. The problem is that when that mission script was adjusted to take into account the distance from arrival, the template/script for the generation of the counter offer mission was not updated as well. A small detail like this is a very easy thing to miss in a game system with thousands of data, formulas, templates and scripts, etc.
You might ask why did the Frontier developer who changed the mission not know to change the counter offer mission too? Well, there's no guarantee that they were the same developer that originally created the mission so they may not have even been aware of the counter offer mission, let alone how it works. Even if they were the same developer, this is a vary complex set of game rules.
Please give the Frontier Developers a break because this amazing game is a lot to manage!
If you're annoyed by small details like this being out of wack, then join lots of us in open the beta starting at the end of the week, watch for threads explaining what needs to be tested, and do more than just fly the newest ship.