majestyk

I think the options should be applicable to all EL-ers, not guild specific or something that only 1 or 2 people find funny. I doubt we can have limitless options so we need to get the most bang for the buck for what is offered. Yes exactly, I won't be making any "inside joke" type artwork. This is not what I was talking about. Not all quotes on the "quote of the week" page are funny for 1-2 people only. I don't understand all of it either, but there are some which most EL players find funny, and I was referring to those "some". Even though this was not what I was intending, it seems a good idea to me. I can see a possible market for #beaver shirts and whatnot.

Great idea Roja, I have waited a long time for this. I didn't like the available motives so far, but this is going to be great. There will certainly be more great ideas than I'd ever be able to afford How about lending some quotes from the "quote of the week" thread? Cheers, maj

Sensible defaults are there to make things _easier_, not to make them possible (or impossible). All arguments like "press Crtl-I", "use the bag icon" etc. are not at the right place here, it was neither asked for "how do I open the inventory" or "how do I open it best". The suggestion was to make things more intuitive, and that should still be the main priority of every user interface. It is intuitive that the default for inventory items and quick-slot items is "use". It is intuitive that the default icon for doors, caves etc is the "door" icon to enter. I don't think it is intuitive to always have to right-click once into the main-window to "reset" the pointer so it will auto-change again. IMO this is a "workaround" for a broken interface, good that we humans can easily adjust to that. Try playing another role-playing game, and you will find yourself asking why you right-click into the main screen so often. And regarding point 1: the point is not to enforce the client to always use a certain action on something, but to use a sensible _default_ action on something. Only because the default is to attack monsters or harvest ores does not mean you would not be able to manually change the pointer to "use" if you want to try it. I think these are some valid points. The user interface is what makes you see, feel and enjoy the virtual world, and I think there's still much room for improvements here. Cheers, maj

I wouldn't have thought that the rate where character transfers are made is so high. Just for the sake of my curiosity, what is the churn rate? How many new characters are created per week? And how many characters are bought/sold? And, to be more on-topic: I like the idea of having a birthday. Maybe even connected with getting a "It's <buddy>'s birthday today!" message for characters on your buddy list Basically I am in favor of everything which adds to character differentiation and deeper identification with your character. Cheers, maj

This is correct, but only for higher level armor and swords, not for starter equipment. Higher level stuff has "degraded", i.e. "damaged" states where they can be repaired. lower level stuff just vanishes. And once it's gone, it's gone. And no, you are not going to lose anything when harvesting. But trust me, it will soon become very tiring to harvest flowers for gc.

Like in "not targetted" and affecting an area surrounding you, affecting all guildies in that area? Sounds nice care to explain? what about harm, poison, mana drain, remote heal, etc? The difference is - harm, poison, mana drain also work "through" obstacles, not requiring a clear line of sight like an arrow shot would. This might be different for fireballs, lighting bolts etc. since they are "matter", not only magic energy

So, this means this paticular spell belongs to the former, the later, or is this entirely unrelated? Neither is Heal, Remote Heal, Restoration, Shield, Harm, ... . It's hard to come up with the idea of a spell which has never been used before, and then it would most likely be either of the "hard to implement" category, or fall into the "know they won't work" category Cheers, maj

