I'm lacking access to efficient developer communication, which makes it challenging to be a useful and effective beta tester.

I experienced a client crash which generated a log file.
The error handler requested that I submit the log file to https://www.cyberstep.com/help/mailform/game, which is simply a contact form.

There's an option to attach a screenshot (image file), but it will not allow the submission of other file types. I have no way to submit the log file except to paste its contents into the Details box.
However, I can't submit the form because it exceeds the 5000 character limit.

By what means am I supposed to report pertinent technical data and crash-related information to the developers?

Tenmiles wrote:I'm lacking access to efficient developer communication, which makes it challenging to be a useful and effective beta tester.

I experienced a client crash which generated a log file.
The error handler requested that I submit the log file to https://www.cyberstep.com/help/mailform/game, which is simply a contact form.

There's an option to attach a screenshot (image file), but it will not allow the submission of other file types. I have no way to submit the log file except to paste its contents into the Details box.
However, I can't submit the form because it exceeds the 5000 character limit.

By what means am I supposed to report pertinent technical data and crash-related information to the developers?

Try putting it on a text hosting site, such as pastebin? I agree it's not very conducive to debugging/QA, but if you're keen on submitting crash reports there are ways around it.

Fair enough, but it's a moot point now, as far as I'm concerned.
I try to be a good beta tester when invited, and to contribute meaningfully to the project, rather than just being a self-interested, early-adopting player.
However, if they weren't really interested in tester feedback, and the CBT was merely a server stress test, then I'm not going to go to undue trouble to submit feedback that they don't care about.
My bigger concern was about the inconsistency of the instructions.
The error handler directed me to submit the crash log, but CS doesn't seem to be organized correctly to handle or even allow for the following of those directions, and this doesn't bode well for the long-term management of the game.
It seems likely that Onigiri may follow the tradition of games with minimal support where dedicated players learn to just grit their teeth and roll with whatever happens and accept it as "part of the experience", while quietly accepting the fact that it's never going to get better.

I think it was more of a stress test. This is, after all, translated from the JP version, which has been live for over a year.

You can use pastebin as thousand log characters or upload to filehosting service to send specific files of logs error then paste your links into them.