In our country we had exceptions for certain breathing sicknesses, certain aged old people (worse breathing capabilities), children under 3, for it was unnecessary, autists and mentally challenged people for they would be under stress.
@Dalph I've been with the community for 3 years. Started on MV 1.4.4. In 1.5.0 we got better plugin manager. In 1.6.0 we finally got better nwjs.
I was one of the 7 people who provided feedback on MV 1.6.0 open beta. Their support of that was good - so good that they did not even fix any of the...
Yeah, at this point it's too late I guess.
At this point. ES6 and better optimization have been requested for years. And if we want a better optimized engine, apparently we have to buy it.
I can't support this practice. Not with the price of MV.
@ImaginaryVillain If I only rewrite engine from ES5 to ES6, I'm breaking next to nothing. The prototype thing vs. class thing is from 90% syntactic sugar. The only real difference is in static variables and functions. There was even a poll on what version people use, with vast majority being at 1.6.
I agree that different code base needs to be shipped under new engine. But in regards to features, so far the only features that would justify new engine are effekseer, new map layer, PIXIv5 and native ATB. Many of the features that got presented so far should have been part of MV someday imo.
This update does contain some amazing features...
But at the same time leaves me feeling gutted.
So many of those features could've been brought to MV. Perhaps not all of them, I would understand why MV sticks to PIXIv4 instead of PIXIv5. But ES6 was a necessity. If not ES6, then at least...
I can understand no update to PIXIv5 due to breaking a couple of things.
But not updating MV to ES6 or preloading? Unacceptable.
The quality of life features of MZ aren't too difficult to implement either. Why not put them into MV then?
Greed is literally the only thing I can think of.
Anyone here managed to never burn out on programming? My current limit is 3 months(6-8 hours per day, 7 days per week, 50 hour programming week on average), and then I just have to take a break, sometimes lasting few days(with at most 2 hours on programming per day). I've been always like this so far, so I admire those who can always be so passionate on programming
Automatic level scaling without an option to turn it off can be a very bad choice for a game. The worst I've ever seen was in Nightmare of Druaga, where if a power outage made your system turn off, the game detects it as an attempted cheat and overwrites your save while taking away your best gear, leaving you unable to progress at the late stages of the game, and unable to recover.