3 replies
Recensioni di GamePlotter App
Accedi per scrivere una recensione
pixelRonan: the statistics screen feels a little sparse right now
Event editor is solid. Node connections — actually intuitive. Tried building a three-stage patrol chain in under ten minutes. Worked first try. The offline part matters more than people realize — no account, no sync headaches, just the app. Stats screen is thin though. Agreed on that.
pixelRonan: my only real gripe is that the statistics screen feels a little sparse right now
I came to GamePlotter after spending some time with similar scenario-building tools that required constant connectivity and cloud accounts, and I must say the contrast is striking; there is something quietly reassuring about an application that keeps your work entirely on your own device, as this one does. I remember when offline-first design was simply the default expectation, and it is a shame it has become something worth remarking upon. That said, I do think the current version leaves certain things underdeveloped — the statistics dashboard, as others have noted, gives you a handful of numbers without much context for what they mean or how they relate to the complexity of what you have built, and I would appreciate some way to review the full structure of a scenario at a glance rather than navigating through each event individually. The event editor itself, however, is genuinely well-conceived; the separation of triggers, stages, actions, and rewards into distinct sections keeps even a moderately complex scenario from becoming unwieldy. I intend to keep using it and will be watching to see whether the developer addresses those gaps in upcoming updates.
pixelRonan: the datapack export feature is something I haven't fully explored yet
Been poking at this for a bit and it's decent for what it is — I used to get a lot more out of scenario-builder tools that came bundled with game engines, full editor suites basically free, and GamePlotter is obviously more focused and mobile-only, so the value comparison is a little different. For a standalone app doing this one specific thing, it holds up pretty well. The export feature is what sold me on keeping it installed — if I can actually reuse my datapacks elsewhere, that's where the real value is. Is anyone actually using the exported datapacks in other projects yet, or is that feature still pretty untested in the wild?
The offline argument is valid, but I'd push back slightly on calling the node editor 'actually intuitive' without qualification — for users who haven't worked with node-based tools before, there's a learning curve that the app doesn't do much to ease you into. There's no tutorial I could find, and the first time I opened the event editor I spent a few minutes just figuring out what connected to what. Once it clicked it was fine, and for what you get out of it the depth is reasonable, but the onboarding gap is a real cost that not everyone will be willing to pay.
carla_m92: there's a learning curve that the app doesn't do much to ease you into
Fair. No tutorial is a real gap — should have flagged that. Took me a minute too. App assumes you already think in nodes. Not everyone does.
Okay so that's a totally fair point and honestly I think I glossed over the learning curve a bit in my review because I was already kind of familiar with node-editor logic from other tools, so it clicked for me faster than it probably would for someone coming in cold, and now that you mention it I do remember hovering over the connection nodes for a while trying to figure out what direction the flow was supposed to go, so yeah, a little in-app guide or even just some tooltip text on the first launch would go a long way, especially for the trigger-to-stage relationship which is the part that confused me most initially, and I still think the core loop is really satisfying once you get there — but getting there is definitely a bit of a climb.
The absence of any onboarding guidance is, I think, the single most significant obstacle this application faces in reaching a wider audience. One can appreciate that the developer may have prioritized depth of functionality over hand-holding, and there is something to be said for that philosophy; but a brief interactive walkthrough — even just one covering the relationship between triggers, stages, and actions — would do an enormous amount of work in reducing the initial frustration that carla_m92 and TechTerrence have both described. I experienced the same confusion on first launch, and I say that as someone who has used node-based editors in other contexts before.