VmanGman wrote: » A solution I would like to suggest to this issue would be to give races a bonus to their representation in a node’s architectural style decision based on the region/biome the node is in.
VmanGman wrote: » due to how the currently proposed system works, the least popular race will most likely never see a metropolis with their race's architecture, quests, and content.
bloodprophet wrote: » If you want to support a node but don't want to roll that race I also get and the answer is obvious as well. But as I said I understand the idea of not wanting to roll Orc but living in their city contributing to the aestic of the Orcs. However if other people are trying to swap it from orc to elf and you roll in as an elf contributing to orc. They are now being short changed by you as they are expecting you to be contributing to elf.
Next point if they allow everyone to select what ever aesthetic they want to contribute to then many people will do so. This could lead to a disjointed feeling for the RP crowd. Imagine walking into a city where 75% of the players are Orc and the aestic is Dwarven. Because a bunch of people picked that. (A large guild could do it just for the lol's).
I will look later but I don't remember them saying racial quests were tied behind node level. But if they did I agree that is a poor choice.
Vhaeyne wrote: » I like the whole "It's a feature, not a bug" school of thought on this one. If only 5% of the server is Niküa, then I would not expect to see any major Niküa architecture. It makes no sense that a race that has 1/20th the world population would dominate 1/5th the world's metropolises by having a single metropolis. Assuming there are only five metropolises.
Dygz wrote: » Vhaeyne wrote: » I like the whole "It's a feature, not a bug" school of thought on this one. If only 5% of the server is Niküa, then I would not expect to see any major Niküa architecture. It makes no sense that a race that has 1/20th the world population would dominate 1/5th the world's metropolises by having a single metropolis. Assuming there are only five metropolises. But, this isn't just about one server. It's all servers. Since an even spread of all races is 11%, it's likely that even the least popular race in the game will have a Metro at some point on some server. Even 5% of the entire game population can be more than 11% on a single server.
JustVine wrote: » bloodprophet wrote: » If you want to support a node but don't want to roll that race I also get and the answer is obvious as well. But as I said I understand the idea of not wanting to roll Orc but living in their city contributing to the aestic of the Orcs. However if other people are trying to swap it from orc to elf and you roll in as an elf contributing to orc. They are now being short changed by you as they are expecting you to be contributing to elf. I don't see how they are getting 'short changed' if it is freely available info on your character sheet. Next point if they allow everyone to select what ever aesthetic they want to contribute to then many people will do so. This could lead to a disjointed feeling for the RP crowd. Imagine walking into a city where 75% of the players are Orc and the aestic is Dwarven. Because a bunch of people picked that. (A large guild could do it just for the lol's). I think this is the most valid crit I have seen argued. I do disagree with it. But thanks for bringing up this point as it shows why the issue is so complex. The reason I disagree with it is 'culture evolves'. Your guild example means that the guild itself decided that was how they decided to impose their cultural identity, which is sort of what the feature was intended to do in the first place. However, I do consider the disjointed rp, and larger possibility of undermining the 'world feel' a fair consideration. This is why I proposed the citizen vote option. The default stays heavily 'as intended' but when it changes to something the community prefers it has a real historical meaning. Culture evolves. If people are worried about players cycling around it. Just make it cost exponentially more to do each time. But that brings us back around to: I will look later but I don't remember them saying racial quests were tied behind node level. But if they did I agree that is a poor choice. If part of the base incentive of node wars is racial quest driven, its extremely bad design. Giving people the opportunity as a community to change their node architecture doesn't effect all the other much much MUCH more meaningful reasons to go to node war. Further more the racial quest incentive lowers over time as the majority of the population gets theirs leaving the minorities. I just simply don't see this specific design principle worth sticking to in favor of ignoring compromise.
VmanGman wrote: » Why do you keep talking about even spreads? The races are obviously not going to be evenly spread out. They never are. Some races will be significantly more popular than others.What's the point of discussing even spreads? Also, what does the entire game's population have to do with a race's population on any single server? The least popular race will be the least popular on every single server.
Dygz wrote: » VmanGman wrote: » Why do you keep talking about even spreads? The races are obviously not going to be evenly spread out. They never are. Some races will be significantly more popular than others.What's the point of discussing even spreads? Also, what does the entire game's population have to do with a race's population on any single server? The least popular race will be the least popular on every single server. Because that gives us an idea of the likely population spreads. Especially compared to WoW, where the highest race is 15%. The OP states: "We might never see a Metropolis of some races." That is not just a single server. That is across all servers. Some races never getting a Metro on a single server is a feature; not a bug.
Dygz wrote: » Let's assume the lowest population game-wide is Nikua at 5%. Nikua at 5% on just one server is too low for a Metro, which is fine. But, that 5% game-wide can band together to be 20% or even 25% on a different server. And, if they want to have a Metro, there is incentive for them to do just that. How players will choose to group in order to get a Metro will not be determined by statistics. Having more Nikua (or whatever the lowest population is game-wide) band together on one sever will not be random. It will be strategic.