Baz Foobar

Does this still happen after today's patch? I believe this was related to the time stopping bug which was fixed today.

It definitely had benefits, but not without disadvantages - it not only broke the clock, but it prevented timely healing as well.

Thanks Ane! We've been avoiding sleep because of this, we've been walking around like zombies due to sleep deprivation

Delete or move your current save file. Edit the dsconfig.json file and set the SessionDataType value to BuiltIn, and the SessionData value to Explore. Launch the server. It should create a new save file in the current working directory with a name of SessionSave.ylandsgame - you're good to go. Optionally, change the SessionDataType back to YlandFile and the SessionData back to SessionSave.ylandsgame. This way it doesn't generate a new map if you move that save file out of that directory, or keep it set to BuiltIn/Explore - as long as the save file is there, it won't create a new one.

I've been moving corpses to a graveyard close to spawn just to keep the landscape clean and to give the players a chance to come back in without losing their barrier/map/keys if they choose to do so within a set number of days. If they don't come back after that, I delete them. If this process could somehow be automated or at least triggered in-game instead of in-editor, that would be a decent compromise.

I've read 15 but I've never seen more than 12.

Only thing I can think of is that they wanted to add additional risk to logging out in an exposed area. You may be attacked by the animals or other players if you don't log out within a protected structure.

