Jump to content

one (possibly) reasonable QOL toggle


is this a good idea?  

12 members have voted

  1. 1. is this a good idea?

    • yes
      4
    • yes, but not as a toggle(tell me what your thoughts are?)
      0
    • i dont have an opinion/fire doesnt bother me
      5
    • no
      3


Recommended Posts

if it is not too far-fetched to suggest i'd like to offer up as a suggestion a "creative mode" toggle whose sole function is that it prevents player-built structures from catching fire. it wouldnt do anything else and could be off by default but for people who make base worlds, people who host pubs and people who just cannot abide by the current style of all things being burnable.

 

this of course isnt just for kicks either though, there are lots of people who turn off hounds and wildfires and download mods all to prevent structures from going to ashes that would be a lot calmer and more bold with their play if they could have an assurance that they'd not lose 50+ hours of resource gathering if they stepped away from their base for a couple in-game days. it would also encourage people to let others play in their worlds and go into more pubs if they were not afraid of things catching alight. this also would not interfere with people who do NOT want to have that extra bit of insurance as they would never have a reason to use the toggle. they could continue playing how they would like as well

 

so what do you think? is it too much?

Wouldn't a simpler solution be to just make Wildfires off by default?

DST does need some basic ownership/preferred players for server owners to control how the play takes place. I've never had the misfortune of a rando burning down the Florid base, but it's definitely happened that someone spawns and cause a Hound Wave to attack the base unexpectedly. Perhaps new players who enter a world after the first year spawn in as ghosts and need another player to revive them before they can use the Florid. 

I do agree that an "Indestructible Stations" slider would be wonderful. Only Giants should be able to **** the players, not other players, not Hounds.

4 hours ago, ArubaroBeefalo said:

Not always since devs need time and resources for it

This exactly- there’s already an option to turn hounds and wildfires off, though why anyone would want to do that is beyond my own logic: Because at that point you should just remove Summer as a weather season.. there’s very little going for Summer, and if you take away what makes Summer, Summer you may as well toggle it off.

The only problem with that is Desert Cactus won’t bloom so you can get Cactus flower to finish upgrading pearls dumb hermit home.. I had to delete one of my world saves when I found out this the hard way.

I always turn summer off or put a password on my room and play through it by myself to avoid going through Summer online with other players: Plain and Simple either intentionally or unintentionally: It’s the season where unaware or totally aware players can PASSIVELY cause the most destruction to your worlds by simply just being Idle in an area while it goes up in flames.

If all players would leave the area and explore the world away from base, base doesn’t spontaneously combust in their absence- same with Meteor fields hitting it, but unaware players just being idle in the wrong place at the wrong time can cause wide scale destruction.

BUT.. you can also turn Off Wildfires, Hounds and even Meteor Showers Already- so for the devs to spend anymore time or resources on it would just be wasted time and resources they could’ve spent elsewhere on new content.

Maybe there should be some new World Gen pre-sets that have certain features already toggled off (such as a Mega Base mode with Wildfires already turned off) But I don’t feel like they should spend a ton of time and resources doing something we can already do ourselves.

This holds extra especially true for PC players who can just download a Mod or request some super nice individual to create one for them so they can have the game play exactly the way they want it to.

And I’ll admit as a console player I’m slightly jealous of Mods, because in order for us console players to be able to play as Walani, Wilbur, Woodlegs, Wheeler, Wilba or Wagstaff in Don’t Starve Together** We would either A: Have to buy a PC to use the mods your already enjoying. B: Hope that Klei someday allows console players to join PC worlds that have these mods available to use... or C: Pray that Klei adds those characters to the game Officially.

And I would much rather they do that, then to spend time fixing/altering features we can Already simply just turn off.

But, as always that’s just my opinion: Others may not feel the same way.

19 hours ago, JaxckLl said:

Wouldn't a simpler solution be to just make Wildfires off by default?

DST does need some basic ownership/preferred players for server owners to control how the play takes place. I've never had the misfortune of a rando burning down the Florid base, but it's definitely happened that someone spawns and cause a Hound Wave to attack the base unexpectedly. Perhaps new players who enter a world after the first year spawn in as ghosts and need another player to revive them before they can use the Florid. 

I do agree that an "Indestructible Stations" slider would be wonderful. Only Giants should be able to **** the players, not other players, not Hounds.