I compiled a CVS client this morning, and ran EL for like 8 hours straight. You can see a slight, but constant memory increase: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND Thu May 10 09:44:35 CEST 2007 majestyk 31770 13.2 5.8 162276 121628 pts/3 SLl+ 09:44 0:03 \_ ./el.x86.linux.bin Thu May 10 09:49:35 CEST 2007 majestyk 31770 48.3 7.0 185348 145400 pts/3 RLl+ 09:44 2:36 \_ ./el.x86.linux.bin Thu May 10 09:54:35 CEST 2007 majestyk 31770 47.5 7.6 198904 159480 pts/3 SLl+ 09:44 4:56 \_ ./el.x86.linux.bin Thu May 10 09:59:35 CEST 2007 majestyk 31770 39.3 7.7 200556 161268 pts/3 SLl+ 09:44 6:03 \_ ./el.x86.linux.bin Thu May 10 10:04:35 CEST 2007 majestyk 31770 34.8 7.7 200292 161004 pts/3 RLl+ 09:44 7:07 \_ ./el.x86.linux.bin Thu May 10 10:09:35 CEST 2007 majestyk 31770 33.0 7.7 200292 161004 pts/3 RLl+ 09:44 8:23 \_ ./el.x86.linux.bin Thu May 10 10:14:35 CEST 2007 majestyk 31770 32.9 7.7 200292 161024 pts/3 RLl+ 09:44 10:00 \_ ./el.x86.linux.bin Thu May 10 10:19:35 CEST 2007 majestyk 31770 32.8 7.7 200372 161144 pts/3 RLl+ 09:44 11:37 \_ ./el.x86.linux.bin Thu May 10 10:24:35 CEST 2007 majestyk 31770 32.6 7.7 200640 161424 pts/3 RLl+ 09:44 13:12 \_ ./el.x86.linux.bin Thu May 10 10:29:35 CEST 2007 majestyk 31770 31.3 7.7 200640 161424 pts/3 SLl+ 09:44 14:13 \_ ./el.x86.linux.bin Thu May 10 10:34:35 CEST 2007 majestyk 31770 29.8 7.7 200164 160948 pts/3 SLl+ 09:44 15:01 \_ ./el.x86.linux.bin Thu May 10 10:39:35 CEST 2007 majestyk 31770 30.4 7.7 200164 160952 pts/3 SLl+ 09:44 16:51 \_ ./el.x86.linux.bin Thu May 10 10:44:35 CEST 2007 majestyk 31770 29.6 7.7 200768 161556 pts/3 SLl+ 09:44 17:53 \_ ./el.x86.linux.bin Thu May 10 10:49:35 CEST 2007 majestyk 31770 28.6 7.7 200292 161080 pts/3 SLl+ 09:44 18:45 \_ ./el.x86.linux.bin Thu May 10 10:54:35 CEST 2007 majestyk 31770 27.5 7.8 201600 162388 pts/3 SLl+ 09:44 19:25 \_ ./el.x86.linux.bin Thu May 10 10:59:35 CEST 2007 majestyk 31770 27.1 7.8 201600 162388 pts/3 SLl+ 09:44 20:27 \_ ./el.x86.linux.bin Thu May 10 11:04:35 CEST 2007 majestyk 31770 26.2 7.8 201780 162568 pts/3 RLl+ 09:44 21:06 \_ ./el.x86.linux.bin Thu May 10 11:09:35 CEST 2007 majestyk 31770 25.7 7.8 201780 162568 pts/3 RLl+ 09:44 22:02 \_ ./el.x86.linux.bin Thu May 10 11:14:35 CEST 2007 majestyk 31770 25.4 7.8 202076 162836 pts/3 SLl+ 09:44 22:58 \_ ./el.x86.linux.bin Thu May 10 11:19:35 CEST 2007 majestyk 31770 25.2 7.8 202012 162796 pts/3 RLl+ 09:44 24:05 \_ ./el.x86.linux.bin Thu May 10 11:24:35 CEST 2007 majestyk 31770 24.8 7.8 202688 163480 pts/3 SLl+ 09:44 25:00 \_ ./el.x86.linux.bin Thu May 10 11:29:35 CEST 2007 majestyk 31770 24.3 7.8 202012 162804 pts/3 SLl+ 09:44 25:41 \_ ./el.x86.linux.bin Thu May 10 11:34:35 CEST 2007 majestyk 31770 23.8 7.8 202536 163328 pts/3 SLl+ 09:44 26:20 \_ ./el.x86.linux.bin Thu May 10 11:39:36 CEST 2007 majestyk 31770 24.4 7.8 202328 163120 pts/3 SLl+ 09:44 28:09 \_ ./el.x86.linux.bin Thu May 10 11:44:36 CEST 2007 majestyk 31770 24.8 7.8 202012 162804 pts/3 RLl+ 09:44 29:52 \_ ./el.x86.linux.bin Thu May 10 11:49:36 CEST 2007 majestyk 31770 24.7 7.8 202260 163064 pts/3 RLl+ 09:44 31:01 \_ ./el.x86.linux.bin Thu May 10 11:54:36 CEST 2007 majestyk 31770 25.0 7.8 202560 163236 pts/3 RLl+ 09:44 32:42 \_ ./el.x86.linux.bin Thu May 10 11:59:36 CEST 2007 majestyk 31770 25.5 7.8 202076 162880 pts/3 SLl+ 09:44 34:33 \_ ./el.x86.linux.bin Thu May 10 12:04:36 CEST 2007 majestyk 31770 24.9 7.8 202992 163796 pts/3 SLl+ 09:44 34:58 \_ ./el.x86.linux.bin Thu May 10 12:09:36 CEST 2007 majestyk 31770 24.1 7.9 204756 165548 pts/3 SLl+ 09:44 35:02 \_ ./el.x86.linux.bin Thu May 10 12:14:36 CEST 2007 majestyk 31770 23.3 7.9 204756 165560 pts/3 SLl+ 09:44 35:03 \_ ./el.x86.linux.bin Thu May 10 12:19:36 CEST 2007 majestyk 31770 22.5 7.9 204756 165568 pts/3 SLl+ 09:44 35:03 \_ ./el.x86.linux.bin Thu May 10 12:24:36 CEST 2007 majestyk 31770 21.9 7.9 204756 165568 pts/3 SLl+ 09:44 35:11 \_ ./el.x86.linux.bin Thu May 10 12:29:36 CEST 2007 majestyk 31770 21.2 7.9 204756 165572 pts/3 SLl+ 09:44 35:13 \_ ./el.x86.linux.bin Thu May 10 12:34:36 CEST 2007 majestyk 31770 20.7 8.0 207064 167984 pts/3 SLl+ 09:44 35:22 \_ ./el.x86.linux.bin Thu May 10 12:39:36 CEST 2007 majestyk 31770 20.2 8.0 207064 168000 pts/3 RLl+ 09:44 35:29 \_ ./el.x86.linux.bin Thu May 10 12:44:36 CEST 2007 majestyk 31770 19.7 8.0 207064 168000 pts/3 SLl+ 09:44 35:39 \_ ./el.x86.linux.bin Thu May 10 12:49:36 CEST 2007 majestyk 31770 19.3 8.0 207064 168000 pts/3 SLl+ 09:44 35:49 \_ ./el.x86.linux.bin Thu May 10 12:54:36 CEST 2007 majestyk 31770 18.8 8.0 207064 168000 pts/3 SLl+ 09:44 35:52 \_ ./el.x86.linux.bin Thu May 10 12:59:36 CEST 2007 majestyk 31770 18.4 8.0 207064 168000 pts/3 SLl+ 09:44 36:01 \_ ./el.x86.linux.bin Thu May 10 13:04:36 CEST 2007 majestyk 31770 18.0 8.0 207064 168000 pts/3 SLl+ 09:44 36:05 \_ ./el.x86.linux.bin Thu May 10 13:09:36 CEST 2007 majestyk 31770 17.5 8.0 207064 168000 pts/3 SLl+ 09:44 36:05 \_ ./el.x86.linux.bin Thu May 10 13:14:36 CEST 2007 majestyk 31770 17.2 8.0 207064 168000 pts/3 SLl+ 09:44 36:15 \_ ./el.x86.linux.bin Thu May 10 13:19:36 CEST 2007 majestyk 31770 16.8 8.0 207064 168000 pts/3 SLl+ 09:44 36:22 \_ ./el.x86.linux.bin Thu May 10 13:24:36 CEST 2007 majestyk 31770 16.6 8.0 207064 168000 pts/3 SLl+ 09:44 36:41 \_ ./el.x86.linux.bin Thu May 10 13:29:36 CEST 2007 majestyk 31770 16.2 8.0 207064 168000 pts/3 SLl+ 09:44 36:42 \_ ./el.x86.linux.bin Thu May 10 13:34:36 CEST 2007 majestyk 31770 15.9 8.0 207064 168000 pts/3 SLl+ 09:44 36:42 \_ ./el.x86.linux.bin Thu May 10 13:39:36 CEST 2007 majestyk 31770 15.5 8.0 207064 168000 pts/3 SLl+ 09:44 36:42 \_ ./el.x86.linux.bin Thu May 10 13:44:36 CEST 2007 majestyk 31770 15.2 8.0 207064 168000 pts/3 SLl+ 09:44 36:42 \_ ./el.x86.linux.bin Thu May 10 13:49:36 CEST 2007 majestyk 31770 14.9 8.0 207064 168000 pts/3 SLl+ 09:44 36:43 \_ ./el.x86.linux.bin Thu May 10 13:54:36 CEST 2007 majestyk 31770 14.6 8.0 207064 168000 pts/3 SLl+ 09:44 36:43 \_ ./el.x86.linux.bin Thu May 10 13:59:36 CEST 2007 majestyk 31770 14.3 8.0 207064 168000 pts/3 SLl+ 09:44 36:43 \_ ./el.x86.linux.bin Thu May 10 14:04:36 CEST 2007 majestyk 31770 14.1 8.0 207064 168000 pts/3 SLl+ 09:44 36:43 \_ ./el.x86.linux.bin Thu May 10 14:09:36 CEST 2007 majestyk 31770 13.8 8.0 207064 168000 pts/3 SLl+ 09:44 36:47 \_ ./el.x86.linux.bin Thu May 10 14:14:37 CEST 2007 majestyk 31770 13.6 8.0 207064 168000 pts/3 RLl+ 09:44 36:57 \_ ./el.x86.linux.bin Thu May 10 14:19:37 CEST 2007 majestyk 31770 13.4 8.0 207064 168000 pts/3 SLl+ 09:44 36:57 \_ ./el.x86.linux.bin Thu May 10 14:24:37 CEST 2007 majestyk 31770 13.1 8.0 207064 168000 pts/3 SLl+ 09:44 36:57 \_ ./el.x86.linux.bin Thu May 10 14:29:37 CEST 2007 majestyk 31770 12.9 8.0 207064 168000 pts/3 SLl+ 09:44 36:59 \_ ./el.x86.linux.bin Thu May 10 14:34:37 CEST 2007 majestyk 31770 12.7 8.0 207064 168028 pts/3 SLl+ 09:44 37:00 \_ ./el.x86.linux.bin Thu May 10 14:39:37 CEST 2007 majestyk 31770 12.5 8.0 207064 168028 pts/3 SLl+ 09:44 37:04 \_ ./el.x86.linux.bin Thu May 10 14:44:37 CEST 2007 majestyk 31770 12.3 8.0 207064 168028 pts/3 SLl+ 09:44 37:12 \_ ./el.x86.linux.bin Thu May 10 14:49:37 CEST 2007 majestyk 31770 12.2 8.0 207064 168028 pts/3 SLl+ 09:44 37:17 \_ ./el.x86.linux.bin Thu May 10 14:54:37 CEST 2007 majestyk 31770 12.0 8.0 207064 168028 pts/3 SLl+ 09:44 37:22 \_ ./el.x86.linux.bin Thu May 10 14:59:37 CEST 2007 majestyk 31770 12.0 8.0 207064 168032 pts/3 SLl+ 09:44 37:56 \_ ./el.x86.linux.bin Thu May 10 15:04:37 CEST 2007 majestyk 31770 11.8 8.0 207064 168032 pts/3 SLl+ 09:44 38:01 \_ ./el.x86.linux.bin Thu May 10 15:09:37 CEST 2007 majestyk 31770 11.6 8.0 207064 168032 pts/3 RLl+ 09:44 38:02 \_ ./el.x86.linux.bin Thu May 10 15:14:37 CEST 2007 majestyk 31770 11.5 8.0 207064 168032 pts/3 SLl+ 09:44 38:03 \_ ./el.x86.linux.bin Thu May 10 15:19:37 CEST 2007 majestyk 31770 11.3 8.0 207064 168032 pts/3 SLl+ 09:44 38:04 \_ ./el.x86.linux.bin Thu May 10 15:24:37 CEST 2007 majestyk 31770 11.1 8.0 207064 168032 pts/3 SLl+ 09:44 38:06 \_ ./el.x86.linux.bin Thu May 10 15:29:37 CEST 2007 majestyk 31770 11.0 8.0 207064 168032 pts/3 SLl+ 09:44 38:12 \_ ./el.x86.linux.bin Thu May 10 15:34:37 CEST 2007 majestyk 31770 10.9 8.0 207064 168032 pts/3 SLl+ 09:44 38:17 \_ ./el.x86.linux.bin Thu May 10 15:39:37 CEST 2007 majestyk 31770 10.7 8.0 207064 168032 pts/3 SLl+ 09:44 38:18 \_ ./el.x86.linux.bin Thu May 10 15:44:37 CEST 2007 majestyk 31770 10.6 8.0 207064 168032 pts/3 SLl+ 09:44 38:21 \_ ./el.x86.linux.bin Thu May 10 15:49:37 CEST 2007 majestyk 31770 10.5 8.0 207064 168060 pts/3 SLl+ 09:44 38:33 \_ ./el.x86.linux.bin Thu May 10 15:44:37 CEST 2007 majestyk 31770 10.6 8.0 207064 168032 pts/3 SLl+ 09:44 38:21 \_ ./el.x86.linux.bin Thu May 10 15:49:37 CEST 2007 majestyk 31770 10.5 8.0 207064 168060 pts/3 SLl+ 09:44 38:33 \_ ./el.x86.linux.bin Thu May 10 15:54:37 CEST 2007 majestyk 31770 10.4 8.0 207064 168060 pts/3 RLl+ 09:44 38:36 \_ ./el.x86.linux.bin Thu May 10 15:59:37 CEST 2007 majestyk 31770 10.3 8.0 207064 168060 pts/3 RLl+ 09:44 38:47 \_ ./el.x86.linux.bin Thu May 10 16:04:37 CEST 2007 majestyk 31770 10.2 8.0 207064 168060 pts/3 RLl+ 09:44 39:00 \_ ./el.x86.linux.bin Thu May 10 16:09:37 CEST 2007 majestyk 31770 10.1 8.0 207064 168060 pts/3 RLl+ 09:44 39:00 \_ ./el.x86.linux.bin Thu May 10 16:14:37 CEST 2007 majestyk 31770 9.9 8.0 207064 168060 pts/3 SLl+ 09:44 39:00 \_ ./el.x86.linux.bin Thu May 10 16:19:37 CEST 2007 majestyk 31770 9.8 8.0 207064 168060 pts/3 RLl+ 09:44 39:01 \_ ./el.x86.linux.bin Thu May 10 16:24:37 CEST 2007 majestyk 31770 9.7 8.0 207064 168060 pts/3 SLl+ 09:44 39:02 \_ ./el.x86.linux.bin Thu May 10 16:29:37 CEST 2007 majestyk 31770 9.6 8.0 207064 168060 pts/3 SLl+ 09:44 39:03 \_ ./el.x86.linux.bin Thu May 10 16:34:37 CEST 2007 majestyk 31770 9.5 8.0 207064 168060 pts/3 SLl+ 09:44 39:07 \_ ./el.x86.linux.bin Thu May 10 16:39:37 CEST 2007 majestyk 31770 9.4 8.0 207064 168060 pts/3 SLl+ 09:44 39:11 \_ ./el.x86.linux.bin Thu May 10 16:44:37 CEST 2007 majestyk 31770 9.3 8.0 207064 168060 pts/3 SLl+ 09:44 39:14 \_ ./el.x86.linux.bin Thu May 10 16:49:37 CEST 2007 majestyk 31770 9.2 8.0 207064 168060 pts/3 SLl+ 09:44 39:19 \_ ./el.x86.linux.bin Thu May 10 16:54:38 CEST 2007 majestyk 31770 9.1 8.0 207064 168060 pts/3 SLl+ 09:44 39:22 \_ ./el.x86.linux.bin Thu May 10 16:59:38 CEST 2007 majestyk 31770 9.0 8.0 207064 168060 pts/3 SLl+ 09:44 39:26 \_ ./el.x86.linux.bin Thu May 10 17:04:38 CEST 2007 majestyk 31770 8.9 8.0 207064 168060 pts/3 SLl+ 09:44 39:28 \_ ./el.x86.linux.bin Thu May 10 17:09:38 CEST 2007 majestyk 31770 8.8 8.0 207064 168060 pts/3 SLl+ 09:44 39:29 \_ ./el.x86.linux.bin Thu May 10 17:14:38 CEST 2007 majestyk 31770 8.7 8.0 207064 168060 pts/3 SLl+ 09:44 39:30 \_ ./el.x86.linux.bin Thu May 10 17:19:38 CEST 2007 majestyk 31770 8.7 8.0 207064 168060 pts/3 SLl+ 09:44 39:45 \_ ./el.x86.linux.bin Thu May 10 17:24:38 CEST 2007 majestyk 31770 8.6 8.0 207064 168060 pts/3 SLl+ 09:44 39:47 \_ ./el.x86.linux.bin Thu May 10 17:29:38 CEST 2007 majestyk 31770 8.5 8.0 207064 168060 pts/3 SLl+ 09:44 39:58 \_ ./el.x86.linux.bin Thu May 10 17:34:38 CEST 2007 majestyk 31770 8.5 8.0 207064 168060 pts/3 SLl+ 09:44 40:11 \_ ./el.x86.linux.bin Thu May 10 17:39:38 CEST 2007 majestyk 31770 8.5 8.0 207064 168060 pts/3 SLl+ 09:44 40:47 \_ ./el.x86.linux.bin Thu May 10 17:44:38 CEST 2007 majestyk 31770 8.6 8.0 207064 168060 pts/3 SLl+ 09:44 41:26 \_ ./el.x86.linux.bin Thu May 10 17:49:38 CEST 2007 majestyk 31770 8.7 8.8 221828 182752 pts/3 SLl+ 09:44 42:40 \_ ./el.x86.linux.bin Thu May 10 17:54:38 CEST 2007 majestyk 31770 8.7 8.1 209200 170124 pts/3 SLl+ 09:44 42:53 \_ ./el.x86.linux.bin Thu May 10 17:59:38 CEST 2007 majestyk 31770 8.6 8.1 209200 170124 pts/3 SLl+ 09:44 42:54 \_ ./el.x86.linux.bin Thu May 10 18:04:38 CEST 2007 majestyk 31770 8.5 8.1 209200 170124 pts/3 SLl+ 09:44 42:55 \_ ./el.x86.linux.bin Sorry that I can't be of more service, but C is not where I really feel at ease. Cheers, maj

