- Mar 9, 2023
- 233
- 62
In the Kagura Games version? Errors and crashes are quite common.Does it happen to someone else that in a cinematic a screen appears that puts an image error and the game stays like this?
In the Kagura Games version? Errors and crashes are quite common.Does it happen to someone else that in a cinematic a screen appears that puts an image error and the game stays like this?
You're buying a game, you're spending money, and in return you receive a game that you can't play and they haven't fixed it for 5 days. I think it's normal for people to be a bit angry. Kagura is selling the game and making profits so the company is responsible for any bugs that their locations may cause.I really don't like how you guys are putting all of the blame on Kagura Games for the errors, yes they *should* have done better testing, but it's not entirely their fault. RPG Maker has no error checking *at all* so it's difficult to check every possible error state, this is a massive failing on the part of the tool, not just the localization team.
Seriously you try checking *thousands* of events with hundreds of lines of event commands spread across several pages each. It's easy to miss and hard to check for manually.
What you said doesn't address the underlying issue, I'm *not* saying Kagura Games is innocent, I'm saying the tooling sucks.You're buying a game, you're spending money, and in return you receive a game that you can't play and they haven't fixed it for 5 days. I think it's normal for people to be a bit angry. Kagura is selling the game and making profits so the company is responsible for any bugs that their locations may cause.
Besides, we are not talking about small translation errors or small errors that do not affect the gaming experience, this time it is literally that you cannot play and the solution is to save the game often because the game breaks.
If they had played for 30 minutes they would have discovered that there would be problems. They didn't need a long game session or to do crazy things to find bugs because bugs find you this time.
that same mistake has already happened to me in several Missions, I think the game is worse than the old MTL versionIn the Kagura Games version? Errors and crashes are quite common.
It's not the consumer's fault that the game's development tool isn't good and also that the game has bugs. The consumer pays money to receive a product, the rest is irrelevant.What you said doesn't address the underlying issue, I'm *not* saying Kagura Games is innocent, I'm saying the tooling sucks.
EDIT:
5 days to fix an issue? You do realize that 5 days ago was the *weekend*, debugging RPG Maker issues is a gigantic pain and will take more than a few days to iron out all of the issues, what you're doing is being entitled to immediate fixes, which no, you aren't. If they don't have a fix out in a couple of weeks, then *yes* that's a problem, however expecting a patch within 5 days, 2 of which were the *weekend* is a little petty.
Incorrect, it's very relevant, I get that the consumer is affected by the game having errors and crashes, however you trivializing how development works as "irrelevant" is ignoring the root cause of the problem, If the RPG Maker tooling was better errors like this would be non-existent. Also I've seen occasions where RPG Maker straight up doesn't properly copy files when deploying the game for distribution, is that the fault of the developer or the tool?It's not the consumer's fault that the game's development tool isn't good and also that the game has bugs. The consumer pays money to receive a product, the rest is irrelevant.
It's definitively worse. They caused major memory leaks which is why any scene (and the status screen) that uses live2d can randomly crash.that same mistake has already happened to me in several Missions, I think the game is worse than the old MTL version
This game doesn't use live2d it uses Animated PNGs (apng)It's definitively worse. They caused major memory leaks which is why any scene (and the status screen) that uses live2d can randomly crash.
I will just that the said crashing errors only existed in the original day 1 japanese release.Incorrect, it's very relevant, I get that the consumer is affected by the game having errors and crashes, however you trivializing how development works as "irrelevant" is ignoring the root cause of the problem, If the RPG Maker tooling was better errors like this would be non-existent. Also I've seen occasions where RPG Maker straight up doesn't properly copy files when deploying the game for distribution, is that the fault of the developer or the tool?
You can't just compare file count, you also need to compare filenames. and there are definitely missing files if you cross reference the missing filenames. Also the pictures directory has a grand total of 7 more hardly worth calling it "bloat"I will just that the said crashing errors only existed in the original day 1 japanese release.
The Developer himself fixed those issues long ago, that is why the japanese version is on 1.13 ( same version as the chatgpt tl).
The chat gpt translation had no such issues and KG version which is supposed to be made by a company does?
Now if Kagura Games actually put some effect in testing games, they would have noticed the issue right away.
And how did they manage to readd a issue that the developer fixed ages ago back to the game? thats the real question.
As for missing files in the KG version, sorry to say but i compared to the japanese version and the file number is exactly the same (kagura games version actually haz even more files than the japanese version, they sure love to bloat the game folders).
At this point people are better off playing the chatpgpt TL, unless they want to save every 2 minutes due to crashes and prob make the computer blowup due to the memory leaks kg added in.
Also i laugh at the 5 days thing. Kagura works in a very simple form. Only 1 or 2 patches and they move to the next game (theres quite a lot of games that been bugged for 3 years with game crashing errors and see if they cared).You can't just compare file count, you also need to compare filenames. and there are definitely missing files if you cross reference the missing filenames. Also the pictures directory has a grand total of 7 more hardly worth calling it "bloat"
If you want to disregard horrible tooling then you're more than welcome to, but that won't make the actual problem go away.
The memory leaks are actually unrelated to what Kagura did, but related to the ApngPicture and PIXIApngAndGif plugins that the original developer used, the leaks always existed, but you either didn't notice, or only started caring now.
People don't give a shit about development, if bugs are hard to fix, or any other excuse. I can keep answering you with the same phrase: The consumer pays money to receive a product, the rest is irrelevant. As long as the consumer is happy with what he has bought, everything is fine. Kagura sells and you buy, if there is any problem you can get a refund.Incorrect, it's very relevant, I get that the consumer is affected by the game having errors and crashes, however you trivializing how development works as "irrelevant" is ignoring the root cause of the problem, If the RPG Maker tooling was better errors like this would be non-existent. Also I've seen occasions where RPG Maker straight up doesn't properly copy files when deploying the game for distribution, is that the fault of the developer or the tool?
Also i laugh at the 5 days thing. Kagura works in a very simple form. Only 1 or 2 patches and they move to the next game (theres quite a lot of games that been bugged for 3 years with game crashing errors and see if they cared).
If a game sells well enough then they will think about doing more fixes, if not then forget it.
They trive on the idiots who blindly buy their games on release who hope the games get fixes. By the time the buyers realize that they wont, kg already haz their money and good luck getting refunds.
And yet they still defend KG.
And sorry to say but i played the japanese version , the chatgpt mtl AND the KG version.
never had "memory leaks" nor the crashes people have when acessign h scenes or the menu in the first 2 Like this :
https://thef95zone.info/threads/sayakas-addiction-v1-01-steam-kedama-qube.191879/post-16479663 (funny how that crash only existed in the earlier japanese versions of the game) and kg managed to bring it back.
Also, please do illuminate me on what files are missing., Because i just compared both versions file name wise, and they look exactly the same , other than the extra "bloat".
Unless youre one of those who doesnt know how to patch a game then comes here complaining that theres "cut content" , like the guy on the previous page
You yourself said as well, if im not mistaken that those crashes only existed in the release of the jp game.People don't give a shit about development, if bugs are hard to fix, or any other excuse. I can keep answering you with the same phrase: The consumer pays money to receive a product, the rest is irrelevant. As long as the consumer is happy with what he has bought, everything is fine. Kagura sells and you buy, if there is any problem you can get a refund.
Ok, then get a refund, complaining about it on an unrelated forum is a) petty, and b) not helpful. It also doesn't address the point I brought up.People don't give a shit about development, if bugs are hard to fix, or any other excuse. I can keep answering you with the same phrase: The consumer pays money to receive a product, the rest is irrelevant. As long as the consumer is happy with what he has bought, everything is fine. Kagura sells and you buy, if there is any problem you can get a refund.
Indeed, I am comparing the japanese version which i actually own with the KG version.And thus i asked you for these "missing files", because its more likely to be renamed files rather than "missing". Like i said people claiming about missing files and cut content do show up:I absolutely know how to modify any just about any game I get my hands on, but the ones I'm comparing are 100% unmodified. When I say missing files I'm going by the filenames that show up in the error messages (which, btw, aren't crashes)
I can only answer you with this after reading your nonsense.Ok, then get a refund, complaining about it on an unrelated forum is a) petty, and b) not helpful. It also doesn't address the point I brought up.
Does KG need to improve things? Absolutely, I'm not denying that, I never once said KG was blameless, they absolutely have blame on their side of things. But it's not the whole story which was what I was saying.
EDIT:
RPG Maker's engine itself is pretty darn robust and decently well designed. Their editor absolutely sucks and leads to problems like this being trivial to run into.
I didn't want to bring it up because I didn't want people to take this as me crapping on RPG Maker to promote my own project, but these *exact* issues are why I've been working on my own replacement editor for RPG Maker MV/MZ, I'm not going to post details here because it's not relevant, but the the *reason* I started it is. The tooling is just awful and hamstrings the engine itself.
I'm not saying that KG wouldn't have had any issues if the tooling was better, but the issues would have been much fewer and more related to logic rather than missing/misnamed files.
You're more than welcome to think of what I posted as nonsense, but at least what I'm saying is on factual grounds.I can only answer you with this after reading your nonsense.![]()
"facts"You're more than welcome to think of what I posted as nonsense, but at least what I'm saying is on factual grounds.