Mordgier

There are no camps on this. There is no agreeing to disagree nor can you call red green and say it's your opinion. You can literally prove it yourself with a single search that will show visible difference. Finally it has nothing to do with DU so it does not belong in a FAQ about the game. If it is opinion, why is it in the FAQ anyway?

It does not really matter how bad or good you think the ED events were as they were still without a doubt better than the DU event.

Dude digging into voxelmancy made me hate everything about it. The tools we have to work with feel like playing a game that has intentionally clunky controls like surgeon simulator, I am Bread or octodad. Voxelmancy as it stands is torture to me. There is nothing that feels fun about it. It infuriating and unpredictable and much of it basically comes down to hours of trial and error till you are able to get the shape that you want. There is no sane way to defend the current state of the voxel tools. It's not even fair to say that they are unfinished - they are not even tools. Making good looking ships in DU is about as frustrating as doing needlework while wearing oven mitts.

I agree with everything you said except this isn't true at least in the US. You are in fact by default responsible for the death of someone while committing a crime. In the US this is called Felony Murder https://criminal.findlaw.com/criminal-charges/felony-murder.html So while I am absolutely on the side that permaban is overkill, they are still responsible for the damage to the marker orders regardless of the intent.

I don't think DU needs to worry about competing for attention with GTA.

December - NQ isn't going to release a content patch that competes for attention with Cyberpunk....

If they fix this I'll forget all about Scoopy....

Kids today - cute cute. Your posts are vastly less mature than that of the "kids" you are accusing of having some failure to grasp the real world.

lol forums broken

Very good. > How is NQ making changes to a market's RDMS any different then them making changes to yours? It's not. But if NQ changes my RDMS to be public and someone else loots my stuff, who is to blame? Even if it's part of their job, they made a mistake doing that job. They are to blame. If I make a mistake doing my job, I don't blame the clients....

Why are you moving the goal posts? User error isn't a bug.

Mistakes in code are not the same thing as user error. Failing to correctly set permissions isn't a bug. It's user error.

What? Why? The two are not the same. When I run the wrong linux command and accidently grant users perms they shouldn't have at work, I don't get to claim "bug"!

Correct. There are bugs, as in code issues, and then there are user errors, when a user fails to use the software correctly. It is not relevant if the user is a player or admin or dev. Their failure to correctly use the software does not indicate that there is a bug in the software. You can argue that the software failed to have sufficient guardrails, but you can't call it a bug.

You're making it sound like the devs only had two options. Permaban - Or - Do Nothing. That's hardly the case. There are thousands of things they could have done instead of a perm ban.

I'm not on NQ's side here - but stuff like this is hilariously over the top and not helping - threats of lawsuits and accusations of fraud are not going to help anyone.

Don't be absurd. It creates massive issues even if you normally work from home. You know simple things like the fact that you may now have to WFH and also watch your kids all day long.

You're still in your honeymoon period. When you have literally spent an entire week of your playtime doing nothing but mining every minute of your playtime, you'll change your tune.

They could also be saying the legate opened up the construct RDMS, either intentionally or by accident. I find it horrific design that the option to share a construct publicly is even a right click option in the first place. Also I imagine OP is past caring about "consequences".

You can compare it to RL - it's just if you do that, you have to hold NQ accountable for the negligence in failing to secure the market place RDMS resulting in millions of losses for the customers of the market. https://www.prattclay.com/blog/2019/march/what-is-negligent-security-and-what-is-needed-to/#:~:text=Examples of Negligent Security&text=Failing to warn visitors about,guards or a security patrol Examples of Negligent Security Business and property owners are required to have reasonable security measures in place that will prevent crimes against those that are on the property. Common examples of negligent security include: Failing to install or monitor security cameras Failing to warn visitors about known risks or dangers Failing to respond to a security alert or emergency call Failing to maintain adequate lighting in dark areas Failing to provide properly-trained security guards or a security patrol Failing to fix broken physical barriers, including locks, gates, fences, or doors Failing to maintain the appearance of an establishment So anyway - so much for the RL examples....

They're legally of age yes, but lets be honest, the mental maturity leaves a lot to be desired. My point remains that once NQ placed a market with open perms, it was just a matter of time before it was smashed. VVVVVVVVVVVVVVVVVVVVVV That really sums it up.

Have you met the average mmo player?

To be fair, nobody in their right mind would have imagined that picking up the terminals would have actually crippled the DB.... It's also fair to say that nobody in the right mind would have thought that picking up the terminals was a good idea. Yes it absolutely shitty that if NQ does try to fix the orders it will be hours of wasted time. I totally agree that what happened is regrettable. Where I do not agree is where the blame goes. NQ just pointed it at the player. Like if it's totally not their fault that the player COULD edit the market in the first place. My stance is that while yes this all hurts us as the community, NQ is largely to blame for this. It was their negligence that allowed for the marketplace to be editable in the first place. Everything that happened after was frankly inevitable.

They've really taken the rapid development model of sprints a bit tooo far eh....

Yeah so like - without the relational model of the DB you have no idea what how many tables you need to touch or what other restrictions are involved that may cause key dupes etc - I don't want to drag this off on to a tanget, but I've been in far far too many situations in RL where a 'simple db change' like the above is in reality incredibly complex to implement.