revi

I don't disagree with you about the gc coming in and (not) going out, but: 'legit players that sell a store' do NOT bring any gc in game that wasn't there before. Nor do harvesters, nor gc buyers/sellers. They just move the gc around. Gc comes in game through sales to NPC, monster drops and harvest events (and I think I have all the sources of gc there), and leaves (afaik) mainly through buys from NPC... (ignoring characters being abandoned/locked/item wiped). While we are at it: is there any hard information about the total amounts of gc coming in and going out of the game over say 24h or a week? Same question for the rare items

What's wrong with trustbot? And you have a budget for this project? Or do you expect the programmer, hoster and radu to give you this service for free? (And when you talk with the coder, I hope you can be a bit more precise in what you want, and how you see this work)

I have to agree with Entris and Vanyel on this. It won't take long for those fast-regeneration spots to be known, so: - lots of complaints, or - the spots won't be used, or - they get camped by the top PK'ers as their private resource Of course, combinations of the three options are possible Don't forget that on the minimap you can see other players, even when they are hidden in normal view (hidden != invisible ...)

Also, there are some very small enclosed PK areas (2-3 person size)... Nice way to load up fast on action points, especially at 1/min...

Best answer I can give: ask a moderator in game ("#help_me ..." will get one to answer you). And don't wait until the mods start asking questions

I'm not a mod, but could translate if needed (and the moderators agree, ofc.) Je ne suis pas un modérateur, mais je pourrais eventuellement traduire qq. phrases.

It would depend on how you could get the diseased state, and how rare the enriched health essence would be. It would be the first time a cure needs a rare ingredient (afaik). E.g. poisoning can mostly be avoided, and is rather easy to deal with (and cures are rather cheap and abundant: HE or antidote). If disease would for instance be a harvesting effect, with a cure requiring a rare essence, not so nice. If disease would be cumulative, well, the less said the better... Also, this could be rather hard on players low on the stat that gets hit (beginners, but also some builds and just after a reset). So I guess I'm not sure this would work out well in practice, seeing what tends to happen to rare items that see a sudden new use (take rostogol stones, for instance (and invance )).

There still seems 'something' able to spawn inside the house near 131,61/131,59. I can't see it at all this time, so no way to kill it. Does this mean there are tiles not marked as non-walkable inside the house area?

Because those counters are client-side only (as Sir_Odie said) and sometimes miss a kill. Server side counters are supposed correct (after all, you see the dead monster, so server noticed the kill...) and are used for the quests, and as client counter <= server counter, yours might not reach 30 when server says you are done.

For dangerous, there's the minimap, which shows any creatures near by (it stays visible in map mode); and for the hyper bags there's markers. I can also see how a #goto command would make macroing a lot easier, though...