I voted yes. I always thought restoration was overpowered the way it is. Nothing against having a restoration spell like we already have, but it should only be available for high level magicians (50+?) and for a much higher cost (15-20HE? 10HE+4LE?). Having a spell that "scales" with your magic level for the time in between is a good idea. Additionally, I think this will bring higher rotation to spawns, which is nice too. Cheers, maj

It is good to know that this skill doesn't have a cap. More and more years to come! And higher level always pwns n00bs.

Good to know there's a life after 29

I wouldn't have thought so, but I seem to be in about the middle - only slightly over 50% of the players so far are younger than I am. That's surprising! PS - if less than 700 people vote this will not be scientifically valid. Vote on folks

I know someone who is in the 61+ category. Speak up, you know who I am talking about

Well, that thread isn't that interesting because it does not represent the current state if it's really that old. Besides, to be honest, I didn't know how to perform a search searching for 3 letter words like "old" and "age" Edit: keep on posting, I already feel less old

Hm, I was able to do a "cvs up" yesterday evening (my time, so about 12 hours ago), but now I can't cvs up any more: cvs server: Updating . cvs server: [08:00:21] waiting for raduprv's lock in /cvsroot/elc/elc cvs server: [08:00:51] waiting for raduprv's lock in /cvsroot/elc/elc cvs server: [08:01:21] waiting for raduprv's lock in /cvsroot/elc/elc cvs server: [08:01:51] waiting for raduprv's lock in /cvsroot/elc/elc cvs server: [08:02:21] waiting for raduprv's lock in /cvsroot/elc/elc cvs server: [08:02:51] waiting for raduprv's lock in /cvsroot/elc/elc cvs server: [08:03:21] waiting for raduprv's lock in /cvsroot/elc/elc cvs server: [08:03:51] waiting for raduprv's lock in /cvsroot/elc/elc cvs server: [08:04:21] waiting for raduprv's lock in /cvsroot/elc/elc cvs server: [08:04:51] waiting for raduprv's lock in /cvsroot/elc/elc cvs server: [08:05:21] waiting for raduprv's lock in /cvsroot/elc/elc Looks like indeed you're the only one who is able to access the CVS right now

