About The Crow's Nest Ylands Server

Be slow to anger and remiss to judge, that's the way to prevent a grudge.

the-crows-nest-18.jpg

Crow's Nest HomeAboutRules
Ylands.com Crow's Nest threadcontactTCN Discord
🖬 TCN1 ArchiveTCN2 Sneak Peak
Bans and ban appeals

► Ylands Server Details For The Crow's Nest (TCN)

The Crow's Nest is a public Ylands dedicated server (DS) hosted in Los Angeles California. TCN began as a private test server for providing feedback and went public on Sunday Jan 15th. I'm attentive to the server and do all that I can to keep lag and issues to a minimum, but this is still early access so you can definitely expect bugs and performance/optimization issues.

TCN is not a default Explore world, it is a custom map generated through the editor. TCN1 (the current map) consists of two islands that are side by side, and much larger than the standard Explore islands. Most of the active players have grouped together near spawn. Since this is a generated world using the editor, the protective barriers (PB or "orb") are not included, this is due to the fact that the PB's are not available in the editor. I'm hopeful that the PB will eventually become available in the editor, but there are benefits to using a custom map that outweigh the orb, and the orb is not currently protecting as well as it could anyway. Here are a few key features of TCN:

► Features
  • Keep items on death. When you die, be sure to choose the "respawn" option. Your personal inventory is the most secure container you have. Craft the additional inventory containers as soon as you can to get the most out of this feature and to expand your inventory capacity.
  • Welcome kit included in your inventory when you start. This includes clay, iron ore, and a seedbox packed with seeds. There's no need to worry about someone depleting the island of key materials, and no one can take your items through PvP.
  • Automated daily restarts at 4:15am and 4:15pm to help keep the lag beast away.
  • Automated backups every 4 hours.
  • Corpse removal every few(ish) 2 days. Note: Server down time during removal.

► Rules
  1. PvP is permitted except for OPC (offline player character) killing and AFK killing. If you go AFK, it's a good idea to sit down (F4) as this is generally intended to identify an AFK or offline player.
  2. Don't destroy/place blocks on bases that don't belong to you without permission. (Exceptions: gifts, team builds, and open community builds).
  3. Don't grief the terrain, especially at or near player builds, spawn, or the shoreline. It's okay to alter the terrain to work on a build project, or to mine, etc…
  4. No exploits, cheats, or hacks. I realize their are some soft exploits like infinite iron and AFK fishing, these are okay, but I'm primarily against exploits that disrupt other players or the server. If you're not sure whether or not something is allowable, just ask an admin.
  5. Keep things civil. No hateful or racial slurs, or personal insults.
  6. When in doubt, treat others as you would have them treat you.
► Server Wipes:

Unscheduled server wipes will only occur if and when extreme performance related circumstances require it. Whenever their is a scheduled or unscheduled server wipe, a copy of the DS save file will be made available for anyone that wants to keep a copy of their work or copy their builds as a composition, request copy here. The first scheduled server wipe is planned for the release of Ylands 0.7.

► Roll Backs

Any roll backs (due to correcting various issues) are usually only a few minutes back. In a worse case scenario, a roll back could be as far back as 4 hours (unless the issue was older and we didn't catch it sooner). Though automatic backups happen every 4 hours, I also I perform backups before performing any maintenance or testing server content.

► Known Issues

There is intermittent character freezing in which you cannot move your character for several seconds. This seems to happen when someone logs in, or has a failed login attempt. This was supposed to be fixed for the 0.63 release and at first it seemed fixed but for whatever reason, it is back.