Tyceberg

Indeed.

If those mods do already exist, then in a way, yes, but also no. Being that this is a forum to request things be added to the base game as regular mechanics, sometimes mods with the same functionalities already exist, but do not fully fulfill the needs of the request. The oils do not necessarily need to be added to the base game as a mechanic for this, it can just as easily be accomplished with the alcohols already present in game. Soaps could like wise be made from fat and other ingredients already present in the game. So, yes, it may take a concept presented in other mods, but, no, it does not mean it has to have the same overall functionality or items as those mods ported in since the base game already has much of what would be needed to clean the resin/pitch from pots. Unless, I'm confusing what you mean?

1. Team size can, but does not always, make a difference to how things should and would be handled. And, user suggestions do indeed provide guidance to a company on which direction they should take for their customers/users. That's the nature of Feedback. 2. Against your quip; While structure can help, I don’t think its absence automatically equals poor quality. Many great works—classic books and artworks, early mods, even open-source projects—were created without strict formatting rules. Their quality came from the dedication, clarity, and passion of the creators, not from external organizational systems. These are two sides of the same coin overall. A well-written description from a conscientious modder can be just as effective as rigid fields or filters. Quality ultimately comes from the effort and clarity of the creator, not solely from the presence of predefined slots, filters, or structure. A careless or rushed creator can misuse structured fields, leading to misinformation. In contrast, someone who takes care in their unstructured description can convey precise, accurate details without needing filters. Both ways have their positives and negatives. 3. I wouldn't say unrelated entirely, but you’re absolutely right—nobody here is trying to erase or dismiss anyone’s viewpoint, they're all equally valid in the grand scheme. (Although, I'd be lying if I said your second point here didn't make me feel that way personally in some regard, but I doubt it's your intention, just like it's not mine towards anyone here.) We’re all contributing valid observations based on our own experiences: mod devs, seasoned users, industry workers, newcomers—we all bring valuable insights to the table. It’s a collaborative effort, a friendly discussion, not a debate to “win.” 4. Glad we can agree on that. The suggestions and the thoughts from everyone—including yours—has definitely added value. Whether or not Anego acts on it, we’ve collectively helped clarify what may or may not improve with this suggestion's implementation. That in itself is a success for everyone, because it provides the devs much to consider and understand towards potentially integrating this and other suggestions around the forum.