yes, nobody owns spawns, you can come and start serping my double if you want, and I can brod whole your guild if I find anyone in PK, serped your spawns, ... it is alowed too btw \o/ ... isnt better be polite and wait? If I get an empty double spawn, I am happy. If someone else comes in and wants to train, I offer one of the spawns. Isn't it better to be polite and offer one of your double spawns than to wait if you can make another enemy?

Today I had two strange red messages showing up in my console, when I was sitting AFK at VoTD sto: Premature start of weather effect! and a while later: Double stop of weather effect! Unfortunately I was AFK, and I was in console mode, so I couldn't see the mysterious weather effect I couldn't find anything logged in the chat_log, the stdout/stderr or the error.log. System is a gentoo linux, using standard (default) FEATURES. If there's something I can help you with to debug, just name it. Cheers, maj

Where are you going to place that proxy? It's either close to the EL game server, so it will be affected by bad routers too, or in any other place, therefore adding to the latency you already have. I (as a european) would certainly not like to use a proxy in the US. It also adds to the maintenance tasks you already have - if a player is banned from the game, he not only has to be blocked on the server, but also have to be disabled/IP banned on the proxy. If you are going to have the proxy listen on port 2000, you will also not solve the problem that some universities block that port. If you are not using port 2000, it would be just as hard to change the player's config as if you would change the EL game server port. So, summarizing, you might be able to workaround some player's problems, and it might be enough players to even pay for itself eventually. But it doesn't solve the problems themselves. PS - for the server port problem - using a (temporary?) DNAT rule to forward incoming connections on port XYZ to the local port 2000 would make for an easy transition phase when changing ports, and could also be used to offer other ports for playing the game in case connecting over port 2000 is broken/blocked. Cheers, maj

