Dedicated new & improved (?) KI thread.

[Aloys]

It may be worth noting the relative key positions between "QWERTY" and french keyboard mapping "AZERTY". Someone using rawkeys for input? :7

I was about to mention that. Keyboard support was wacky on all levels, both in the chat and for the movement key mapping.. Newcomers would often complain about why they had to map the W key instead of Z or vice-versa..
Why this was never flagged as a priority 1 bug when half of the player base was struck by it still baffles me.
Hoppefully this should be easy enough to fix.

[teedyo]

The default is a pain in the backside, I don't use WASD, ever!

Its just general key mapping, easy to change in code

I think you misunderstood my post. The default movement keys are the cursor keys.

What I don't get is people talking about typing 'z' to start chat. Is this a UU thing? I never remapped any keys in MOUL and just needed to type in order to chat. None of my alpha keys were mapped to anything. Maybe this was an international thing?

[D'Lanor]

Yes, the "z" thing was an UU bug. Possibly the MOUL open beta as well but I'm not sure about that. Anyway, it got fixed in MOUL so we don't have to worry about it.

The unicode bug which prevented typing of international characters on the other hand was introduced in MOUL. btw, can anyone remember what the error message was?

[J'Kla]

I have to take your word for it being fixed in MOUL as I got so used to it in UU I never used to start a line with a Z.

My default movement was always the arrow keys but I know users that had issues when running the game from laptops and I did not have that problem because i got one of those separate number pads that used either the mouse port or a usb.

[Aloys]

The unicode bug which prevented typing of international characters on the other hand was introduced in MOUL.

I'm pretty sure it has always been here. I might be wrong though.

[D'Lanor]

I am positive that unicode in chat worked fine in UU. I have found the MOUL error message: "Must be text only". I can see where the error occurs in the Python code. It has something to do with the petition commands.

Hmm, I just realized that I am already trying to fix things before we officially got the source. Oh well, it probably won't lead anywhere without in-game debugging.

[J'Kla]

Hmm, I just realized that I am already trying to fix things before we officially got the source. Oh well, it probably won't lead anywhere without in-game debugging.

I thought that was the whole point of this thread as something we could do while we were waiting.

[Grogyan]

Somone will shoot me for doing this

Considering Cyan has open sourced the KI, thought it'd be an idea to resurrect this thread

[Aloys]

This new Ki modification debate looks like a very nice mess waiting to happen.
Bug fixes or minute enhancements (unicode support; mouse wheel support etc) can be easily agreed upon but fundamental interface design 'flaws' means that a full re-design of the KI GUI is needed.. And that's just totally subjective. And doing design by commitee through a whole community? Thank you but no. We've already been through that with the DRC liaisons and I totally plan to stay out of this mess..

The Age rating/submission process debate will be complicated too but to a lesser degree..

[kaelisebonrai]

For me, I'm just ecstatic that we have (some) of the Old KI textures, at least.

Though, this review process is going to be bloody, and bloody messy, as well. I've missed pretty much all of the discussion on this (Yay, work!), so, can't comment on its state at present, but, its probably going to get nasty. very nasty. Also, uh, aren't alterations of game files still... well.. "Against the MOUL forum rules" still?

Even if Father Cyan has given out the files? =P