Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
happened with me but not too sure
Back when I was in computer science class, you'd get F's if your otherwise fully operational program's code wasn't documented right.
F, as in total fail!
Kids these days...
[/melodramatic]
But I'm being honest. My first two working programs got an F when I didn't document it right.
#ScarredForLife
But - if one person started building before the group was formed, or maybe you use a different character on a gold upgrade without remembering to select the group before building, then not all of the structure will be associated with the group. You would have to pick up the parts and put them back down again.
Either make replacements or do that thing where you pick up and place most of the building structure... but not all of it, since we need to know (for Science!) what would actually happen.
...
Now that I think about it, best move valuable items out of susceptible storage areas, just in case (but again, leave some items in as a test).
Building decay works like this:
If there is not a single player of a group on the server for at least exactly seven days (168 hours) all the buildings placed by the group members disappear.
If there hasn't been anybody on the server for at least three and a half days (84 hours), decay ticking will not occur anymore, and will resume ticking from zero when a player joins.
For simplicity, here are some examples:
There are two or more players in a group and they have built stuff on a server. One goes on vacation (literally, no VAC memes) or isn't able to join the server for a prolonged period of time due to various reasons (including the ones you've stated).
If the other player(s) regularly play on the server (taking breaks shorter than 7 days), the buildings won't despawn.
A group of players own a base on a multiplayer server. They all are very busy, but still able to join the server for a limited amount of time. If they make a schedule so each players join the server at regular times, in order to not surpass the 7 day cap (say: player A joins on Thursday, then player B joins 6 days later, on Wednesday, player C joins 6 days afterwards, on Tuesday, so on and so forth), the buildings will not despawn.
You are playing solo on multiplayer and are very busy due to school/work/whatever. If you join the server every once in a while (still taking breaks shorter than 7 days), then your buildings won't despawn.
Nelson pops a new update as he does on every Friday, but the admin is a pisa schitt and won't update the server anytime soon, because he is busy and has a frogging social life! Howdy! If he doesn't do so soon enough that there wouldn't have been no players in more than three and a half days (no player on the server for 84 hours), then no buildings will disappear, no matter how long it takes for the admin to finally update the server and players to join.