Aeris

It actually takes a pretty long time to bash them, especially if people have built them from high-QL materials. If they were easy to remove people would remove them once they're done with them, and they don't. I don't want to rob people of the ability to build a safe zone for a rift: I want them to be able to build one that doesn't inconvenience everyone hunting in the area for 3 years to come.

Crossing servers in a boat tends to generate nonsense messages even though it’s a normal crossing. It’s confusing, and the first few times it happened I tried to moor the boat to prevent whatever disaster I started anticipating at the border. What Happened? I keep getting error messages indicating that I have not plotted a course when I'm nearing a border, even though I have. Crossing server borders in a boat often throws one of the following error messages: "You feel a disturbance in the currents. You are approaching the edge of these lands and should turn back immediately." "You see dark shadows moving beneath the waves. There is nothing in this direction" Here is an example of what the Event messages looked like during my latest server crossing: "You plot a course to Release. If you keep going in this direction you will end up on Release. If you keep going in this direction you will end up on Release. If you keep going in this direction you will end up on Release. If you keep going in this direction you will end up on Release. You will soon leave this island, and end up on Release. You will soon leave this island, and end up on Release. You will soon leave this island, and end up on Release. You will soon leave this island, and end up on Release. You will soon leave this island, and end up on Release. You feel a disturbance in the currents. You are approaching the edge of these lands and should turn back immediately. You head out to sea. You drift away on the "Boat Name". You leave the "Boat Name". (this was a voluntary disembark, because I was being visually keelhauled and had to disembark to end up at normal sitting level again)" You stop to regain your bearings. You will be able to move again in 30 seconds. What was meant to happen: The error messages are only meant to be thrown when something is wrong, specifically relating to not having plotted a course. Steps to reproduce It doesn't happen every time, but often enough that crossing servers should trigger it eventually. Additional notes - The course had been plotted on all occasions where the errors were thrown. - As far as I could determine from my logs it's been happening since the end of April. - All the crossings have been normal (with only the usual bugs of the boat ending up facing the wrong way, people being disembarked after crossing, sails being lowered, being visually keelhauled etc.). - It's possible that the server is trying to generate a message for something else, and picks the wrong one? - ”You feel a disturbance in the currents. You are approaching the edge of these lands and should turn back immediately” supposedly means that you're too close to a server border with no destination set. - ”You see dark shadows moving beneath the waves. There is nothing in this direction” supposedly means that you're approaching a border with no destination set.

Thank you so much for the giftbox skins!

It's not a bug, they specifically went in to give the two new necklaces their own placed models. The gold, silver, electrum, maple leaf, translucent, aquamarine, ruby, anchor and marbled necklaces all share the gold necklace model. The jade winged hound medallion and necklace of focus are question mark bags.

The Shop was down for 8h 29 minutes, but it seems to be up now?

This is just a wild stab in the dark, but is it possible that the lightning strike forcefully put your character into the old affinity system? When cooking affinities were launched they underwent several changes, one of which was that the profile settings got an option to "fix cooking affinities". The old system didn't contain all the available affinities, and so a one-time toggle was added to amend it. New characters don't spawn with the old system toggled anymore, but the lightning strikes pre-date the change. I'm thinking that maybe the lightning strike adds skill to your character, and then checks a bunch of status boxes for your character - like the cooking affinities. It's a long shot, but if nothing else makes sense it could explain it.

I'm neither bashing anything nor am I being dishonest. This type of dismissive attitude towards criticism is unbefitting. You made some good strides towards acknowledgment in your post, so it's a shame you felt you had to end it with slapping me over the fingers.

Maybe fix the portals and everything else that is still messed up from The Update before you introduce more untested stuff. And no, players shouldn't have to test it on the live servers: The game's not in beta anymore and hasn't been since 2012. Oh and at least one of my friends still doesn't have their friend list, and another is still forcibly male on every character they migrated from NFI. The weight of getting things like that mended shouldn't be put on the players: You shouldn't have to beg on a case-to-case basis to get stuff like that "fixed". They shouldn't be bugged up in the first place, but hey. Think I'm being negative? Someone has to be, because this isn't cute anymore. Every single item that was introduced during the Halloween event was buggy in some way - or missing. Those were for the most part cosmetic additions, so it's easy to brush it off as "just a small thang". I actually really liked the Halloween event, and I thought it was nice that you'd arranged something for us to engage with that was spooky. Personally I find that Halloween textures are more than enough, but I know that events always go down really well so that was thoughtful. But it's the principle of it: Every Single addition was buggy in some way. It's not that I don't appreciate it when actual effort is put into features, I just find it extremely hard to be excited about new features when I know they'll be put on the live servers in a buggy state with no acknowledgement that that's a practice you're working towards moving away from. I would like to hear some sort of nod to the fact that you learned something from the June update, because the Halloween event and all its untested additions was not it. You basically broke the entire game back in June, and are trying to move past it by pushing new feature previews and dangling goblins in front of people.

Please - The rift colossi very clearly show that you can make temporary structures. With the upcoming goblin camps the already bad pen situation is going to get completely out of hand. The servers are already littlered with one-time use pens from rifts and holy sites. It takes hours to get rid of pens that take 5 minutes to build. Lately I've run into issues with being forcefully disembarked from my horse whenever I accidentally brush a corner of a pen, which isn't the best hunting experience.

This portcullis + champion troll team-up offered up a bonus layer of frustration: I kept going in and out of combat too rapidly for me to be able to engage in combat, the fight window just flickered constantly and I didn't even block. But the troll isn't bound by the same restrictions and therefore had no trouble getting hits in. I never entered the portcullis pen, the troll targetted me through it as I was riding past so I stopped to see how it would act.

I noticed, it came back up after circa 1h 22m downtime. No thanks, even this was too much effort for what it was.

You might want to post a warning about this somewhere so people don't try to buy premium in this way, since it's very much still a problem.

Did you forget to bring Release back up after today's restart or did something go horribly wrong? It's currently been down for 1h18m while the other servers were down between 13 and 25 minutes

If your pockets are full and you try to bury a corpse with the "bury all" function it won't let you bury the corpse unless you drop it on the ground. What Happened? When trying to bury a corpse that contains butchered products its contents are compared against your total inventory item count. If you are at capacity (i.e. your inventory already contains 100 items) the following message is produced even if you choose the "bury all" option: "The inventory is full so you need to bury the corpse from the ground." What was meant to happen: Logically that it doesn't compare the item count against the inventory's item count, since the butchered items are moot. Steps to reproduce Try to bury a corpse containing butchered products while the inventory is at an item count of 100.

Oh, sorry, didn't mean to make it sound like I was telling you about the bug. I tagged on to your thread in the hopes that the severity of the problem would be noticed so it stops happening so often (preferrably not at all), because it's not fun to be stuck in the water.