Streetwind

That "square that indicates the area" is probably drawn by the mod VsProspectorInfo. It is not a feature of the base game.

This is not possible, but you can achieve the same look by using multi-material chiseling.

Not currently, no.

Yes, temperature currently changes at a rate of 0.667°C per block height difference (says Tyron on Discord), colder at high altitudes, warmer at low ones, independent of total world height.
Note: 1.18 is likely to make changes to this formula, as there is a worldgen revamp coming with it.

This is currently under very active discussion on Discord, and a lot of people have a lot of opinions about this.
On one hand, both .NET 4 and Windows 7 are extremely old. Using Win7 with an internet connection in this day and age is a major security risk for the user, and building software on an outdated framework makes that software slower and less safe. .NET 7 in particular has significant performance optimizations under the hood that would really benefit people using older hardware. Additionally, the Steam user survey, which is a fairly representative global sample of PC gamers, suggests that fewer than 2% of all Steam users are still using Windows versions older than Win10.
On the other hand, reducing the scope of supported platforms without prior announcement is a dick move, even with an essentially unlimited refund policy like Vintage Story has. The team is well aware of this, and Tyron aspirationally wants to continue shipping old framework builds for multiple future releases.
On the third hand, shipping multiple builds in parallel is fraught with issues, both when it comes to developing the base game, and when it comes to mod support. Maintaining support for the old framework costs development time that could be spent on improving the game instead. Modders would have to choose between supporting and debugging two separate versions of each of their mods, or to pick just one and not service the other. This risks a split in the modding community that'll get worse the longer the base game decides to maintain support for the outdated framework and Windows versions.
It has been confirmed that 1.18 will be shipping on both .NET 4 and .NET 7. Anything beyond that, nobody knows for sure.
Meanwhile, good lord, update your OS. Please don't tell me you habitually do online banking on this machine...
 