Beaverhunter: that's exactly what's Trollson is talking about: mix/max/mean statistics, based on lowest/highest/average values. What I would like to see is to have a "rank" based on the amount of skills at a certain level: 3 skills above level 20: junior squire 3 skills above level 40: junior knight ... 4 skills above level 20: senior squire 4 skills above level 40: senior knight ... 5 skills above level 20: master squire 5 skills above level 40: master knight ... 6 skills above level 20: grand squire 6 skills above level 40: grand knight ... [ and so on, you get the picture ] What I think would be cool would be if you could see that title: maybe only if you use the "eye" on a player, return the player rank ("majestyk (Master Squire)") instead of only the player name, or even make it somehow visible (with "badges" or something). Cheers, majestyk

Being "rich" is relative. IMO having a ti armor set, a steel armor set, a therm serp, a BOD, a BROD and a NMT qualifies for being rich, even if you only have 10gc in storage. This is maybe a bit exaggerated, but good fighters also have their riches. I'd rather not see my name on any "top" items/gc list, but I think that it is certainly helpful in adjusting the economy. Good work! And since we're at that topic: a while ago I thought about getting some skill related statistics: experience points gained per day/skill (I'd like to see the graph for a/d skills on sun tzu day), most frequented maps (maybe count map enter/leave), killed monsters/players, everything as totals/per time, maybe even a nice graph with total players online over a day (like network usage?). Some of that could also be interesting on per-player basis, that would make nice statistics, maybe in the future something like EA does for Battlefield2 (http://www.bf2s.com/ is a frontend for those stats, click a player in the top10 lists for examples). Anyway, that's far off from item stats, but I like to dream Cheers, maj

I think that most of the people never even thought about it Maybe put up a poll or something? This is a very minor change without any effect to gameplay at all, so maybe a client developer will consider changing it if enough people vote for it ...

You are absolutely correct. Right now, all the monsters have a default visibility. Soon, they will have a different visibility based on size and maybe color. I absolutely second that. Maybe it's even possible to take surroundings into account? This would make fluffies next to invisible on arctic maps at night times .. :-) On a different sidenote, does that also affect if the aggressive monsters see you? A cyclops would probably not have a high perception (being a brute, only having one eye etc), while feros seem quite capable hunters with their cat-like derivation ... Cheers, maj

I did a couple of pretty big projects with hyperbags, gathering 50k+ coal and iron ore to make bars. The problem with obvious places is that the obvious ones are the good reachable ones, so you always have to find a compromise between lazyness and risk. There even was once or twice the case that I was "sharing" my hyper with someone I did not know, we both dropping huge amounts of coal into it and withdrawing a couple of 10k's from time to time, and it worked because we both dropped more in than we took out. I met a few nice people at that time, and we all knew what was going on, but I never had any negative experience. I always left a key in the bag in case someone opened it by accident (because of coord mismatch or something), and I was never disappointed. People doing projects that large are high level alchemists, and they respect the work and effort of others, it seems

Most "commercial" games don't restrict themselves to in-game graphics or textures. For box covers, opening screens, even often during in-game cut scenes artwork with much better graphics is used than what is available using the game engine. Just the best is good enough to attract more players I also think that EL could use a nicer opening screen. Maybe a drawn image of an actual in-game map, or inspired by one (some c2 maps come to mind), along with some creatures/monsters/players?

That's exactly his point. If people were expecting the price of EFE to rise drastically, they would be all available EFEs on the market, even for 4k (which is not that unusual today). I guess people don't care that much, and I also don't think the price will drastically change. There are still a lot of people who buy EFEs at the shop and sell make them into in-game gc's.