I realize this isn’t a new idea, however there are some ways to address concerns people have had in the past.
potential issues:
- If we’re going to pay an npc corp to name a system, what possible reason would there be for it to own such rights, especially in nullsec?
Local is handled by the fluid router network. Just have the bill be paid to concord and problem solved.
- Learning routes, names of systems and how they connect is important gameplay. Being able to rename your systems to mess all that up would have real gameplay impacts, not just cosmetic benefits.
‘chosen name’ FD-MLJ
You can keep the static name while tacking on the named portion before or after it.
- Vulgar language.
Content moderation can be handled in the same way station, alliance, corporation, and character names are handled.
Implementation:
-
Own system sov.
-
Offer an amount of money in a blind auction format as a bribe to concord to change the system name.
-
If the amount offered is above the threshold, (ie: x% more than was offered previously for that system,) the system’s name changes to the desired name in exchange for the offered amount of isk.
-
If the amount is below the threshold, the alliance still loses the amount of isk and the system name doesn’t change.
-
In case of naming violation, a GM will delete the name and keep the new isk threshold in place.
Reasons:
It’s a massive isk sink targeted at the richest in new eden while giving those players a legacy in return. Keeping the threshold amount blind helps to foster legacy.