Senal

Genuine question, what's the irony here ?

Sure, when you reach a point that you don't have better options to achieve the desired goal (for whatever metric you define as 'better') then killing is on the table by the sounds of it.

All we need now is an agreement on the threshold.

I'm assuming you'll concede that individual killing comes before mass killing, in the hierarchy of options.

So, once this threshold is reached then, according to your logic, you are morally allowed to kill in defence ( and i assume pre-emptive defence, given the "They are won by stopping the enemy‘s ability to act." statement ).

So going back to your original statement, it's entirely possible to kill an individual and still believe in your definition of 'believe in universal human rights.' ?

Provided the correct conditions are met, ofc.

I saw the parts about the declaration of war, i was specifically looking for the part from which you pulled :

Once a war has started, killing is morally acceptable, not before.

Rights need to balanced against each other in practice of course.

So contradiction is possible as i have said and balance would require contextual interpretation, in practice.

Absolute statements such as :

Once a war has started, killing is morally acceptable, not before.

and

You don’t kill people for their ideological beliefs, but to stop their ability to act and remove them from power.

Can be contradictory, depending on context.

I wasn't challenging your interpretation, though i do think it's naive and idealistic to the point of impracticality, i was pointing out that your statements could be considered contradictory.

While I'm at it, i missed a false dichotomy as well :

Wars aren’t won by killing soldiers. They are won by stopping the enemy‘s ability to act.

Those things are not mutually exclusive.

You can find that in international humanitarian law.

That's a large amount of text to sift through, if you could give me a hint to where it specifies moral authority before and after an official declaration of war i'd appreciate it.

Firstly, citation? because as i understand it "killing is morally acceptable in war" isn't in the universal declaration of human rights.

Secondly, even if it was, there is no magic attribute of those declarations that makes them immune to contradiction.

That is a very strange and self-contradicting hill to die on.

I think you meant to reply to the poster above.

I have exactly the same issue though, a full rack switch and nas that i can't easily downsize to 10 inche dimensions.

I could probably just buy/build something that would fit but i can't justify it at all.

Do you mean in the sense that there's not enough competition/variety in the existing types of available tech or that there are types of tech that you can't find at all?

both ?

It's similar in etymology to mum's the word iirc

remained private

Depends on the team.

On paper what you're "supposed" to do is iterate through gameplay mechanisms and scenarios by building up the bare minimum needed to get a feel for it, then once you have something viable you proceed further along the development process.

In reality it really depends heavily on context, sometimes you find a particular scenario works fine standalone but not as a part of the whole, or some needed balancing change elsewhere breaks the fun of something established, late additions can also cause this.

but again that depends heavily on the type of game, rpg's are more sensitive to balancing changes than racing sims for example.

Specifically we'd usually evaluate the tradeoff between how much it doesn't work and how much work it is to "fix" it, sometimes it'd get cut completely, sometimes it'd get scaled back, sometimes we'd re-evaluate the feature/scenario for viability and make a decision after that re-evaluation and sometimes we'd just bite the bullet and work through it.

Over time you get a bit more cautious about committing to things without thinking through the potential consequences, but sometimes it just isn't possible to see the future.

I understand the realities of managing a project like that, at the same time these kinds of things are known upfront to a degree and yet people always seem surprised that the cone of uncertainty on a project like that is huge.

As i said, i have no problem with re-use, i have a problem with saying re-use is "essential" to stopping crunch, like the management of a project like that isn't the core of the problem.

Apologies for the delay, my instance is having problems with communities so i can't reply with that account.

To answer the question, not anymore.

The crunch culture was a big part of me leaving.

Honestly it's not that different in type from non-game dev houses, the difference is in the magnitude.

I understand why these things happen, the reasons just aren't good enough for me.

Poor planning compounds with ridiculous timeframes to create an almost immutable deadline to deliver unrealistic goals.

The problem is, they'll jump right back in to the next project and make exactly the same mistakes. At what point does it stop being mistakes and starts being "just how things are done".

One of the main reasons this works at all is that they take young idealistic programmers who want to work in their dream industry and throw them into a cult of crunch where everyone is doing it so it must be ok or this is the price of having my dream job.

it's certainly not all studios and it seems to have gotten marginally better at the indie to small-medium houses but it's prevalent enough that it's still being talked about.