Does trustbot work for bots? Then that could be a solution: mark the bot that has no gc/no slots/no emu repeatedly as untrustworthy, and after a while (to get enough votes) you can ask trustbot about the trade bot you want to deal with. Abuse is possible of course, but you can check who voted. Advantage is that the whole mechanism is in place, and works for all bots (if it works for bots at all). And no need for the bots to advertise their gc content. (Note: @ zombie: bots don't have to be stocked with gc by their owners; some can be used as outlets for the production of their owners => the gc comes from the customers, the owners skims off the profits...)

Just a note: there is NO NEED to enter any of these rooms to enter an instance, so any request to do so is a scam/luring in itself And the same scam has been tried on guildies of mine, so the perp likes repeat performances (and it seems to have worked at least once)...

Just FYI: the same is true now for OpenSuse (12.1), and probably also for Fedora (from what Google results I got). For me, adding "EXTRALIBS=lstdc++ lX11" in make.default/make.conf worked, there might be a better place to add these.

Not quite. Tanks are useful in a number of situations, where a group has to work together to kill monsters, like instances and invasions. I had the impression radu wanted to have more group work in EL, so tanks seem to have a place there. Remains the small problem of getting to be a good tank (build and levels)... EDIT: Just to be clear, with 'tank' I mean a build such that you are the one that's going to be attacked by the monster and that you can absorb or avoid most of the hits

Elaborate. Wtf is bad about it? It is 3 usd. You could have at least looked at the shop page... So you see a notice on your window telling you not to jump through it? I see I should have put in <irony> markers... And the final suggestion just that, a suggestion in case something should be changed (though I have no idea why anything should be changed) FWIW, I didn't say it's bad to take a nexus, some others here did

So as a new player you take one vegetal nexus to finish tutorial, later you hear that that's bad or you feel you need that PP elsewhere.. How expensive is a nexus transfer stone? Edit: I did the additions just now, after having done the rest earlier, so I don't know if the tutorial NPC says the two additions are optional. I didn't notice anything like that in the texts, so adding that in the NPC text might make it clearer that you're totally free to stop before you have to take the nexus

Well, if someone's grabbing all the spawns, I'd say there's no one else training in that area (you can't run after a monster if you're engaged in a fight, so the monster passed close enough to engage you). So starting multi-train shouldn't cause a problem. Unless we start reasoning like: "He's alone now, but someone else might come by in 5, 10, 60 min, so we can't allow multi training". I agree that later, when a second trainer comes by, releasing a monster should be automatic, no need for asking (but that's a nice theory...) Personally, I don't see a problem with multi-training when the trainer is alone in an area, or polite about it. Most pay for the possibility one way or another, and if not, more power to them. @Aislinn: if Orick was able to offer you a spawn when you arrived, he was clearly not training AFK... And yes, it is annoying if someone has grabbed all the spawns while he was alone, but then again, he was alone, so not hurting anyone (any players, at least). But if multi-training is to be made more difficult, would it be possible to use a modifier to the ignore calculation? One way could be with a multiplier for every opponent engaged: say a factor of 1.2, so if ignore is def-based, def 50 will count as 60 for ignoring, while you're fighting any monster, 72 while fighting 2 monsters etc. And the multiplier would take effect whenever you are fighting (so that rabbit that came by makes the yeti you're after ignore you). That way, ignore levels would stay the same, but multi training would be a lot more difficult, especially AFK multi (which seems to be the most objected to). Although this would not make multi completely impossible, depending on how it would be implemented, it would make it a lot riskier.

This is something new, as I've been playing for the past month with no problem. I'm not sure how to go about checking my firewall, and I assume I just call my provider to ask them- which I'll do at a more decent time- it's 1:30AM here. As I'm traveling home tomorrow, I guess I can eliminate one or the other if it works/still doesn't work... A classic check for this is trying to connect to the test server (port 2001/tcp) and doing a telnet to the game server on port 2000/tcp. If the first works, and the second doesn't, that would confirm a blocked port 2000, if both fail or both succeed, you have other problems (or in case of fail, 2001 could be blocked as well).

What might cause this is the gamma control in the EL client. At least under Linux, it changes the screen gamma: resulting in a brighter and less saturated image (loosely speaking). And as it is a global change that touches the whole screen, it also affects all other windows (that's why I keep it disabled: global changes like that plays hell with photo editing).

So we get even more complaints about some guilds luring players into PK areas...

<sarcasm>Then how about to strictly enforcing the subjects on @@6: invasion and Lenny. That sounds like the best way to reduce spam there </sarcasm> It used to be that the accepted way to publish death bags was 1 message in each of @1, @2, @4, with a repeat after 5-7 min. When @4 got abandoned in favour of @6, I'd expect the DB messages to follow. The idea being that you reach the owners through the most frequented channels open for general messages and help. If you're so concerned about spamming on @6, perhaps try and convince some of the more frequent posters to stick to decent talk (and not like yesterday evening, where Aislinn had to bang her fist on the table to shut up a group of 3-4 players, whom I won't name here; that was after warnings from other mods that were simply ignored)

Because your message is wrong: {[sit_down][3][0]} is three bytes, where it should be four bytes: {[protocol][length LSB][length MSB][parameter]}, as the length is a 16-bit (2-byte) value. You are missing the parameter ('0' or '1' in this case), so the server will take whatever comes in next (most likely a HEART_BEAT, value 14) => illegal => disconnect (or missing heart beat, as your messages are out of sync, but that also disconnects you) This page has some information. Be aware that not everything is there. Edit: according to that page, your sit-down message should have been: {[7][2][0][0]} : [7] : protocol code [2][0] : length (in order LSB,MSB): 1+datalength = 2 [0] : data (bool, so 0 or 1) and all I can suggest is: read those pages, including the coding examples. And for details/up-to-date information about the protocols used, study the client code. It's the only official documentation available (afaik)

At least 2 possibilities : either there's an error in your message format, or you are sending too many messages too fast. You might get better answers if you post relevant and current code... I for one don't want to look through all of a 5 year old program to answer a question about new code :/ Also, in order to see how the protocols work, you could just copy all messages you receive from the server to a file, and I mean the full server data as a byte stream, not just the text messages. The basic format used by the server and client is the same. To see the meaning of the protocol codes (the 1st byte of a message) have a look at 'client_serv.h' in the EL client code, this also gives you the different colour codes, and lots more.

There are rules for bots (and their code) already: here... As for the official server collecting bot data: bots have always been a player activity, why should the official server want to deal with that? Also, how would you assure that the data is reliable, and won't be used to try and gain illegal access to the server? (not saying it can be done that way, but why should the official server take the risk?). And that's assuming the bot owners provide data in the correct format (which is already not easy between professionals, btw). We'll not dwell on that such a system would require yet another scraping of the bot servers every so often (Learner said something about 15 min intervals). So you propose putting an extra charge on ALL servers concerned for ... (yeah, for what exactly?)

Are you sure it's the finger bones bending the wrong way? For me, it looks like the back of the hand is deformed in world, as if it's at least twice as thick as it should be. If you follow the line along the palm to the pinkie, it looks ok (that is the under/inner side of the hand, at the lower edge of the hand in the image)