Well, what I'm about to say is purely conjecture. However, considering that this site is ran via premade templates and coding by another service (see the "Powered by Invision Community" link listed at the bottom of every page.) I doubt they have a 100% fully dedicated team for purely the website alone. You'd be amazed how often this is actually the case with smaller businesses and developers. Being a small company, this would not be cost nor time effective with how infrequently major layout or function updates are done to this site (or at least that I've seen). Their own employment opportunities page states, "Anego Studios consists of a team of passionate game developers working remotely from multiple countries. We are a loosely organized team ... we are looking for talent that we ourselves are lacking." This would indicate they might not have the man power to separate departments like that. And, from my own experiences at multiple companies over the years, nearly half or more of members outside of PR and Marketing had some form of HTML and CSS coding knowledge on top of any other languages for coding the actual game or even on top of 3D modeling knowledge. I still must disagree with it raising the quality of the site, as it does not truly add anything that isn't already available, viable or functional to the same ends as what's already there. At most it would simply maintain the status-quo as it is or even cause frustration by leading to too many options or places to check or look for and add certain information since anyone could choose to or not to use it. "... every one comes and brings different experiences," to this I do agree, however, those experiences should not be dismissed. You’re learning from someone else’s trials so you can make better decisions without wasting time or repeating every potential mistake yourself. And these are my experiences and wisdom that I have gained in my 12+ years of game development that I wished to provide. I do believe, though, we've hit an impasse in this thread that will cause us to continue to loop and repeat ourselves from here. We have all provided our full opinions and thoughts on the matter and it ultimately remains the decision of VS's Anego Studios and it's members to make. Both my comments, yours, and everyone else's provide them with insights into the logistics of the situation based on practicality of the suggested implementation and the desire of an indeterminate portion of users. With that in mind we can all be happy that we have provided to the community and wait with happy anticipation to see what happens.

My pleasure! This kind of logistical stuff is what I happily do for a career. I enjoy providing a professional opinion on these types of back-and-forth discussions. Questioning, providing rebuttals , sound-boarding off each other and so on--it's all a grand and fun process! (Just gotta have a strong backbone for criticism in those offices, haha!)

This is true. However, it is soluble in alcohol and oils can also help remove it. So, I would propose, then, that adding mechanic for filling a pot with a strong wine or other spirit, or olive oil or so, would help dissolve the pitch and clean the pot. Or even soaps based on oils and such.

All of these statements echo my previous points. Again, this: "... so keen that they wouldn't even think of the flip side," would fall under smaller and unorganized. If they do not take the time to check or plan around other mods because they're too "keen" on getting their mod out, then they still wouldn't have anything to list or add to a dedicated area. "... option to fill in the notes they feel they need to" This is what the Description section is--a large note pad to list the important information related to the mod. And, if they don't feel the need to include that information now why would they then? "It would take modders 2 seconds to complete the section ..." Correct, just as much as it would take them two seconds to add it into the description section if they really wanted/planned to add that info. "I really don't see a downside as it will save everyone time ..." The downside would be pulling VS developers away from working on the game and its mechanics to implement something that mod developers can already easily do within an already provided area and easily draw attention to it with text formatting. As an employee for a game developer myself, our company often tells us to dismiss small things similar to this because users can already do the things mentioned easy enough and our development team's time is better spent elsewhere. It also now adds new sections a user has to check, not just the description. Specially since some modders would choose to continue to just list it in their descriptions as @Renrogn pointed out, "... depends on the mod developer. But let's be honest: each of them does it their own way." Therefore if there's only one way to do it, it wouldn't add to the confusion of where to look per-mod. "... don’t even think about uploading a mod icon." Then what would make one think that they've taken the time for researching or listing compatibilities or incompatibilities either? Going deeper, then, being young developers, they may not even know how to test for or track compats and incompats yet, so, again, the sections purposed would be more for organized and established mod makers who would be more likely to use those items. But it doesn't change that they aren't entirely necessary. As you say the game does already have a built in mechanism to help download missing required mods. And, frankly, this--providing you a large list and downloading them all at once to the mods folder--would already be faster than scrolling through a list on a mod page and visiting each independent mod's page on-by-one to download and then having to slide them to the mods folder. This already happens by using links in a description as it stands, so it doesn't adjust much. "But let's be honest: each of them does it their own way." Quite right. Therefore, there is no guarantee that all. or even most. mod developers would use it. So, you've essentially now added two or more spaces a user would have to go through to make sure they have successfully found all the information listed for requirements, incompatibilities and compatibilities. By this you're increasing the frustrations of users because they now spend more time on each mod page determining whether the Mod creator has listed them in the description or a number of separate areas. Whereas, they could start the game and automatically get the required ones they're missing or read the mod description for incompats and compats. I still pose the question; if the mod developers do not take the time to list dependencies and incompatibilities now, what makes them more likely to do so just because there's an input section for them? And, is it worth frustrating the user installing them by giving them both a description to have to check as well as multiple other spots on the page every time for every mod? It sounds more hassle inducing, in my opinion as a user, anyway. ----- So I still stand by my convictions: those who don't add these things to their mod descriptions now aren't much more likely to add them into a different section either. Those who don't read everything about the mod now aren't likely to start [regardless of which section it's in]. And I'll also now add: if they're a new or inexperienced mod maker they aren't necessarily going to have this info to add in anyway except for dependencies. I just personally do not see any grand necessity for such a feature, nor the need to pull VS resources away from the actual game development for something that can already easily be done and added to a mods page as-is.

Personally, on many mod sites I go to for different games, it's usually up to the Mod developer to maintain a list of Dependencies and Incompatibilities within the mods description section. And on here I have noticed that is usually the same case; the bigger, more popular, or more organized mods and mod makers tend to include these in their descriptions already. Same for @Phantom72's idea, mod makers will generally warn you of those kinds of complications if they're known. So, by and large, this already happens so long as you read the description (and I don't know who wouldn't anyway to be absolutely sure of what they're getting and adding to their game.) Adding these field spaces is minorly more visually apparent, but it would still fully depend on the mod maker to fill in these fields and the player to read everything on the page. Those who don't add these things to their mod descriptions now aren't much more likely to add them into a different section either. Those who don't read everything about the mod now aren't likely to start.

There's already a kind of way to do this I think. You throw the crock/bowl into a body of water. Wait a few seconds or so, and the rot floats out. If it's a sealed crock, you must first unseal it by using a bowl to take out a portion of the rot before it can be cleaned this way. I think the rot is lost when doing this too. Someone correct me if I'm wrong though! You can also just scoop the rot out of crocks with a bowl and then dump the bowl of rot into a barrel to start a composting. Ctrl + Right-Click might also dump the bowl of rot like a bowl of water does. I don't believe there is a way to clean residue covered pots though, but its easy enough to just dedicate the residue pot to crafts and stuff, and make a new pot for cooking in exclusively.

It would be nice if support beams could also provide vertical support for things like dirt when soil instability is turned on. Being that it is a form of instability after all. The video attached below shows a wall blocked in with support beams. These beams fail to hold even the blocks that are right up against the wood. Configurations/Builds wouldn't necessarily have to look like the one in the video. It could be one beam per wall column, multiple beams stacked horizontally, etc, etc. (example photos below.) Technically, this can be done by placing one beam per block space, one at a time. This is because their hit-boxes register as blocking the blocks' falling paths, but you only get one hit-box per beam placed. This is tedious and slow, and even limits making certain designs with the beams (example photo below.) So, it would be nice for the walls to recognize the full length of a singly placed long beam (like stone ceilings do). Then, we wouldn't need all those hit-boxes, loss of creative freedom, or the increased time consumption. Support Beams Issue.mp4 Other Designs Examples: Stacked Beams Ground "embedded" beams, centered per block column. Block-by-Block Curving Issues, 3x10 blocks example: The beam going from bottom-left to top-right was placed as a single beam. The beams running from bottom-right to top-left were placed block-by-block. This led to crooking and curving in a number of spaces due to the increased number of used anchor points.