I'm not sure if there is a proper definition of a "solid block" written down anywhere, but in my own experience it is something like:
A block that is no less than half a block thick at any point; and which has a face that is level with a neighboring full block surface, which is the "solid face".
In other words, a full block automatically qualifies. But a solid block can also be a stair or a slab, or even a chiseled block of equal or greater thickness, if it is oriented correctly. For example, a slab that is attached to the upper side of a neighboring block will have its "solid face" (the one level with a full block face) on the top, whereas a slab attached to the bottom side of a neighboring block will have its "solid face" on the bottom.
To build a charcoal pit, it needs an unbroken surface of solid faces on the inside. You can use slabs for this, as long as all the solid faces are pointing inwards. You can use chiseled blocks for this, as long as they are as thick as slabs or thicker, oriented correctly, and not perforated.
Doors and such are not solid, and therefore automatically invalid in the construction of a charcoal pit.
(I can't remember right now whether transparent blocks count or not. I think so, but might be mixing things up with Minecraft here. Or I might be mixing up the mixup. Who knows!)
 

You are not doing anything wrong You are correct to expect magnetite at this location You are somewhat unlucky and lack experience Not all ores are created alike. Indeed, there is a bit of a scale to them, in terms of difficulty of finding them. The common ores, something like copper and bismuthinite, and to some extend even cassiterite? They're easy to find by just going through the motions with the prospecting pick. Hunt down a nice, high peak value with Density Search, dig vertically down in that place, perhaps take the occasional Node Search sample along the way - and you're virtually guaranteed to hit ore. Every time.
But the more exotic and/or advanced ores, they have quirks. Things to know about each of them that inform the way you search and the way you dig for that particular ore. It partially starts with cassiterite, where knowing to dig in a place with all-igneous stone top to bottom will noticeably increase your chances over places with just an igneous bottom layer. And then comes iron - and it's a completely different beast. All of the iron ores, to some extend, but especially magnetite.
You see, to generate ores, the game rolls a number of tries each chunk. It picks a random block within the ore's spawn range in that chunk, and rolls a die against the spawn chance in that location. If you've got an Ultra High reading, the chance to succeed this roll approaches 100%; if you've got a Miniscule reading, it's almost guaranteed to fail (but only almost). When the roll succeeds, the game tries placing an ore vein centered on that block. Now, this may still fail - perhaps it picked an invalid block that cannot host this ore. Or maybe a cave generated later-on might turn everything in that area, including the ore vein, into air. But if the block is the correct host rock, then it and surrounding host rock blocks are replaced by a disc of ore of a certain size, as defined in the ore's spawn config. Then the game rolls another try, up to the number of tries per chunk as defined in the ore's spawn config. It does this for every chunk.
Up to iron, every ore has multiple tries per chunk. Some of them have two-digit tries per chunk. Iron... doesn't. Iron has fewer than one tries per chunk. Magnetite, in particular, sits at an abysmal 0.3 tries per chunk.
Now, when the game goes to roll for a spawn, it has to make two rolls. First it needs to roll whether or not it is even allowed to roll. And with Magnetite, it has a 70% chance to fail this roll. So your Ultra High chunk, where Magnetite has a near guaranteed chance to make its spawn roll? It failed to even be allowed to try. And that's why there isn't anything there, despite what the prospecting indicates.
The takeaway here is that when searching for iron, and magnetite in particular, it's not enough to examine just that one chunk with the highest reading. You need to examine enough chunks to overcome the ore's chance of failing to be allowed to try to spawn. In return, when you do find an iron vein, it's going to be absolutely ginormous and you're unlikely to need to look for another vein for a long, long time.
Iron discs are over fifty blocks in diameter. This means that, since you didn't find any indication of iron in your current shaft despite eight blocks of Node Search range, it is safe for you to go fifty to sixty blocks away to dig another shaft. Continue picking locations with high readings, and/or make some sort of grid around your Ultra High result. You can try closer than fifty blocks, of course, if you're afraid of missing something; but the smaller you make your search grid, the more shafts you may have to dig until you find a vein.

@Aoi Kasai Temporal stability depends on where you are.
Some areas have naturally high stability. If you spend time there, your stability will increase.
Some areas have naturally low stability. If you spend time there, your stability will decrease.
Building a base in an unstable area is a very common beginner mistake, as new players won't know how it works.
You will likely have to pack up everything you own and move somewhere else, a place where you see the gear in the lower middle of the screen spin clockwise.

Could be that you're running out of VRAM.
Go to the settings menu, and read the tooltips to find settings that mention that they're heavy on VRAM (I think view distance is one?). Try reducing those settings significantly, and see if it makes a difference.
Could also be that your video card is damaged. However, that would mean you should see broken graphics in other games too. If this only happens to you in Vintage Story, then your GPU is most likely fine, and you're just asking too much of it.
Finally, it could be a driver issue. But I would expect that both Nvidia and AMD have very stable drivers these days. If however you're running on an Intel GPU (either CPU-integrated or one of the new Arc series cards), then yeah, driver hickups are going to be a thing.

...Wait, what? o_O What does it matter where the executable is located? You're not supposed to change that, nor is it necessary. All you're supposed to do is tell the executable at startup where it should look for its data folder.
The data folder can be located anywhere you like, completely independent of the game's install directory. You could have it inside the install directory (to keep everything in one place), but you don't have to. It can even be located on network drives or external drives, so long as you ensure these drives are mounted when you try to launch the client.
I know this because I've been playing Vintage Story like that since 1.12, and it has always worked reliably.
There is probably something you misunderstood about how to set this up. Let me try to describe it again:
Create the directory where you want your data folder to be located in the future, and copy its full, absolute path. Paste the path into a text file or something similar for later reference. You don't need to recreate the folder structure inside the data folder, the game will do that on its own. Go to your VS install directory and create a shortcut to vintagestory.exe. The easiest way to do this in Windows is the select the file, so that it is marked blue. Then, using the right mouse button, click and drag the file to an empty space inside the folder (or some other folder, or even the desktop, wherever you want it). Upon releasing the mouse button, a context menu pops up. Select "create shortcut". Rightclick the shortcut, and select "Properties". A small window pops up, with a few editable fields. The topmost one is called "Target". Inside this field, do not delete anything that's already there. Instead, go to the very end, press spacebar once, and then write --dataPath your:\path\here. That's a double dash at the front. You input the absolute path to your desired future data folder that you set aside during the first step. Finally, pay attention to quotation marks inside that target field. If the absolute path to your game's install directory contained spaces, then the contents of the target field in the shortcut will likely have been encased in quotation marks, so that the operating system understands it. By appending something to the very end of that, you'll have broken it, because you'll now have a quotation mark somewhere in the middle, where it doesn't belong. Find that quotation mark, and move it to the very end again, after everything you have typed. If there were no quotation marks, then add them just to be sure. One at the very start before anything else, and one at the very end. This covers the edge case where your path to your desired future data folder may contain spaces or other weirdness. Press OK to close the properties window. Doubleclick the shortcut in order to launch the game. Pay attention to your desired future data folder; the game should auto-populate it with certain required files and subfolders. If this did not work, I'll need you to describe to me step by step what you did, or better yet, show me your shortcut's properties with screenshots. If this worked correctly, you can now move your savegames and clientsettings.json over from the default data folder to the new one.

1.17 increased crop growth times, including berry bushes.
In return, yields were increased. Overall the amount of produce harvested from a crop type across an ingame year should be close to what it was in older versions, but split into larger but less frequent harvests.

Crop growth times were changed in 1.17. I guess nobody got around to updating everything on the wiki yet.
Remember, the wiki is maintained by community volunteers, not the dev team.

Unfortunately, the terrain generator does not support large bodies of water at the current time.
It's on the development roadmap for the future, but there are currently no indications when it might happen. The theme for the next update right now is "storytelling, lore, and ruins".

It's a little bit of column A, a little bit of column B.
By default, the server is set to pause (basically, slowing the global sim speed to more or less standstill) while nobody is online. The moment one player logs in, it resumes. The server can be configured to keep running normally when no one is online, but the default behavior is pausing.
This means that whether or not long processes continue to happen while you're offline will depend on whether anyone at all is online. If you're the last person to log off, causing the server to pause, and then return before anyone else, you'll find things pretty much where you left them. On the other hand, if the server is more or less always populated, you can log off with a freshly seeded field and return to fully grown crops later.

This is not a thing, no. Drifters do not set anything on fire. Not even if the drifter itself is on fire (you can hit them repeatedly with a torch for that).
I'm quite sure that the base was on fire because a pit kiln was too close to something flammable.

The first thing you can try is pressing F11 once the client has launched and the window is in focus. That should switch display modes.
If that doesn't work:
There should be a file called clientsettings.json somewhere (I don't know where it is located on OSX, sorry). There's a "screenWidth" and a "screenHeight" definition in it.

If you're not adverse to installing a mod, Accessibility Tweaks provides a number of additional graphical options that the base game doesn't have.

Make a shortcut of vintagestory.exe Add the "--dataPath InsertFolderPathHere" switch to the shortcut target, according to where you want your new Data directory to go Start the game once via the shortcut to create and populate the new Data directory Migrate your existing savegames to the new directory Only start the game via the shortcut from here on out (If you want to install the game itself somewhere else, you can choose the location when running the installer.)

If you're in a 1x1x1 hole, then jumping will get you out. Blocks do not have any collision from the inside.
Knockback pushing you into blocks is a known, if very rare, bug in 1.16.x versions of the game. But even when it happens, it will only ever push you into the first block. There's no such thing as "solid blocks on all six sides". You just haven't found the way out yet, likely because you got disoriented by what happened.
Finally, in singleplayer, you can always do /gamemode creative to allow you to break any block with a single click of your bare hand, and then /gamemode survival to return to what you were doing before. Note that this will not break the block you are already inside of. You still need to jump/walk/fly out of that one.

Which version of the game are you running on? That's always one of the most important pieces of info you can include.
Additionally, state if there were mods present, and if so, which ones. Does the error still appear if you remove them before loading into the world? Has there been a specific subset of mods that has always been present whenever you got this error?
Also, did you try loading the world in Repair Mode? (It's a box you can check inside the saved world's details.)

I think the recipe is defined as "any chisel + any anvil", and therefore loops through all those options in the handbook. However, upon actually trying to do it, the game also checks if the chisel has enough durability. Higher tier anvil consume more durability for breaking down, and so a copper chisel may not have enough, even when full. This check must happen at the moment of crafting, since it must catch any possible case, including partially damaged chisels. This cannot be shown in the handbook recipe preview.
Try using a higher tier chisel, and observe exactly how much durability the process consumes. Then compare that value to the maximum durability of the copper chisel.

/worldConfig propickNodeSearchRadius [radius]
Pick a number for the radius. The larger the number, the further away you will be able to pick up ore, but the more difficult it becomes to triangulate. Numbers around 6-8 are recommended. Do not include the square brackets.
After entering, quit to main menu and then reload the world.

You need to use the big cogwheel to split power, yes. Unfortunately that also acts as a big accelerator gear, so you're going to lose a lot of torque. The counter to that is using a second big cogwheel as a reduction gear further up.
Connect your windmill rotor with an angle gear to the rim (not the shaft) of a large gear. That is your reduction gear. Now bring the shaft down into your workshop, and connect your consumers with angle gears to the rim (not the shaft) of a second large gear. That is your accelerator. The two will cancel each other out, and the system will act as if you had zero large gears, but you are still splitting power.
 
Not without installing a mod, no. That said, your forge gives off plenty of heat. You'll have to live with the +25% winter food usage penalty, but you're not going to freeze.

Welcome to the forums
Placement of blocks can be context-sensitive. For example, it can depend on the direction you are currently standing/looking, or on which side of another block you try to attach something. With logs, for example, try placing them on the side of another block, not the top, if you want a horizontal placement.
As for lower-half slabs, no, you cannot place objects directly on them without a gap. The game works in a block grid, and every object occupies a block space. You cannot have an object sit halfway between two block spaces, and especially not have it invade the space that another object is already occupying. Even if the lower-half slab looks like it is only the size of half a block, it is still an object, and it still occupies its block space completely. You can verify this by trying to place a second slab on top of the first one. They should both fit in the same space, but they do not. Each is an object, and each wants its own exclusive block space.
Now, there are potential solutions to this limitation that could be implemented. Minecraft for instance allows you to place two slabs into the same block space by way of secretly deleting the first slab and replacing it by a full block that looks like it is made out of two slabs. That way it can maintain the "one block space, one object" rule. But right now, Vintage Story does not implement such a thing. Maybe it might at some point in the future? Who knows. For now, the game is still a long way from finished, and with only one person working on code, new features take priority.

When you use the public listing, you will be trying to connect to your public internet IP. This IP is only reachable from the internet. You, however, are not coming from the internet. You're on the same local machine as the server is. For this reason, using the public listing may fail.
Instead, try the "Add New Server" button to create a custom entry. For the IP address, enter 127.0.0.1 followed by a colon followed by your server's port. This is is your "loopback address" - that is, a unique IP address that points to yourself. Every computer has it. The word "localhost" can often be used as a stand-in.