Charuru wrote:You're accentuating the obvious, easy to blame, issue and dismissing the less obvious ones as mitigatable.
No, I'm picking up on the one part which is most likely, statistically speaking, to fail. And I strongly suspect you're over-emphasising the problems of selling your own stuff on your own, although I've not yet tried to sell a VN, myself; I'd be quite interested to hear whether people like Sake-Bento who have recently started to sell stuff have found it as difficult and problematic as you suggest.
Anyway, I'll phrase the question in a different way: why should we trust NovelStream's payment system even as much as we trust BMT Micro, an established service with an established reputation, to pick an example?
It's all very well saying that we know who to call if something goes wrong, but if the thing that's gone wrong is that your startup has gone the way of most other startups and gone out of business for one reason or another, that makes it worse; even leaving aside the engine itself, using a platform like NovelStream
as opposed to dealing with two or three other companies for the separate parts of selling a VN is putting all your eggs in one basket.
You can make it a more attractive prospect just by continuing to exist, of course, and there's nothing inherently wrong with selling a service which has some risk attached. Already you have an offering which is leaps and bounds ahead of anything else I've seen in the field of web-delivered VNs, so if it's a market that's sustainable there's no particular reason right now to think you won't get there and sustain it in the end - all I took issue with was the tone of your dismissal earlier, basically claiming it was "unfair" to even bring these issues up.
Charuru wrote:
1. NovelStream is a decently complex setup, it's not something that people can install easily, if at all.
From a technical point of view, this also makes me worry a bit - in the case of disaster, how quickly are you going to be able to be back on your feet? If the services
you rely on disappear overnight for whatever reason (datacentres catch fire all the time, at least in the minds of risk assessors) how long will it take you to marshal your backups and organise a replacement and re-deploy your code? I'm sure the "if at all" is an exaggeration since you have a working installation yourself, but talking about how difficult it is to set up gives the impression it might be a longer rather than a shorter time... obviously this isn't so important for a VN site as it would be for a bank or something, but if you're asking indie developers with low enough cashflow already to place their trust in you, they may disagree!
(I understand not wanting to licence and distribute the source for the site itself, of course... and if it's just rhetoric to explain not wanting to support the various bizarre issues that might crop up in 5% of cases on other users' hardware, then fine.)
It's good to see a script reference - I'll have a look through it later and have another go with the editor...
As to the text log, though - since it's possible in some browsers (and in some users' cases, desirable) to disable the ability of scripts to replace/modify the right-click menu, and on some platforms (Mac!) there's no obvious right-click for a lot of existing users - my laptop only has one big mouse button, for example - could you not provide an alternate way to get to it? Maybe something on the big black bar at the bottom or something, if nothing else? I know how to perform a right-click with my Mac, and a lot of people plug in a third-party mouse, but there'll still be a significant portion of users who don't realise it's possible, believe it or not.
Charuru wrote:
On Crescendo, yes the source script we had access to is pretty old. JAST was not able to figure out how to open up the current retail version. If you could help, be great. Thanks.
Did you try
this tool, which claims to extract files from archives from Crescendo (and other titles)?