not really? some people like wildfires and wildfire management and it wouldn't prevent hounds or players from starting fires. this would be a way to encourage keeping wildfires, hounds and other players toggled on so that the person hosting can have a richer experience with their gameplay without it coming at the cost of a base or three. considering the conversations that have been going on in the forum over all three of these sources of fire(and how base destruction is the worst part of two and a notable problem with the third) it makes sense to me

 

as far as "indestructible" goes do you mean sinking or soaking or hammering as well as burning?

I'd rather a better method of fire fighting in an item. It's always a hassle to deal with the aftermath of a fire, but can be very rewarding to stop a blaze before it does great damage. 

A malbatross fan that extinguishes the screen worth of smoldering would be a start.

13 hours ago, chirsg said:

I'd rather a better method of fire fighting in an item. It's always a hassle to deal with the aftermath of a fire, but can be very rewarding to stop a blaze before it does great damage. 

A malbatross fan that extinguishes the screen worth of smoldering would be a start.

it can be but what about when you are days away from the fire? you still have to deal with the aftermath but not have the ability to intervene

3 hours ago, gaymime said:

it can be but what about when you are days away from the fire? you still have to deal with the aftermath but not have the ability to intervene

???? Does the PC version of the game run drastically different than console or something? I have never had Wildfires happen to my base when I leave the bases render distance.. during Summer I spend the entire season out on adventure and far away from my base so it doesn’t you know.. catch fire. (It literally can’t catch fire cause it’s not in render distance..)

Now also keep in mind I play mostly alone so there’s not other players in the game with me very often: And those other players could be within rendering distance of your base: Which even if your not near the base THEY still are: And it will Smolder.

Maybe that is what is happening to You? That or the PC version just continues to have things happen off screen out of render distance where as on Xbox it’s a known method of leave base render and base can’t be harmed.

29 minutes ago, Mike23Ua said:

???? Does the PC version of the game run drastically different than console or something? I have never had Wildfires happen to my base when I leave the bases render distance.. during Summer I spend the entire season out on adventure and far away from my base so it doesn’t you know.. catch fire. (It literally can’t catch fire cause it’s not in render distance..)

Now also keep in mind I play mostly alone so there’s not other players in the game with me very often: And those other players could be within rendering distance of your base: Which even if your not near the base THEY still are: And it will Smolder.

Maybe that is what is happening to You? That or the PC version just continues to have things happen off screen out of render distance where as on Xbox it’s a known method of leave base render and base can’t be harmed.

players can start fires while you are away from a base, they can either light them up or they can be nearby while a smoulder starts or they can use something that causes fire on accident or a monster with fire properties can spawn near them while at base. this comment is relevant in worlds where you are not the only player. in those cases where you are not the reason the fire started there can still be fires and there is nothing you can do about it since you are not there to respond

7 minutes ago, gaymime said:

players can start fires while you are away from a base, they can either light them up or they can be nearby while a smoulder starts or they can use something that causes fire on accident or a monster with fire properties can spawn near them while at base. this comment is relevant in worlds where you are not the only player. in those cases where you are not the reason the fire started there can still be fires and there is nothing you can do about it since you are not there to respond

This is exactly the reason I password lock my public worlds (that I’ve accidentally forgotten I left Summer toggled on for) until Summer is over- either intentionally or unintentionally it’s the season players can cause the most widespread destruction to your worlds. 
 

Those are for worlds I want to keep- but otherwise I just host worlds that anything goes and I know it’s going to go to hell in a waste basket eventually.

in those worlds (the ones I don’t mind losing) I set the world Gen to random season start and season lengths so Summer can happen randomly. :) 

17 minutes ago, Mike23Ua said:

This is exactly the reason I password lock my public worlds (that I’ve accidentally forgotten I left Summer toggled on for) until Summer is over- either intentionally or unintentionally it’s the season players can cause the most widespread destruction to your worlds. 
 

Those are for worlds I want to keep- but otherwise I just host worlds that anything goes and I know it’s going to go to hell in a waste basket eventually.

in those worlds (the ones I don’t mind losing) I set the world Gen to random season start and season lengths so Summer can happen randomly. :) 

which is fair. the reasoning behind the toggle though is it would give you peace of mind so you could have more worlds that were not password protected while still keeping your structures safe(and so you could visit more worlds hosted by others)

Archived

This topic is now archived and is closed to further replies.

Please be aware that the content of this thread may be outdated and no longer applicable.

×
  • Create New...