Vyril wrote: » SongRune wrote: » Vyril wrote: » Strevi wrote: » Around 8-10k concurrent users per server is projected.[2][3][4][5] Initially there will be a limited number of registered accounts (approximately 15,000) per server to help mitigate login queues.[6] This limit will increase over time to around 50,000 registered accounts per server.[6][7][8] Spodos wrote: » and then allow people to whitelist friends / guildies so you can still see their costumes. So theoretically the server should be able to save the setting of each player in relationship to the other 50 000 registered accounts That means 50 000 to the power of 50 000 = "Invalid input" worse than 5000 ^ 5000 = "Overflow" How many bytes we need to store the 50k ^ 50k "white / black" setting? No? That's how ignore lists work for chat. It's 50,000 * 50,000. Each user has white/black tags for 50,000 other players. The server as a whole has 50,000 users. Also, the answer is 6.25 KB per user. Which doesn't even need to ever be on the server side, but if you wanted to sync it, it'd still cost under $7/month in AWS S3 storage for the whole server. Nonetheless, you'd never bother storing it that way, because an individual user on average isn't gonna have even 1,000 entries on their list. You don't even need the 6 KB, in that case. Still not how that works. They use relational databases. Which you only write a record for off. In which case is only 1byte per entry. Because at the worst case scenario only be turning off a few thousands players. Additionally you could just have a flag to turn all players off which also is just 1byte. I dont know what type of data plans you're expecting to use but I work with petabytes worth of data and 6kb is like .01 cents.
SongRune wrote: » Vyril wrote: » Strevi wrote: » Around 8-10k concurrent users per server is projected.[2][3][4][5] Initially there will be a limited number of registered accounts (approximately 15,000) per server to help mitigate login queues.[6] This limit will increase over time to around 50,000 registered accounts per server.[6][7][8] Spodos wrote: » and then allow people to whitelist friends / guildies so you can still see their costumes. So theoretically the server should be able to save the setting of each player in relationship to the other 50 000 registered accounts That means 50 000 to the power of 50 000 = "Invalid input" worse than 5000 ^ 5000 = "Overflow" How many bytes we need to store the 50k ^ 50k "white / black" setting? No? That's how ignore lists work for chat. It's 50,000 * 50,000. Each user has white/black tags for 50,000 other players. The server as a whole has 50,000 users. Also, the answer is 6.25 KB per user. Which doesn't even need to ever be on the server side, but if you wanted to sync it, it'd still cost under $7/month in AWS S3 storage for the whole server. Nonetheless, you'd never bother storing it that way, because an individual user on average isn't gonna have even 1,000 entries on their list. You don't even need the 6 KB, in that case.
Vyril wrote: » Strevi wrote: » Around 8-10k concurrent users per server is projected.[2][3][4][5] Initially there will be a limited number of registered accounts (approximately 15,000) per server to help mitigate login queues.[6] This limit will increase over time to around 50,000 registered accounts per server.[6][7][8] Spodos wrote: » and then allow people to whitelist friends / guildies so you can still see their costumes. So theoretically the server should be able to save the setting of each player in relationship to the other 50 000 registered accounts That means 50 000 to the power of 50 000 = "Invalid input" worse than 5000 ^ 5000 = "Overflow" How many bytes we need to store the 50k ^ 50k "white / black" setting? No? That's how ignore lists work for chat.
Strevi wrote: » Around 8-10k concurrent users per server is projected.[2][3][4][5] Initially there will be a limited number of registered accounts (approximately 15,000) per server to help mitigate login queues.[6] This limit will increase over time to around 50,000 registered accounts per server.[6][7][8] Spodos wrote: » and then allow people to whitelist friends / guildies so you can still see their costumes. So theoretically the server should be able to save the setting of each player in relationship to the other 50 000 registered accounts That means 50 000 to the power of 50 000 = "Invalid input" worse than 5000 ^ 5000 = "Overflow" How many bytes we need to store the 50k ^ 50k "white / black" setting?
Around 8-10k concurrent users per server is projected.[2][3][4][5] Initially there will be a limited number of registered accounts (approximately 15,000) per server to help mitigate login queues.[6] This limit will increase over time to around 50,000 registered accounts per server.[6][7][8]
Spodos wrote: » and then allow people to whitelist friends / guildies so you can still see their costumes.
Noaani wrote: » The idea 0f a cosmetic toggle has already been rejected by Intrepid. Their thought - and I agree - is that if you spend money to have your character look a specific way, you should be able to know other players will see your character that way. The idea that gear is a representation of what you have achieved in a game where all gear is able to be traded - even after use - is also just outdated.
Craiken wrote: » In this fantasy world, we all have the power to look however we want. Will it be weird when your tank charges a dragon looking like this? Yes, it will. But it's just some weird fantasy power we have.
ClintHardwood wrote: » I agree with the OP for many reasons, but clearly Intrepid needs that cosmetics money. Since there's a no-cosmetics functionality in the game already, during large PvP events and such, we'll just have to wait till a 3rd party add-on allows us to toggle cosmetics in all other scenarios.
Natasha wrote: » ClintHardwood wrote: » I agree with the OP for many reasons, but clearly Intrepid needs that cosmetics money. Since there's a no-cosmetics functionality in the game already, during large PvP events and such, we'll just have to wait till a 3rd party add-on allows us to toggle cosmetics in all other scenarios. Imagine getting banned turning off cosmetics.
ClintHardwood wrote: » Natasha wrote: » ClintHardwood wrote: » I agree with the OP for many reasons, but clearly Intrepid needs that cosmetics money. Since there's a no-cosmetics functionality in the game already, during large PvP events and such, we'll just have to wait till a 3rd party add-on allows us to toggle cosmetics in all other scenarios. Imagine getting banned turning off cosmetics. Clientside modifications are undetectable. I'd rather see the actual gear someone I'm PvPing against is wearing than the clown suit he bought from the store.