I understand the desire to have the barrier become a respawn point (we've experimented with it actually, and with the right logic in place you can do this in a non-explore map). I think, however, that risk management is a part of the explorer game and would be diminished by the safety of having a quick respawn to your base. As it stands now, respawn is done to the closest island's respawn point but there are some exceptions - I've noticed that you sometimes end up on the respawn for the server itself. I think this happens when you aren't associated to any island (like falling through the world), or perhaps if the island you're on is not hospitable and has no resources (polar desert perhaps). I think that's a reasonable setup assuming no bugs and you respawn randomly to an island halfway across the world. You can still mitigate risk by bringing some backup gear with you, locking it up on a ship, and knowing how to get to it in the event of death on that island. That said, if we could have some way of teleporting to a barrier/base but at a cost (maybe gold coins or can only be done once a day or something), I'd be open to exploring that further.

Terrain manipulation within a barrier was fixed. That doesn't mean your griefer didn't find an exploitable way to get through the barrier, but this specific problem was addressed. If anyone has any new exploits to report, I recommend they create appropriate bug reports so the team can handle them.

Thanks Berzeger! Is it definitely caused by sleeping or are there any other events that trigger it?

Ane, How long do you usually keep the official servers running? I restart mine at least once a day and I've only seen it go down once since 0.8.

Definitely more griefers since the last refresh - likely a combination of people coming back to see if 0.8 improved their experience, students home for spring break, and maybe some new people who purchased the game. In any event, I figure they're doing me (and other server non-griefing server admins) a favor. Prove you're a griefer while you're still on spawn island and give us a chance to ban you early on before we have to deal with you later. Thanks for speeding up the process! Note - I'm not on some power hungry admin trip here, we make it very clear that we are a non-griefing server via the server name, rules published on our Discord welcome channel, and in-game server-wide broadcasts every 5 minutes to remind players. If they still manage to grief others after all of that and I have clear evidence of it (I cut a backup every few minutes so I can see what's going on throughout the day even if I'm not there to witness it), they get banned, no questions asked. I simply don't have the time to deal with these guys trying to justify what they did or make excuses, and with all of the warnings provided up front, I don't see how there could be a viable excuse anyway. There are plenty of no-holds barred servers out there, so it's not like I'm depriving them of the experience. To other non-griefing server admins, if you're interested in sharing ban lists and the rules you use to ban said players, contact me - I've already shared with some of you. No expectation of reciprocating bans, but feel free to use the information that suits you best - maybe you just scan your LAP lists to see if some of my bans are on your server and you keep an eye out. As always, I would recommend performing your own investigations, but if this information is helpful, I'm happy to provide it.

Search for Foobar - you are welcome and encouraged to join our Discord server as well. We use it to communicate since the game lacks a global chat system.

Ane - for the server log, please refer to the file I sent you this morning.

I think it would be fantastic if BI would provide some community support in the methods described above. Maybe we don't need to give out compensation, but certainly some kind of recognition would go a long way. That all said, I think I would draw the line at idea #4 - even though Red called me out personally as an example (Thanks Red, I appreciate it!) I don't think I deserve that kind of recognition. My server is made up of the players who inhabit it - I merely provide the opportunity for their ideas to foster and community to flourish while keeping an eye on tidying things up. I also am not sure I would want a game developer to be singling out servers in that regard, as it could lead to some belief of favoritism or unfair advantage being provided. Instead, I would suggest that we, the Ylands Gaming Community, should take on that responsibility of recognizing the servers that have helped make the community strive the best. That kind of recognition would go a long way and mean a lot more coming from that audience (no offense intended, BI!) In any event, I welcome the notion of enhancing the Ylands Community. Ane has a huge opportunity here, and I think we can all help her out in this regard. After all, the community is ultimately ours.

Sounds like the Philadelphia Experiment...

Server log from last night sent! Anyone else noticing constant log spam similar to this? [IN] [17:27:45.35] Executing sequenced command type=ylands.CmdInterrupt seq=745 [IN] [17:27:45.47] Executing sequenced command type=ylands.CmdUseItem seq=746 [IN] [17:27:45.63] Executing sequenced command type=ylands.CmdInterrupt seq=747 [IN] [17:27:45.73] Executing sequenced command type=ylands.CmdUseItem seq=748 [IN] [17:27:45.91] Executing sequenced command type=ylands.CmdInterrupt seq=749 [IN] [17:27:45.99] Executing sequenced command type=ylands.CmdUseItem seq=750 [IN] [17:27:46.16] Executing sequenced command type=ylands.CmdInterrupt seq=751 [IN] [17:27:46.24] Executing sequenced command type=ylands.CmdUseItem seq=752 [IN] [17:27:46.43] Executing sequenced command type=ylands.CmdInterrupt seq=753 [IN] [17:27:46.49] Executing sequenced command type=ylands.CmdUseItem seq=754

Quick observation - login times are much improved, kudos to the programmer who cleaned that up. Trees are still crazy - sometimes they become unchoppable until you log out and back in. Overall performance seems good, but we started with a new map for 0.8 so we haven't uncovered all of the Ylands yet - will report back once the map is all discovered. One problem that is new though - the entire server (5-6 of us) would get booted every once in a while (it happened at least 3 times within a span of 2 hours) where we'd all get connection time outs and we'd have to log back in again (good job on the queue, we get in real quick without clobbering each other like in previous versions). Not sure if the timeouts were because of the server or what, so I'll give the system a clean recycle tomorrow morning and see how tomorrow plays out. If it continues to get timeouts with server-wide disconnects, I'll provide client and server logs.

You need to take the server offline, bring the savegame into the editor, and drop a Creator Cube near your avatar. Then start the game up with the new savegame, pick up the creator cube and have at it. The creator cube grants you unlimited crafting and invulnerability. Alternatively, just make all your edits to the world and the environment using the editor, but then your server has to be down for that entire duration.

Will players have the ability to bring the save file into their editor, make changes, and push it back out to the cloud save so that the next person who hosts it will get that same version? Also, I presume these worlds are not eligible for the monetization parameters described previously for Official Servers?

Good luck buddy - your input here was always insightful and I enjoyed reading your contributions. It's too bad we didn't get a chance to play in the same world. Ylands has some development left. Hopefully when you return, you'll see a much improved experience. If not, well, hopefully you got your $15 worth of fun

Honestly at this point, fix MP and make sure it works, then release it. You're losing interested players otherwise. MP can be a very frustrating experience for some people, I've seen it firsthand both as a player and as a dedicated server admin. As it stands, I'm keeping my DS down until 0.8 - I look forward to seeing improvements.

Since they've already stated that dedicated servers will be rentable, it would make sense that additional cloud save storage beyond some free amount would be feasible using Coyn currency. I think the notion of free storage sufficient for a save or two with additional demand covered by Coyn to be a reasonable model. Up until the cost of said storage starting to encroach upon the cost of renting a dedicated server, of course.

I know it's not a negotiation, but since the release is ready for tomorrow and the only reason it's going out on Monday is to make sure you have sufficient support resources on hand to deal with issues upon release, how about a changelog for tomorrow (Friday)? Surely that would address the concerns you brought up? Either way, it's your game. We're just hosting and playing it. And as far as 0.9 is concerned, at this point as long as it fixes all of the problems we've been reporting in MP (some of which are seriously game-breaking), I'm all for it.

It happens. As a consolation, any chance you can provide the changelog ahead of time so we know what to look forward to?