I'm a tad confused about the mechanics. I've used the automated installer to ensure I have done nothing wrong on my end. And for mest part it does. Backslash opens the slick looking interface, message history and all. However any input, even SPC commands (I have this installed), returns a newline for new input. No "Bad Command" or any sort of recognition my command was executed.
Do I have the wrong idea when I believe this thing worked right out of the box?
EDIT
Nevermind. Ballsed up the PlayerAPI patch is all.
Yes I did. I had the mod working before 1.1, after that I just couldn't make it to work, the option to set the key set for it in the options does not appear at all either.
No errors at all, it's just like it's not there at all.
Try re-downloading the minecraft jar and using the automated minecraft console installer just to make sure nothing is going wrong.
Hey there, great mod (I'm now using this as an alternative to Improved Chat), just a few things I'd like to suggest: Could you please adjust your "Line-Too-Long-Feature"? (I wasn't sure how to call it, you know, the one that splits up sentences that are too long for the minecraft chat and sends the lines separately.) 2 requests: - Please don't do that for lines that start with a command. It often happens to me that I am typing a pretty long private-message (using the /m command, or /tmc for our server's team-chat), a bit of wrong estimation and half of your private message will be sent to public. (You might also invent some crazy command-filter that lets you configure how the parameters of some commands work and how this feature is supposed to deal with it. :P) - If it doesn't cause too much trouble, try not to cap sentences right inside words. Cap them earlier, at the end of a word. It will be easier to read. And besides that, I have a small bug report: When I write something to the chat and (by reflex) hit the ESC-button quickly after that, my message won't appear. (neither in the console, nor in normal chat) But I guess, its still being sent to the server... at least some of my conversations indicated that, I have never asked people wether the message arrived. Its not too serious, but if you know an easy fix for it... If not, well... gotta get rid of the bad habits. My current build is 4 days old if it matters. Thanks in advance
I have fixed the line wrapping when your message is too long. It will now wrap at a space if the space if it's reasonably close to one and it won't let you type over the message limit if your message starts with a /.
Oh and the escape thing just deletes what you have written so far. If you think it will help, I can add a setting that will submit anything you have left on close.
Thanks for the quick reply! I have tested the latest build, and found a small bug so far: If a sentence is too long and needs to be capped, the last word of the 2nd line is missing. About the missing-text-escape-issue: It's not like my input is disappearing, I have already pressed Enter and the message appeared in the window for a very short moment. Just when I press ESC too quickly after Enter, the Console closes and the message disappears again. But it has already been sent and the server also received it. (So did my client, and showed it for a short moment.)
Fixed that bug (and added wrapping at spaces to the history field). I'm still not sure what's happening with the escape thing. I can't seem to reproduce your problem. I have connected to a local test server and entered a message. I hit enter and escape as quickly as I could to see if I could get the server to see the message and it not be put in the history. The only thing I can think of is that I live to close to my testing server and the time it takes to recieve the message is somehow the problem.
To be honest, I can't reproduce it either when I try to.
It just happens occasionally, can't force it though :/
Thanks for the fix, but I found some more issues.
First, if your text is too long for the input-cell, some pixels don't fit into it and will be displayed outside.
Screenshot: http://img825.images...20313045144.png
(It also happens with minecraft's default font.)
And about the text-wrapping: Some 2nd lines are being cut off pretty early.
I suppose that, additionally to the "new" early cap at the end of a word, it also adopts minecraft's default chat window's message-wrapping.
In other words: If minecraft's chat decides to cap a word somewhere, the console will also do that, even though there's only 4 characters displayed on the current line so far.
Screenshots: http://img18.imagesh...20313043940.png http://img515.images...20313045244.png
Minecraft's default text-wrapping in this case: http://img440.images...20313045249.png (I wonder why it wraps incoming text like this anyway, since its width is much larger than minecraft's default chat.)
I can live with it like it is now, I was more focused on the text that's being sent to the server.
Just figured you'd like to know that.
I was actually able to reproduce the text dissappearing while I was in single player. I was using SPC and the commands sent but I didn't get their output. I'll look into it, and those other bugs tomorrow. Unfortunately one of the wrapping problems is due to minecraft wrapping the text before I get it. I might be able to undo their wrapping rules though.
I installed it after I installed ModLoader.
I think it's installed since the key for it is shown in the Options-screen.
But when i hit the key nothing happens.
Is it because I also have installed some other mods?
€dit: The other mods are : Optifine, Rei's Minimap, and InvTweaks.
Try change the key to something else. For me the default is BACKSLASH which doesnt work. I use BACK, that's backspace i think.
Do I have the wrong idea when I believe this thing worked right out of the box?
EDIT
Nevermind. Ballsed up the PlayerAPI patch is all.
Try re-downloading the minecraft jar and using the automated minecraft console installer just to make sure nothing is going wrong.
It's updated now! You can grab the latest build from github
TY MATE!
but this doesnt seem to work with zombes modpack :/ any chance to get this working WITH zombes?
I have fixed the line wrapping when your message is too long. It will now wrap at a space if the space if it's reasonably close to one and it won't let you type over the message limit if your message starts with a /.
Oh and the escape thing just deletes what you have written so far. If you think it will help, I can add a setting that will submit anything you have left on close.
Fixed that bug (and added wrapping at spaces to the history field). I'm still not sure what's happening with the escape thing. I can't seem to reproduce your problem. I have connected to a local test server and entered a message. I hit enter and escape as quickly as I could to see if I could get the server to see the message and it not be put in the history. The only thing I can think of is that I live to close to my testing server and the time it takes to recieve the message is somehow the problem.
I was actually able to reproduce the text dissappearing while I was in single player. I was using SPC and the commands sent but I didn't get their output. I'll look into it, and those other bugs tomorrow. Unfortunately one of the wrapping problems is due to minecraft wrapping the text before I get it. I might be able to undo their wrapping rules though.
They have an dev update, http://dl.dropbox.com/u/8016309/Minecraft%20Console/Minecraft_Console_Snapshot.zip
Looks interesting
Lou
Links to pdf format, downloadable, command lists for (these often clarify/expand descriptions, and where possible link to the author's posting):
MoreCommands: http://www.mediafire.com/view/qjc9c6klcnp660e/CmdLstMoreCommands.pdf
WorldEdit: http://www.mediafire.com/view/bi7r00xd9rgxrrt/WE_Commands.pdf
This doesn't replace SPC at all. There are not commands included it's just a wrapper for the chat function to make it better and more configurable.