Grid Sage Forums
- May 02, 2024, 07:20:37 PM
- Welcome, Guest
|
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
Ideas / Interface / kb (alpha vs num)
« on: November 27, 2016, 07:31:43 AM »
When you do:
/-Number: it provides you with prompting to help you pick the right choice from the currently lettered items in your inventory.
When you do:
/-Alpha: it creates a new list of alphas from your inventory that has nothing to do with their current labels.
I like the way /-Number works a lot better, and if it's possible to extend this functionality to /-Alpha I think it would be good as an option if there's a reason for the current functionality or, if not, the only method.
/-Number: it provides you with prompting to help you pick the right choice from the currently lettered items in your inventory.
When you do:
/-Alpha: it creates a new list of alphas from your inventory that has nothing to do with their current labels.
I like the way /-Number works a lot better, and if it's possible to extend this functionality to /-Alpha I think it would be good as an option if there's a reason for the current functionality or, if not, the only method.
2
Fun thought:
Allow database queries that generate reports on 'known data'. Allow players to construct reusable query definitions and bind these to some set of keys to allow players to get quick reports on things that they might find interesting.
Depending on how things are implemented in the game right now this might not be possible without a gigantic overhaul.. But I think that from what I've seen it might be plausible.
(I thought about this because it occurred to me that it would be good to have a 'seen objects list' report that could be generated and ideally interacted with to some extent, but then my data analytics background kicked in.)
Allow database queries that generate reports on 'known data'. Allow players to construct reusable query definitions and bind these to some set of keys to allow players to get quick reports on things that they might find interesting.
Depending on how things are implemented in the game right now this might not be possible without a gigantic overhaul.. But I think that from what I've seen it might be plausible.
(I thought about this because it occurred to me that it would be good to have a 'seen objects list' report that could be generated and ideally interacted with to some extent, but then my data analytics background kicked in.)
3
- for alpha imo you should think about having report errors be the standard default, or at least prompt us to choose right off
- name would be a nice thing to be prompted to choose
Changes to defaults in general that I'd make:
-autoascend=on should go off imo
-if not for being part of the tutorial that leads players to it I'd say auto-enable parts should probably be on by default (it may rob players of volition slightly unlike autoascend=on new players will always want it on)
Personally I'd also max out on UI elements as well as a default but that may just be me. I know I have a bias on that one so I won't really make that a suggestion as much as a stating of personal preferences that should probably be ignored.
- name would be a nice thing to be prompted to choose
Changes to defaults in general that I'd make:
-autoascend=on should go off imo
-if not for being part of the tutorial that leads players to it I'd say auto-enable parts should probably be on by default (it may rob players of volition slightly unlike autoascend=on new players will always want it on)
Personally I'd also max out on UI elements as well as a default but that may just be me. I know I have a bias on that one so I won't really make that a suggestion as much as a stating of personal preferences that should probably be ignored.
Pages: [1]