VmanGman wrote: » Dygz wrote: » 9 races and 5 Metros. It's very likely some servers will have race that never gets a Metro. That's one of the great things about Ashes. Servers will be different. To regain their ancestral homes, they are going to have to "fight" for it with population. That is a key part of Ashes "PvP" conflict. Yes, I am aware that some races won't get a metro because there are 9 races and 5 possible metros, but it goes beyond that. We might literally never see a specific race's metro structures, quests, NPCs etc. in game (across all servers) because there are so few players of that race. Dygz wrote: » I guess you will just have to play to see for yourself, but... Those extremes are highly unlikely. That's not the way the numbers work. That is exactly how these numbers work. Technically, since it is all based on percentages, if the races are spread out evenly, you will only see nodes with the most popular race's architecture. Of course that is an extreme example and it won't happen exactly like that, but it strengthens my point that some races might never be represented architecturally past a certain node level. The developers would literally create content that would simply never have the chance to be seen because a metropolis of a less popular race will never exist.
Dygz wrote: » 9 races and 5 Metros. It's very likely some servers will have race that never gets a Metro. That's one of the great things about Ashes. Servers will be different. To regain their ancestral homes, they are going to have to "fight" for it with population. That is a key part of Ashes "PvP" conflict.
Dygz wrote: » I guess you will just have to play to see for yourself, but... Those extremes are highly unlikely. That's not the way the numbers work.
Merek wrote: » It's not going to happen. I'll assume the nodes will have a base aesthetic but due to the cosmetics you can apply inside of nodes, expect them to look weird, if not completely ridiculous.
Cypher wrote: » Don’t like it. Your solution to “maybe we won’t see a metro with X racial aesthetic” is essentially “we will probably only see X racial aesthetic in this region because it has a disadvantage in the other regions”. Just leave it alone and keep it totally free-market and unbiased. I guarantee you will see at least one node of each race on a server.
Azherae wrote: » It's not extreme at all, that's exactly how that works, it's just Search Engine Optimization/YouTube algorithms in 'reverse'. Personally I'd bet on never seeing Nikua nodes past stage 3, on at least one server.
Dygz wrote: » I doubt they would spread themselves out over 100 Nodes, they would most likely attempt to get at least a Village because there is racial progression via racial quests that would start at the Village stage. We will be able to filter characters on the server by race, so it will not be at all challenging to find other characters of your race on your server. It's highly unlikely that a race will not at least have a Village on the server. The devs will determine if there needs to be prevention for that. It's unlikely to be in the form of creating multi-racial neighborhoods and/or Mayors choosing the architectural style. The code for that is likely to be to convoluted. Already challenging enough to meet their current design goals.
JustVine wrote: » And again, the real problem isn't 'unpopular races.' The real problem is 'my race determines my architecture vote and there is no current way to change that.' There will always be less popular character choices for body type/self expression. That is normal and not problematic. Architecture is less directly about personal representation and more about 'what I find pleasing to have around me.' There could be entire swathes of kaelar who would rather their costal city be Nikua architecture but 'moving to the coast' would just spawn a less desirable city for them. I am glad they make the architecture lore based and I am glad the current default will lead to some initial diversity in locale and design. However, it's far easier and more free market to have a vote and 'persuade people to vote empyrean or dunir architecture.' Than it is to 'persuade people to play that race.' Let certain populations be naturally lower or skewed in different servers. That's part of what will make ashes unique. Let's just also hope they come up with a way to 'have a way to vote for ones truely desired architecture.'
JustVine wrote: » You keep saying 'mayor deciding it.' But I am not suggesting that. I am suggesting 'the mayor issues an election on a specific node issue. Citizens of the node vote on the 8 choices. After the vote is concluded the city changes to that architecture style instead on next server maintenance or whatever is most convenient. To issue this vote costs node resources to initiate the rebuild.' Given their intentions for nodes many of the systems for implementing this will already be needed for other intended features.
JustVine wrote: » Dygz wrote: » I doubt they would spread themselves out over 100 Nodes, they would most likely attempt to get at least a Village because there is racial progression via racial quests that would start at the Village stage. We will be able to filter characters on the server by race, so it will not be at all challenging to find other characters of your race on your server. It's highly unlikely that a race will not at least have a Village on the server. The devs will determine if there needs to be prevention for that. It's unlikely to be in the form of creating multi-racial neighborhoods and/or Mayors choosing the architectural style. The code for that is likely to be to convoluted. Already challenging enough to meet their current design goals. Just have a setting where the vote system reads me as x race instead of my 'actual.' This adds various potential bugs, but thats the main challenge for it. I would figure the democratic vote would be easier to implement and contain bug wise, hence me suggesting it first. You keep saying 'mayor deciding it.' But I am not suggesting that. I am suggesting 'the mayor issues an election on a specific node issue. Citizens of the node vote on the 8 choices. After the vote is concluded the city changes to that architecture style instead on next server maintenance or whatever is most convenient. To issue this vote costs node resources to initiate the rebuild.' Given their intentions for nodes many of the systems for implementing this will already be needed for other intended features.
Dygz wrote: » JustVine wrote: » You keep saying 'mayor deciding it.' But I am not suggesting that. I am suggesting 'the mayor issues an election on a specific node issue. Citizens of the node vote on the 8 choices. After the vote is concluded the city changes to that architecture style instead on next server maintenance or whatever is most convenient. To issue this vote costs node resources to initiate the rebuild.' Given their intentions for nodes many of the systems for implementing this will already be needed for other intended features. I keep saying Mayor because it's the Mayors that make those kinds of decisions. The only Node Type with voting is the Scientific Node. And that is just mayoral election. Voting for architecture style is not going to happen.