StarMade - PvP & PvE balance, Perspective & Direction

    schema

    Cat God
    Joined
    Feb 17, 2012
    Messages
    1,552
    Reaction score
    2,604
    • Schine
    Hello Players,


    This is more of a blog post about the general direction of the game.


    With the recent updates there have been a lot of new build mechanics and restrictions that were controversial. However, they seemed necessary to solve certain problems with people exploiting certain aspects of the mechanics. Most players never plan or intent to abuse these mechanics but they were still negatively affected by them. New players are also affected by the added complexity. Even the existence of an additional number while building has a negative effect. Understandably, a lot of those players asked the question “Why is this even a thing?”.


    Restricting the build mechanics is most of the time affecting the wrong people, and a lot of times they are also not 100% effective in what they are trying to prevent. Making them more severe would put even more restriction on the whole system. Reducing them would make them completely ineffective.


    With all that in mind I came to the realization that my perspective on balance might be a bit off. In trying to put out fires, new fires are coming up while development of other things suffers. We have been focusing on fighting the extreme cases of exploits way to much.


    The conclusion of this is that I want to go back to those things that make the game fun.

    To explain it better: The game should be fun for one or a group of players that are enjoying the game without going out of their way to exploit mechanics. While there still need to be things to prevent these exploits, it will be done with a different perspective. Measures that solely exist to prevent to exploitation will be put into a rule system, so a server admin can apply them. This rule system will be quick and easy to setup, which will be explained a bit later.


    We will still be sticking with the basic premise of reactors and stabilizers but will be simplifying things a fair bit.

    The first things that will be removed from the game is integrity and the reactor stream between reactor and stabilizers. Also, while I can not promise for sure, the required reactor stabilization distance will likely be reduced.


    Server Rules

    The server rule system will work as follows:


    The server admin picks one or multiple conditions with either “all conditions must be true” or “one of the conditions must be true”. While there will be other affected areas, this explanation will be for structures. This means that these conditions will be checked while a player builds or spawns a ship. These conditions will include a reactivation of integrity, the stability stream, ship size, mass, dimension, block counts per type, weapon strength, shield strength and a lot more.


    After the admin picked a set of conditions, they can choose from one or more actions. These will range from very light “ship weapons are disabled while conditions are true” to more harsh “remove ship” or even “ban player”. It’s the admin’s choice. They will also have the option to warn players on certain actions.


    A simple rule would be:


    • “If block count is over 1 million, deactivate the ship’s power”
    The player would then be notified in their structure view in build mode that a their ship is currently triggering the rule.


    Another rule would be:

    • If integrity is in the negatives, the ship is disabled.
      The condition can be more soft like “mark ship for admins”. Admins would be able to track those marked ships in a panel, as well as the blueprints.
    This would exactly emulate how the integrity works right now.

    For normal gameplay all integrity would not be visible as long as the player is on a server that doesn’t use a rule that relates to integrity. Same is true for the stabilization stream, and other things that will be removed for simplification.


    When I make the game I think about people that have fun together player the game. Exploring, building, fighting. Competitiveness is also nice as long as I doesn't go to extremes. So I want to focus on that fun part. Unlike many games nowadays, I don't want to create an esport. If you want to play hardcore, you are welcome to do so, but you will have to make your own rules.


    With this, development can move a lot more freely and will have a lot more resources available for other things. For anything that might be exploitive, conditions will be added to help a server effectively detect and remove it from their server if they so wish. We will be also providing default options for servers to quickly setup. These default options will be based upon what rules are typically set on the different types of servers PvP, PvE, RP, Building etc


    This is all of course not a complete fix to all balance problems, but it enables us to create a balance for a specific scenario instead of doing the impossible task of coming up with a balance that works in a possible scenarios. For example, the intended vanilla balance will be based on economy also, something that currently doesn’t matter on some servers, which in turn completely changes the scenario and the requirements for any balance. By focusing on a specific scenario and then letting the admins control what kind of play they want to see on a server, we can reduce the amount of forced restrictions considerably making building and the game a lot more fun.


    The rule GUI will come equipped with a simple way to create new rules. Also it will be possible to create and export/import ruleset templates. There will also be some general rulesets available that an admin can choose from like “Creative Build”, “Restricted Pvp” or “Hardcore PvP Open”.


    List of Conditions and reactions
    There are a lot of possible conditions and actions. I’ll be compiling a list shortly with all possible conditions and actions I can come up with. Since any action will be specific to a server to use them I’m willing to implement pretty much any request a server admin has for a rule.


    Possible conditions would include

    • ship size

    • ship mass

    • block count (per type)

    • system count (specific to system)

    • integrity (which would activate the integrity GUI and stats for all peple on that server. Otherwise integrity would be completely removed)

    • Shield size

    • Reactor level

    • A lot more. Whatever we can come up with.

    Actions would affect the entity & creator/spawner of the entity and would range from hidden to severe including:

    • Mark entity for admins. This entity is then trackable by the admins in a panel

    • Mark entity for everyone in hud/name

    • Disable certain systems

    • Add an effect (like a reactor effect) to the vessel

    • Disable completely

    • Warn player for amount of time

    • Remove completely (conditions can be chained, so that would for example be after a warning)

    • Kick/Ban player (same as above)

    This would also enable servers to implement buffs for certain builds (e.g. bigger stations) by applying certain effects. This would be a lot easier than modifying the config. Also it would be compatible with most updates of the game.




    General
    In general there have been a few adjustments to my perspective as well. With the universe update coming up, I will be going moving away from trying to middleground on things that would cost extra time. Too many “you can do either this or that” choices for how the basics of the game work are not good for complexity and code. This is not directed on gameplay, in fact gameplay should be enriched with more options, but for things like having an option to use old deprecated things still (old turrets etc are a good example).


    The universe update is pretty huge in scope, but all in all I’m looking very much to 100% dive into it. The basics are already there. Most of the old systems have been overhauled internally. The few old ones that are left will be overhauled at the beginning of the update (amongst other things AI, fleets, the basic loading system and sector transitions). The universe will be torn down and recreated according to what we planned. And then it will be filled with new and interesting things, adding gameplay and things to do, as well as making the surroundings a lot more recognizable.


    Thanks for playing StarMade,

    • schema
     

    Valiant70

    That crazy cyborg
    Joined
    Oct 27, 2013
    Messages
    2,189
    Reaction score
    1,167
    • Thinking Positive
    • Purchased!
    • Legacy Citizen 4
    The server admin picks one or multiple conditions with either “all conditions must be true” or “one of the conditions must be true”. While there will be other affected areas, this explanation will be for structures. This means that these conditions will be checked while a player builds or spawns a ship. These conditions will include a reactivation of integrity, the stability stream, ship size, mass, dimension, block counts per type, weapon strength, shield strength and a lot more.


    After the admin picked a set of conditions, they can choose from one or more actions. These will range from very light “ship weapons are disabled while conditions are true” to more harsh “remove ship” or even “ban player”. It’s the admin’s choice. They will also have the option to warn players on certain actions.
    As a server admin, I'm very happy to see this. We already have certain rules about ship sizes for the sake of server stability, but we have to police and enforce these rules manually, which isn't ideal. Being able to write most of our ship rules into the game engine itself is a much better solution.

    I'd like to see rules for:
    • Total docked entities
    • Chain-dock depth
    • Number of turrets
    • Outputs per weapon computer
    • Thrust to mass ratio
    The universe will be torn down and recreated according to what we planned. And then it will be filled with new and interesting things, adding gameplay and things to do, as well as making the surroundings a lot more recognizable.
    Will (or could) the overhaul include removing the block-shaped systems? To me it would make more sense to just mark out roughly-spherical areas of sectors as star systems rather than imposing an artificial grid. It would allow more variation in the size of star systems too.
     
    Joined
    Mar 18, 2014
    Messages
    292
    Reaction score
    153
    • Arrrty
    • TwitchCon 2015
    • Legacy Citizen 5
    For normal gameplay all integrity would not be visible as long as the player is on a server that doesn’t use a rule that relates to integrity. Same is true for the stabilization stream, and other things that will be removed for simplification.
    This makes sense, though it could also be cool to have client-side options to enable viewing aspects which would normally be hidden by the current server rules. This could make it easier to build ships which also satisfy some rules not present on the current server (for wider use, if the build happens to have some flexibility), or to check out a downloaded blueprint and view it "as the builder intended" without having to change rules in a single-player game first.

    So if, say, stabilizer streams are disabled normally but can be enabled by a rule, a player might want to place some stream nodes if they have a few blocks of extra space. Or similar thing with integrity, if the builder has plenty of space then they may want to adapt the reactor/shields/etc. shape to make the ship more adaptable for use on other servers.

    Having the option(s) be available and dynamic in the in-game UI would be ideal, and of course would only affect the information which the local player can see and not the actual gameplay.
     
    Joined
    Feb 1, 2015
    Messages
    214
    Reaction score
    558
    Hello Players,


    This is more of a blog post about the general direction of the game.


    With the recent updates there have been a lot of new build mechanics and restrictions that were controversial. However, they seemed necessary to solve certain problems with people exploiting certain aspects of the mechanics. Most players never plan or intent to abuse these mechanics but they were still negatively affected by them. New players are also affected by the added complexity. Even the existence of an additional number while building has a negative effect. Understandably, a lot of those players asked the question “Why is this even a thing?”.


    Restricting the build mechanics is most of the time affecting the wrong people, and a lot of times they are also not 100% effective in what they are trying to prevent. Making them more severe would put even more restriction on the whole system. Reducing them would make them completely ineffective.


    With all that in mind I came to the realization that my perspective on balance might be a bit off. In trying to put out fires, new fires are coming up while development of other things suffers. We have been focusing on fighting the extreme cases of exploits way to much.


    The conclusion of this is that I want to go back to those things that make the game fun.

    To explain it better: The game should be fun for one or a group of players that are enjoying the game without going out of their way to exploit mechanics. While there still need to be things to prevent these exploits, it will be done with a different perspective. Measures that solely exist to prevent to exploitation will be put into a rule system, so a server admin can apply them. This rule system will be quick and easy to setup, which will be explained a bit later.


    We will still be sticking with the basic premise of reactors and stabilizers but will be simplifying things a fair bit.

    The first things that will be removed from the game is integrity and the reactor stream between reactor and stabilizers. Also, while I can not promise for sure, the required reactor stabilization distance will likely be reduced.


    Server Rules

    The server rule system will work as follows:


    The server admin picks one or multiple conditions with either “all conditions must be true” or “one of the conditions must be true”. While there will be other affected areas, this explanation will be for structures. This means that these conditions will be checked while a player builds or spawns a ship. These conditions will include a reactivation of integrity, the stability stream, ship size, mass, dimension, block counts per type, weapon strength, shield strength and a lot more.


    After the admin picked a set of conditions, they can choose from one or more actions. These will range from very light “ship weapons are disabled while conditions are true” to more harsh “remove ship” or even “ban player”. It’s the admin’s choice. They will also have the option to warn players on certain actions.


    A simple rule would be:


    • “If block count is over 1 million, deactivate the ship’s power”
    The player would then be notified in their structure view in build mode that a their ship is currently triggering the rule.


    Another rule would be:

    • If integrity is in the negatives, the ship is disabled.
      The condition can be more soft like “mark ship for admins”. Admins would be able to track those marked ships in a panel, as well as the blueprints.
    This would exactly emulate how the integrity works right now.

    For normal gameplay all integrity would not be visible as long as the player is on a server that doesn’t use a rule that relates to integrity. Same is true for the stabilization stream, and other things that will be removed for simplification.


    When I make the game I think about people that have fun together player the game. Exploring, building, fighting. Competitiveness is also nice as long as I doesn't go to extremes. So I want to focus on that fun part. Unlike many games nowadays, I don't want to create an esport. If you want to play hardcore, you are welcome to do so, but you will have to make your own rules.


    With this, development can move a lot more freely and will have a lot more resources available for other things. For anything that might be exploitive, conditions will be added to help a server effectively detect and remove it from their server if they so wish. We will be also providing default options for servers to quickly setup. These default options will be based upon what rules are typically set on the different types of servers PvP, PvE, RP, Building etc


    This is all of course not a complete fix to all balance problems, but it enables us to create a balance for a specific scenario instead of doing the impossible task of coming up with a balance that works in a possible scenarios. For example, the intended vanilla balance will be based on economy also, something that currently doesn’t matter on some servers, which in turn completely changes the scenario and the requirements for any balance. By focusing on a specific scenario and then letting the admins control what kind of play they want to see on a server, we can reduce the amount of forced restrictions considerably making building and the game a lot more fun.


    The rule GUI will come equipped with a simple way to create new rules. Also it will be possible to create and export/import ruleset templates. There will also be some general rulesets available that an admin can choose from like “Creative Build”, “Restricted Pvp” or “Hardcore PvP Open”.


    List of Conditions and reactions
    There are a lot of possible conditions and actions. I’ll be compiling a list shortly with all possible conditions and actions I can come up with. Since any action will be specific to a server to use them I’m willing to implement pretty much any request a server admin has for a rule.


    Possible conditions would include

    • ship size

    • ship mass

    • block count (per type)

    • system count (specific to system)

    • integrity (which would activate the integrity GUI and stats for all peple on that server. Otherwise integrity would be completely removed)

    • Shield size

    • Reactor level

    • A lot more. Whatever we can come up with.

    Actions would affect the entity & creator/spawner of the entity and would range from hidden to severe including:

    • Mark entity for admins. This entity is then trackable by the admins in a panel

    • Mark entity for everyone in hud/name

    • Disable certain systems

    • Add an effect (like a reactor effect) to the vessel

    • Disable completely

    • Warn player for amount of time

    • Remove completely (conditions can be chained, so that would for example be after a warning)

    • Kick/Ban player (same as above)

    This would also enable servers to implement buffs for certain builds (e.g. bigger stations) by applying certain effects. This would be a lot easier than modifying the config. Also it would be compatible with most updates of the game.




    General
    In general there have been a few adjustments to my perspective as well. With the universe update coming up, I will be going moving away from trying to middleground on things that would cost extra time. Too many “you can do either this or that” choices for how the basics of the game work are not good for complexity and code. This is not directed on gameplay, in fact gameplay should be enriched with more options, but for things like having an option to use old deprecated things still (old turrets etc are a good example).


    The universe update is pretty huge in scope, but all in all I’m looking very much to 100% dive into it. The basics are already there. Most of the old systems have been overhauled internally. The few old ones that are left will be overhauled at the beginning of the update (amongst other things AI, fleets, the basic loading system and sector transitions). The universe will be torn down and recreated according to what we planned. And then it will be filled with new and interesting things, adding gameplay and things to do, as well as making the surroundings a lot more recognizable.


    Thanks for playing StarMade,

    • schema
    Yes, way to go Schema!
    Softer approach is better than all the strict rules and precise percentages.
    Pleas also think on the shield bubbles and shields in general, they would also benefit from a huge simplification and maybe even nerf them some more.

    Anyhow, looking forward to a game that does not take several hours to explain how the basics works ;)
     

    Jake_Lancia

    Official Source of Blame
    Joined
    Oct 2, 2013
    Messages
    859
    Reaction score
    1,434
    • Legacy Citizen 10
    • Competition Winner - Small Fleets
    • Community Content - Silver 2
    Pleas also think on the shield bubbles and shields in general, they would also benefit from a huge simplification and maybe even nerf them some more.
    Yes to the remove shield bubbles and going back to the older shield system; it was far simpler and less annoying to set up.

    No to the nerfing shields; if anything, shields need a buff, or weapons in general a nerf, because of how much disparity is between weapons and shielding right now.
     
    Joined
    Jan 11, 2018
    Messages
    43
    Reaction score
    57
    Just forget integrity. It was never a good solution to low-density systems, and there are now other game mechanics which adequately address this issue.

    Forget the power stream too. Unless stabilizer distance is excessively large, like it was in the early dev builds, island ships aren't worth it so there's no exploit to fix.

    Also, while I can not promise for sure, the required reactor stabilization distance will likely be reduced.
    The current stabilizer values already allow you to fill an entire ship with systems quite easily. If you reduce stabilizer distance even further, what is the point of stabilizers at all? Are they no longer intended to encourage interiors?
     
    Joined
    Feb 1, 2015
    Messages
    214
    Reaction score
    558
    Yes to the remove shield bubbles and going back to the older shield system; it was far simpler and less annoying to set up.

    No to the nerfing shields; if anything, shields need a buff, or weapons in general a nerf, because of how much disparity is between weapons and shielding right now.
    I think armour is a fun concepts, making that useless and relying on only shields as we have seen makes a boring battle, also I don't want any ship to 100% fine after a battle, more fun with some wear and tear aspects. Hell, would actually be great if shields protected and absorbed like 70% of damage, not all!
     
    Joined
    Dec 26, 2017
    Messages
    5
    Reaction score
    7
    Thank you for removing integrity :D
    That was the thing I hated the most about the Power 2.0 update.
    Shields or armor (or both) definitely need a buff since weapons currently shed through them, and I agree that bubbles should be removed since they over-complicate things.
    Keep up the hard work ^-^
     

    Sachys

    Hermit.
    Joined
    Nov 30, 2015
    Messages
    648
    Reaction score
    317
    So... looks like I can turn around on my thing of stations being dead maybe
     
    Joined
    Jul 10, 2013
    Messages
    626
    Reaction score
    486
    • Community Content - Bronze 2
    • Purchased!
    • Legacy Citizen 7
    Nice Schema. Is that you trying to apply the KISS* rule ? I hope so.

    It also to me anyway seems that it opens the door to modding...


    *Keep It Simple Stupid
     
    • Like
    Reactions: NeonSturm

    Crimson-Artist

    Wiki Administrator
    Joined
    Sep 10, 2013
    Messages
    1,667
    Reaction score
    1,641
    • Video Genius
    • Competition Winner - Stations
    • Wiki Contributor Gold
    If memory serves that was originally a streamer's reaction to E3's Halo Infinite teaser.
    no it was originally for Super Smash Bros Ultimate. It was super meme worth so ppl used it for other things.
    His channel name is Etika. Hes famous for his smash reactions. You should look up some of them hes great.
     
    • Like
    Reactions: ebr1198

    Reilly Reese

    #1 Top Forum Poster & Raiben Jackpot Winner
    Joined
    Oct 13, 2013
    Messages
    5,140
    Reaction score
    1,365
    • Legacy Citizen 8
    • Thinking Positive
    • Purchased!
    no it was originally for Super Smash Bros Ultimate. It was super meme worth so ppl used it for other things.
    His channel name is Etika. Hes famous for his smash reactions. You should look up some of them hes great.
    Guess it was someone who looks similar streaming at the time.

    *Shrug*