Discussion in 'Bukkit News' started by Dinnerbone, Feb 25, 2011.
Appears to fix most of the problems, cheers!
I'm rather intrigued by jline, I must play around with it some time.
Win7 x64 sp1
dinner i have a quetsion where is the newest wroking version of bukkit i cant find it 2.0 i had a bunch of probs with and 2.1 it didnt work
I triple this. This breaks wrapper scripts something fierce. An option to turn it off would be very appreciated. I can't see continuing to use Bukkit without such.
I would think the concept would be to duplicate the default functionality of minecraft_server.jar by default with the OPTION to add plug-ins/etc as desired.
I've been pushing hard to get this working with MCMAs wrapper - I simply cannot get it to go.
I'm using build 474, using the the -d and -Djline.terminal=jline.UnsupportedTerminal options.
It's doing *something* to the console that completely breaks everything. Even if I stop MCMA from trying to push its standard input/output/error around (but leaves it redirected) then it stops any typed input from showing.
@SpaceManiac suggested something smart. I requested a feature for a disable option: http://leaky.bukkit.org/issues/524
524 appears to be a duplicate of 514 - http://leaky.bukkit.org/issues/514
Unfortunately it's target isn't until the Preview Release. So nobody using a wrapper will be able to use the newer versions until this is fixed.
Completely ignored twice, loving the support on how I can fix this. Time to scrap bukkit since plugins will keep getting updated and I won't be able to keep up stuck on build 440.
Ah I missed that because 514 is a "bug" and I figured it wasn't a bug since Dinnerbone did it on purpose. So 524 is a "feature request" and I only (foolishly) looked through feature requests first. Not sure how to handle those two now...
How about we get rcon, so GSPs can offer us a direct link to the server, as opposed to the requirement that we use Minecraft to admin the server now.
Mine seems to be working great! Running CB build 446 on CentOS 5. Everything works through SSH, and also the weird ioExceptions that were crashing my server seem to have stopped for the time being, which is awesome. Thanks, Bukkit devs! I <3 you!
@Dinnerbone Wow amazing. Now if there was a way to remove the 5 second delay from the console each time someone logged out you would be a genius! <3
Cough chunk unloading
Please read my response to see how to disable jline. I believe the jline, i.e. sensible, console should be the default. Bukkit already broke some wrappers by changing the time/date format, but that too can be changed back
Are you using -Djline.terminal=jline.UnsupportedTerminal as a java runtime or server process argument?
When I'm accessing a computer running a server via remote desktop, the console will sometimes freeze until I press a key. That's the only time I have it happen, but it happens quite frequently when managing a server that way (for me, using XP pro 32 on both computers).
I have had no problem:
- Directly managing a server on an XP box.
- Managing a MineOS server.
So the one I remote into is now just a test server... it doesn't get the privilege of always being on even.
It's in the plans as a default plugin.
Be patient. This isn't a recommended build yet and we've not finished tweaking how the console works yet. We're investigating how to make it easy to disable.
You're putting the -Djline part before -jar, right?
java -Djline.terminal=jline.UnsupportedTerminal -jar craftbukkit.jar
Did I mention it worked before ?
Build 470 is working relatively fine with Multicraft without any additional options, the only thing that breaks is console input (of the wrapper, not Minecraft itself).
If I add "-Djline.terminal=jline.UnsupportedTerminal" console input works fine.
Thank you for clarifying lukegb, it wasn't clear when I first scanned the thread I guess.
So, -Djline.terminal=jline.UnsupportedTerminal for a Java argument and -d"yyyy-MM-dd HH:mm:ss" for a CraftBukkit argument and it seems the worst now is a lot of extra ">" characters bouncing around.
It would still be really nice to have a simply switch to disable it, similar to the "nogui" argument perhaps. "nojline"?
Also it would be really nice to have that option mimic the default console exactly.
It would seem this time you failed a comprehension check. Read my first line after Basic answer: . You will see I explained why it USED to work. The very next sentence gives the likeliest reason why it NO LONGER works (about 95%+).
Dinnerbone, we've gotten in the habit of not ever using the server console unless it just hangs up and we need to restart. Mainly because of the messy Ctrl-C problem. We are on linux, and tail logs a lot, which you use ctrl-c to break out of, and if you happen to be in the console and forget, ctrl-c is an evil monkey, nasty, and of course, it stops the server with no save.
Can we get that disabled or captured and a "Are you sure" type of question asked?
Something else that would be nice, but not a must have type feature, is scrollback for the logs. If you are in screen, and know how to use it, it's built in, but I take it that some people don't use it, or don't know how to, so hitting Page-Up to scroll back to get crash info might be handy. Again, it's not a must, we have log files, etc, but seems logical to have it in the console.
One last thing, and I haven't run this under a load yet, but the error messages that pop up about the server being overloaded? Are these suppressed, or can we suppress messages like a filter? Again, not necessary, but a nice to have.
Love the arrow usage though, great addition.
Sure, I was considering it earlier. Will look into it tonight.
Edit: About ctrl+c.
In fact I quoted you so that Dinnerbone pay a little attention to this problem.
Where can we get the new console?
guide on how to access and use this new shiny terminal?
For everyone wanting to try the development build:
Maybe no one is bothering to answer you because this question is already answered very clearly in the Documentation.
Hint: Scroll up.
If I were a woman, I would have your babies. You, Sir... Rock.
Make a proper group/user system instead :/ THAT DOESN'T USE YAML!
Ah, apologies then.
Separate names with a comma.