Lachesis

I'm always anew[ly] amazed by our artists' works. I'm looking forward to seeing them in game. I'm not sure how you want to place the text on the heavily torn one though. It would be possible to set high margins so that the text only appears in the middle, but I'm not sure if that's what you want. If not, can you please make an example with text on that paper? Thank you Lachesis

Something that came into my mind ... the problem is that we are thinking the client either knows of the invisible person or not. But it can also partially know. That is, when the character moves there might be some small probability that a nearby client gets a notification. But that information is only worthful for a short time because the invisible player might already have moved elsewhere. I really like the idea of real invisibility, it's a really great thing for role plays.

Oh, sorry, I didn't expect you don't have time sync ... should be worth consideration shouldn't it? Using timestamps the server can work a little ahead if he has some spare time or bandwidth and doesn't get in a hurry that easily. Sorry for hijacking the thread!

Or you just include the time when the movement will happen in the message

No Problem, CK, it's not urgent.

Why have you included the older revisions (.#-files) and CVS-Information in the ZIP archive? Can you please make a patch for encyclopedia.xml at once, it is easier for me to look at the modifications for finding format bugs of that file, since AFAIK the last revision was bug-free

This is an ancient usenet/forum joke, but it's my favorite and so I think it shouldn't be missing here. German: U: Man kann über alles geteilter Meinung sein. A: Das sehe ich anders. English original: O: Nothing is unarguable. R: I disagree.

Nicht, wenn man den Quartz selber abbaut. Seit wann sind es eigentlich 4 GM, ich hab bisher immer 3 GM gezahlt?

Das "flücht" bezog sich auf meine eigene Gilde, Ketzer. Wie meinst du das mit der Drogeriemarktgilde, Klaus?

Weird, I had a look at the TinyXML code and it should accept plain LF, plain CR, CRLF and even LFCR as a single newline. Must be some hidden bug.

Stupid Cal3D, let's write a bug report ;-) What does it use? Mac style? DOS/Win style?

Wytters book window is 320x400 pixels in size for scrolls and 528x320 pixels in size for books, you can align with that if you like. Don't make them too big. The texture image size has to be a power of 2: 32x32, 64x64, ... up to 512x512. They are scaled using the height and width (in pixels) properties in imagedef.xml. Try to use as small as possible images to save memory. Sorry, I won't let you hard-code the stain or tear position, because it won't work with the translations. I know it might look better, but you can already achieve good results with alpha blending for the stains (oops, seems we need PNG). Torn pages are even worse with translations, so I think it's best restricting them to abruptly ending pages (you define the word after which to end). I could then try to squish and squeeze a tear texture so that it fits the final position of that word. Both features are dreams of the future though, there are lots of more vital things to do first. In the meantime, you'll have to describe the stains and tears in words I'm sorry. With regards Lachesis

XML files should always be saved in UNIX format, the specification requires it.

No problems related to VBO here either.

Itilli sells Jewlery Books instead of Jewelry Books.

For now, yes, Derin. Other formats may be supported later. One day ;-) Lyanna, the word wrapping is done in the client and depends on the locale and default font size the player chooses. However I think it could be possible to create a stain texture that is then rendered at the final position of a piece of text enclosed by a stain tag. Torn pages are much harder because not only is it complicated to define what portion of the text shall be hidden by the tear, but also it cannot be moved with reewrapped text in a sane manner.

This one I guess? Nice work indeed. Didn't look under accepted patches :blushes:

I thought you were talking about stains that hide text or torn pages that cut the text. Background images would not be difficult. Currently, only the two backgrounds provided by Wytter are used, I'll make the visual format more flexible then. Just add your backgrounds to the textures directory* and add an image definition to textures/imagedef.xml*. The height and width you provide there will become the size of the window (unless you specify double-page display). You do not need to change your source documents for this, such visual effects will be created by separate XSLT stylesheets for your books. Most of the stuff in encyclopedia.xsl is not needed by "normal" books so they will look much simpler and you will probably be able to change minor things such as background images even without any knowledge of XSLT. You will probably also need extensions to the semantic format, for instance maybe tags for songs/poems (and their verses). If you encounter any, please request them immediately as these will directly affect the source documents that are currently written. With regards Lachesis *) on freepository, please see Encyclopedia forum

Please try to get rid of it, otherwise we get "spaghetti code"* Keeping that code will cause many more bugs on the medium term, because it doesn't fit with the Cal3D animation handling. So it would be a kludge and nobody wants that. *) I don't know if that term exists in English, it basicly means code that is hard to maintain.

CK, can you please correct the case in the zip file? And please inform all authors to use an xml-declaration at the top of their files otherwise libxml will complain. Of course, they have to replace "UTF-8" with the encoding they actually use. All authors working on the same file will have to use the same encoding though, so UTF-8 is probably not a bad idea. Microsoft's software supports it since around 2000. I don't know how long it's been supported by Linux, I've been using Linux for three years only so far. P.S. The correct tag name is "appropriate_name" (without "Pw"). I don't know what screwed it up, how did you create the files, CK?

Mikeman, we could as well make it simpler: we introduce three generic messages START_ACTION, STOP_ACTION and PERFORM_ACTION. The former are for continuous actions (idle) whereas the latter is for one-time actions (currently all other). The server then just forwards this info to the clients (in range), and these decide what animations to start. The relation between actions and animations can be stored in an XML file shipped with the client. In that way, adding an animation that does nothing but show up (like emotes) can be done fully client-side. Further more, changing the animations attached to a specific action can even be done without modifying client code. P.S. No, there is no good list implementation in ELC yet. Most list code is implicit, there are no generic functions. If you ask me, using the container classes (that have a close-to-optimal implementation in gcc) is just one of many reasons for using C++, but the god says no :angel: So we are reinventing C++ (look at the window handling). Maybe you can "copy" the list implementation from gcc as well, though it'll probably be hard to draw the algorithms out of all the template clutter ;-)

That Patch is not on BerliOS, where is it?

I thought you were talking about cash, not virtual gold coins ... If you have read visual art you'd even know that there'll be two new monsters with a combat strength between those of Fluffy Rabbit and Chimeran Mountain Wolf in the next release.

Mikeman, we need a new animation handling for animation mixing, and it looks like we need a protocol change as well. Don't hesitate to throw some more of the old character handling code overboard if it helps to clean up.

What about rearrangering some PP for cash? And there's still the suggestion of moving 2 PP instead of spending one at high OA levels.