Guys really... I played yesterday again with some friends and the rubberbanding and performance issues especially with Flamehearts ship are just ridiculous.
Fokus on performance instead of making the game more and more unplayable.
Just stop adding more and more content in a world that is already full!
This game was once so cool and with the last updates you just made SoT almost unplayable.
Sadly, you are not even listening to the people that play your game.
They are a business, they do need to draw new players. That being said they have mentioned attempting this sort of focus. I think insiders have shown though with a live service game trying to test things in isolation just doesn't work. Its how each new feature interact with others that causes the unexpected issues.
@mrfoleytv I think the better solution is vaulting old content on rotation until the engine is upgraded (if the engine is ever upgraded).
Going into a "maintenance mode" would turn off the casual playerbase and keep it off the radar of new players.
You have to remember that the overwhelming majority of the playerbase doesn't proactively engage in PvP...which is the only part of the game that is really in a noticeably bad state. Sure there's some hiccups in PvE, but it mostly gets shrugged off because you still get the win condition. Whereas on the PvP side of the game, wins come on narrow margins at times and one game-hiccup will leave you with a sour taste.
Vaulting content would allow for new content to continue to be intoduced and theoretically leave server performance in a much better state.
You are somewhat right, but if you draw new players and the game keeps getting more unstable, then the new playerbase will not play in long term...
Don't know, but atm it is in a very bad state and we get more and more performance hungry things...
@SweetSandMan
That would be great!
@mrfoleytv said in Stop make more content and get a stable performance for SOT:
Guys really... I played yesterday again with some friends and the rubberbanding and performance issues especially with Flamehearts ship are just ridiculous.
Fokus on performance instead of making the game more and more unplayable.Just stop adding more and more content in a world that is already full!
This game was once so cool and with the last updates you just made SoT almost unplayable.
Sadly, you are not even listening to the people that play your game.
this approach would be bad for business
@mrfoleytv said in Stop make more content and get a stable performance for SOT:
You are somewhat right, but if you draw new players and the game keeps getting more unstable, then the new playerbase will not play in long term...
Don't know, but atm it is in a very bad state and we get more and more performance hungry things...
I'll tie into the commentary on my previous post...
Remember, the absolute overwhelming majority of players doesn't proactively engage in PvP or even interaction with other crews of any kind. Casual/new players that are just island hopping and trying to figure stuff out are not being noticeably impacted by the abysmal state of the game.
@SweetSandMan
That would be great!
👌
Start with the Shrines/Treasuries...vault them for a season or something, then the next season bring them back and vault the sea forts, then next season bring them back and vault something else.
Anything to get some immediate performance improvements for the dedicated playerbase.
@sweetsandman said in Stop make more content and get a stable performance for SOT:
Start with the Shrines/Treasuries...vault them for a season or something, then the next season bring them back and vault the sea forts, then next season bring them back and vault something else.
Anything to get some immediate performance improvements for the dedicated playerbase.
If this was going to boost performance, they would have done it already. Instead, they do the opposite by adding more things like the Skeleton Camps.
That seems to suggest that areas on the map have very little impact on server performance.
@d3adst1ck said in Stop make more content and get a stable performance for SOT:
@sweetsandman said in Stop make more content and get a stable performance for SOT:
Start with the Shrines/Treasuries...vault them for a season or something, then the next season bring them back and vault the sea forts, then next season bring them back and vault something else.
Anything to get some immediate performance improvements for the dedicated playerbase.
If this was going to boost performance, they would have done it already.
Would they have, though? I feel like Rare still has PTSD from being lambasted for having a content-less game at launch.
If it wouldn't boost server performance, then fine whatever. Neither of us is a dev for this game and has no idea if it would or wouldn't help. That said, it's an undeniable fact that the performance of the game went off an absolute cliff starting with Season 4 when Shrines/Treasuries were introduced and has been on a steady decline since. Heck, even Season 3 when the Pirate's Life TTs were introduced and the map was expanded to accommodate caused some unsavory performance.
Hit-reg was really the only notable "performance" issue before Season 3 went live. Sure, there were some bugs, but the game was largely stable.
@sweetsandman said in Stop make more content and get a stable performance for SOT:
@d3adst1ck said in Stop make more content and get a stable performance for SOT:
@sweetsandman said in Stop make more content and get a stable performance for SOT:
Start with the Shrines/Treasuries...vault them for a season or something, then the next season bring them back and vault the sea forts, then next season bring them back and vault something else.
Anything to get some immediate performance improvements for the dedicated playerbase.
If this was going to boost performance, they would have done it already.
Would they have, though? I feel like Rare still has PTSD from being lambasted for having a content-less game at launch.
If it wouldn't boost server performance, then fine whatever. Neither of us is a dev for this game and has no idea if it would or wouldn't help. That said, it's an undeniable fact that the performance of the game went off an absolute cliff starting with Season 4 when Shrines/Treasuries were introduced and has been on a steady decline since. Heck, even Season 3 when the Pirate's Life TTs were introduced and the map was expanded to accommodate caused some unsavory performance.
Hit-reg was really the only notable "performance" issue before Season 3 went live. Sure, there were some bugs, but the game was largely stable.
Performance has always been all over the place. I can remember encountering intense lag when approaching specific galleons, while other ones on the same server would be completely fine, long before the season system even existed.
@d3adst1ck I don’t know, what @SweetSandMan says does make sense.
Drew said in the last SoT news video that they have identified server merging through diving (HG/voyages/on-demand WEs) to be causing significant server instability which they are focusing on fixing. However this was kind of know since when diving first got introduced in S8 with countless bugs with the ship being uninteractable, spawning with missing pieces like no cannons or wheel and extreme stutter/rubberbanding when diving many times without sinking (15+ streaks). Yet, Rare went ahead and made a whole Season (S11) based around this rather buggy/server taxing mechanic of constantly diving, probably increasing the server strain tenfold by increasing the amount of server dive merges. They presumably did this because of the concept being so cool and with the degradation of server performance probably being accepted as a manageable side effect.
@SweetSandMan has a good suggestion. A lot of the current map could be sunset/vaulted through the usage of instances. There is no reason for the Pirates Life tall tale locations to be on the main map, it only opens up them to griefing. The sunken pearl could easily be instanced (go to a portal and then dive down to do the TT), same for the coral fortress.
The sunken kingdom is a bit trickier but the amount of locations could definitely be reduced, even half of the shrines and treasuries could be removed in order to increase server health and make way for new content to replace them.
@sweetsandman said in Stop make more content and get a stable performance for SOT:
Start with the Shrines/Treasuries...vault them for a season or something, then the next season bring them back and vault the sea forts, then next season bring them back and vault something else.
Anything to get some immediate performance improvements for the dedicated playerbase.
Three months without a certain feature seems too long to me.
Instead of vaulting a set of something, introduce two (or perhaps more) types of servers: one without treasuries and shrines and one without seaforts for example. Content would still be there but just turned off, no reason to have them maintain two types of servers.
You'll land on one of those randomly and if you land on a server that doesn't have the content you're looking for, you can dive to one.
@lem0n-curry said in Stop make more content and get a stable performance for SOT:
@sweetsandman said in Stop make more content and get a stable performance for SOT:
Start with the Shrines/Treasuries...vault them for a season or something, then the next season bring them back and vault the sea forts, then next season bring them back and vault something else.
Anything to get some immediate performance improvements for the dedicated playerbase.
Three months without a certain feature seems too long to me.
Instead of vaulting a set of something, introduce two (or perhaps more) types of servers: one without treasuries and shrines and one without seaforts for example. Content would still be there but just turned off, no reason to have them maintain two types of servers.
You'll land on one of those randomly and if you land on a server that doesn't have the content you're looking for, you can dive to one.
That's going to cause issues with merging if you happen to be in an area that is not present on one server but exists on the other one.
@d3adst1ck said in Stop make more content and get a stable performance for SOT:
@lem0n-curry said in Stop make more content and get a stable performance for SOT:
@sweetsandman said in Stop make more content and get a stable performance for SOT:
Start with the Shrines/Treasuries...vault them for a season or something, then the next season bring them back and vault the sea forts, then next season bring them back and vault something else.
Anything to get some immediate performance improvements for the dedicated playerbase.
Three months without a certain feature seems too long to me.
Instead of vaulting a set of something, introduce two (or perhaps more) types of servers: one without treasuries and shrines and one without seaforts for example. Content would still be there but just turned off, no reason to have them maintain two types of servers.
You'll land on one of those randomly and if you land on a server that doesn't have the content you're looking for, you can dive to one.
That's going to cause issues with merging if you happen to be in an area that is not present on one server but exists on the other one.
Not if you would only merge into the same type of server.
The seafort islands would still exist on non-seafort servers, but quite empty (assuming it's not the island and building itself that would cause performance issues) as would the treasuries but no squirly whirly above them and no entrance (and no content inside) (same assumption). They would still appear on the map as well, perhaps with a suitable icon when they're disabled.
@lem0n-curry said in Stop make more content and get a stable performance for SOT:
@d3adst1ck said in Stop make more content and get a stable performance for SOT:
@lem0n-curry said in Stop make more content and get a stable performance for SOT:
@sweetsandman said in Stop make more content and get a stable performance for SOT:
Start with the Shrines/Treasuries...vault them for a season or something, then the next season bring them back and vault the sea forts, then next season bring them back and vault something else.
Anything to get some immediate performance improvements for the dedicated playerbase.
Three months without a certain feature seems too long to me.
Instead of vaulting a set of something, introduce two (or perhaps more) types of servers: one without treasuries and shrines and one without seaforts for example. Content would still be there but just turned off, no reason to have them maintain two types of servers.
You'll land on one of those randomly and if you land on a server that doesn't have the content you're looking for, you can dive to one.
That's going to cause issues with merging if you happen to be in an area that is not present on one server but exists on the other one.
Not if you would only merge into the same type of server.
The seafort islands would still exist on non-seafort servers, but quite empty (assuming it's not the island and building itself that would cause performance issues) as would the treasuries but no squirly whirly above them and no entrance (and no content inside) (same assumption). They would still appear on the map as well, perhaps with a suitable icon when they're disabled.
There is no content inside when no one is in there.
I don't know if making the matchmaking side more complicated (since it needs to now track different server variants within each stamp) is a good solution either.
@d3adst1ck said in Stop make more content and get a stable performance for SOT:
There is no content inside when no one is in there.
If so, I don't think removing treasuries and shrines would do much for server performance. Perhaps sailing around with 20 something items from the treasury would cause lag, but then crews would find something else to stack loot, making such an adjustment moot.
I don't know if making the matchmaking side more complicated (since it needs to now track different server variants within each stamp) is a good solution either.
Indeed, I didn't take the different servers for xbox+controller or Ps5 into account, which numbers may be small and halving them to merge into might cause less merging possibilities for those.
