Nintenduh Report post Posted May 4, 2013 (edited) I would like to see #commands have more functional switches. $ #stats --help Mandatory arguments to long options are mandatory for short options too. -h, --help this screen. ~ -a, --all detailed long-form statistics -b, --bots detailed list of bots -p, --players detailed list of human players $ #research --help Mandatory arguments to long options are mandatory for short options too. -h, --help this screen. ~ -a, --all detailed long-form statistics -r, --read show read books -u, --unread show unread books -t, --time show total time spent reading books *approximated* $ #inv -h Beats me.. Any thoughts? Edited May 4, 2013 by Nintenduh Share this post Link to post Share on other sites
hussam Report post Posted May 4, 2013 I would like to be able to type: #exp | grep Overall Share this post Link to post Share on other sites
Raistlin Report post Posted May 4, 2013 $ #research --help -u, --unread show unread books try #know -u, also works with filtering like for example: know - u fight Share this post Link to post Share on other sites
revi Report post Posted May 4, 2013 a -h/--help option would be nice for those few commands that (can) take parameters. For the others, it might help avoid problems (the old #enemy-combatant?) (yes, I'm still an optimist ) and would still be nice to have. on the other hand, I see listing all on-line players or bots as less useful or even useless: there's a good page for that through the EL site, with extra options, and not all bots are trade bots. As for the time spent reading books: too many factors influence that for the value to be even remotely realistic: food level (no progress if below 0), rationality, fast reading rooms (what did I forget?) Share this post Link to post Share on other sites
Wizzy Report post Posted May 4, 2013 Why not add in a complete Bash shell into the client to access pc also? (I am being serious) Share this post Link to post Share on other sites
revi Report post Posted May 4, 2013 Tricky for those playing under MS-Windows (yes, there are a few who do that...). And parsing of one parameter is in place already (for #know command). Share this post Link to post Share on other sites
tork_unib Report post Posted May 4, 2013 Why not add in a complete Bash shell into the client to access pc also? (I am being serious) mmhm. tail and grep in combination with the chatlog is quite useful. Share this post Link to post Share on other sites
Nintenduh Report post Posted May 4, 2013 (edited) mmhm. tail and grep in combination with the chatlog is quite useful. I do like the idea of tail/head and grep. #sto|grep red Edited May 4, 2013 by Nintenduh Share this post Link to post Share on other sites
revi Report post Posted May 5, 2013 But then we don't need the Bash shell: grep and tail are not built-in commands of Bash. Grep or some more limited functionality like it would be nice to have, though. (And if it's decided to include a version of Bash, could we use it to send game commands to the server? ) Share this post Link to post Share on other sites
tork_unib Report post Posted May 5, 2013 But then we don't need the Bash shell: grep and tail are not built-in commands of Bash. Indeed true, both tail and grep are part if the gnu coreutils package. But i didn't explicitely say that either. I was more inspired by wizzy's suggestion than anything else and added a comment highlighting how a more *nix like approach to the client could help to enhance the client. As far as bash itself, well some of the commands could really use some sort of foreach structure: #ig seems like an obvious candidate. Share this post Link to post Share on other sites
revi Report post Posted May 6, 2013 That has been discussed before, esp. with regards to #IG: http://www.eternal-lands.com/forum/index.php?showtopic=57895&hl=message I think the main objection was that that would be too easy to spam lots of guilds. And I think there's a fear in general that any kind of loop could be abused too easily. Share this post Link to post Share on other sites
tork_unib Report post Posted May 6, 2013 That has been discussed before, esp. with regards to #IG: http://www.eternal-l...7895&hl=message I think the main objection was that that would be too easy to spam lots of guilds. And I think there's a fear in general that any kind of loop could be abused too easily. I recall the discussion. I agree that there are legitamate concerns. There are also potential benefits. Share this post Link to post Share on other sites
revi Report post Posted May 6, 2013 I recall the discussion. I agree that there are legitamate concerns. There are also potential benefits. Indeed. Personally, I think the balance would be towards not wanting such a 'multi-IG' system. To get back to the original suggestion: I think having a help option for each '#'-command would be ideal, as it gives a simple to use in-game explanation of how to use a command (and perhaps what it does). The encyclopedia would be the normal place for this information, but we all know that that is rather outdated. That's not a slur on the maintainers of the encyclopedia, they have a lot of work and also need to get the information (and programmers are notoriously bad at writing documentation, and I include myself in that...) Having the help for the '#'-commands in the source (as part of the program) might make it easier to keep it up to date. Share this post Link to post Share on other sites
SolarStar Report post Posted May 16, 2013 (edited) Can we get a level over IG so send messages to multiple guilds ? This would work in combination with guild ranks. Only rank 16 can use it. This would form larger groups in EL too. Edited May 16, 2013 by SolarStar Share this post Link to post Share on other sites
Nintenduh Report post Posted May 17, 2013 I would like to see auto-completion as well. That is, when you start a #command, TAB doesn't activate the map. Try to keep #IG stuffage related to command syntax please. Share this post Link to post Share on other sites
SolarStar Report post Posted May 17, 2013 autocomplete is done with CTRL + space or STRG+ Leer It works with names and commands. But not guild tags. Share this post Link to post Share on other sites