?Regarding the assertion that namespaces would be simple, my response is simply: Sure, it's not hard if you want something that works extremely well for a couple specific use cases and fails utterly for the way the myriad GMs actually WANT to use Realm Works.
Programmers don't usually realize - want to accept? - that they are given a very strict framework and forced to adapt everything they do to operate within that rigid framework. That's the EXACT OPPOSITE of the way end-users think. They want something that adapts to how THEY operate. Yes, even the programmers out there have wildly different approaches to GMing and creating their worlds, and most of them would balk at the notion of having to conform to a very specific - and different - way of doing everything just to have namespaces.
To a significant degree, we successfully adapt to the way different users operate within Realm Works, as the product works extremely well for a very diverse range of GM approaches. Achieving that, however, is FRICKIN' HARD. With some regularity, programmers comment that we should do things X way, because that would make things easier. Typically, it would make things easier for that user and the way they want to work, but it would be at the expense of large contingents of other users who think and work differently. Programmers also have a habit of saying that doing X should be easy, but they overlook this fundamental problem that it's only easy if we force all users to conform to a very specific way of using the product, which users aren't going to respond well to.
Believe me, hearing this stuff from programmers never ceases to frustrate the hell out of me.![]()
Adding a field to the DB, a dropdown after the suffix and adding a bit of logic that all defaults to "global" constrains anyone who doesn't want to use it how?
Look, I like this product and use it a lot and am one of your biggest boosters but I am also not just a programmer with 25 years experience. I'm a project manager with more than a decade in this sort of thing. I'm used to making end users happy and know the difference between something that sounds easy and something that is easy. You may not want to make the change for other reasons, I know of several, further cluttering the UI and the difficulty of explaining the concept to users are two, but bashing an honest suggestion over an area that is going to keep coming up once the CM goes live seems like a poor plan.