Placid Report post Posted January 15, 2007 The Wiki has come a long way. Some restructuring has taken place to remove non-essential information from the protocol description article (EL Network Protocol). We now have a complete list of Item Image IDs (thanks to Entropy & Learner) and the official client's colour codes has also been provided. The Actor related data has been split to its own page to shrink the main article slightly. You can view these pages here: EL Network Protocol EL Item Image IDs EL Actor Data EL Colour Codes Thanks to all those who have contributed, hope it helps those who are new to EL's protocol! Share this post Link to post Share on other sites
bkc56 Report post Posted May 16, 2007 Do we know when the EL Item Image IDs page will be updated for the 5/07 release? I'm hoping to have our sales bots updated with some of the new items the day it goes to the main server. Thanks. Share this post Link to post Share on other sites
Placid Report post Posted May 18, 2007 Do we know when the EL Item Image IDs page will be updated for the 5/07 release? I'm hoping to have our sales bots updated with some of the new items the day it goes to the main server. Thanks. I'll see what I can do. Share this post Link to post Share on other sites
coch Report post Posted June 17, 2007 I'm working on a client app for a bot. I've registered to the wiki and I'll try to add some info about the protocol when I figure them out. Share this post Link to post Share on other sites
Placid Report post Posted June 18, 2007 I'm working on a client app for a bot. I've registered to the wiki and I'll try to add some info about the protocol when I figure them out. Great, thanks. We're in need of server to client messages so if you're able to do this i'd be grateful. I've also updated the Item Image IDs article to reflect the new items. Cheers! Share this post Link to post Share on other sites
nicky Report post Posted August 21, 2007 Placid, you rock! thanks for the Item ID's, that site is extremely useful! Share this post Link to post Share on other sites
Placid Report post Posted August 29, 2007 Placid, you rock! thanks for the Item ID's, that site is extremely useful! Glad it could help. Bear in mind it was not just me who wrote the documentation I have recently moved servers, so please update your bookmarks to point to the following hostname: - wiki.beplacid.net/ The base of any Wiki URL will now be: - wiki.beplacid.net/articles/ So please ensure you have the correct hostname and URI (including '/articles/')! Cheers, Placid Share this post Link to post Share on other sites
Torg Report post Posted August 30, 2007 I have recently moved servers, so please update your bookmarks to point to the following hostname:<snip> So please ensure you have the correct hostname and URI (including '/articles/')! Bookmarks and links like your sig?? ;-) Share this post Link to post Share on other sites
Placid Report post Posted August 30, 2007 I have recently moved servers, so please update your bookmarks to point to the following hostname:<snip> So please ensure you have the correct hostname and URI (including '/articles/')! Bookmarks and links like your sig?? ;-) ROFL Thanks Share this post Link to post Share on other sites
nathanstenzel Report post Posted October 17, 2007 I hope you don't mind. I just registered and submitted something for the python code section. The trick is, I have made some references to some things in my code implementations. It gives a good tip and a rough idea though. The tip is struct.unpack('=HIBB') will not distort the data while struct.unpack('HIBB') will. Feel free to do what you will with the entry. I hope it helps some. The struct.unpack command can be a pain without the '='. Share this post Link to post Share on other sites
Grum Report post Posted October 17, 2007 The tip is struct.unpack('=HIBB') will not distort the data while struct.unpack('HIBB') will. Ah, I never knew about the '=' character. Nice to learn something new. I think you should use '<' instead, however, since the EL protocol is strictly Little-Endian. Share this post Link to post Share on other sites
Placid Report post Posted October 17, 2007 I hope you don't mind. I just registered and submitted something for the python code section. The trick is, I have made some references to some things in my code implementations. It gives a good tip and a rough idea though. The tip is struct.unpack('=HIBB') will not distort the data while struct.unpack('HIBB') will. Feel free to do what you will with the entry. I hope it helps some. The struct.unpack command can be a pain without the '='. Not at all, all contributions are welcome! Thanks! In code I've written for the EL protocol, the '<' char was used in the pack/unpack calls. As Grum said, the protocol is specifically little-endian. Cheers! Share this post Link to post Share on other sites
nathanstenzel Report post Posted October 17, 2007 (edited) Ah. Well, use < then. Without it, the darn thing will try to pad stuff to the largest size and it will mess it up. The < vs = difference is that = will be whatever endian case it is for the computer running it.....which for some systems won't be little endian. BTW, I modified my post to the protocol code example. Edited October 17, 2007 by nathanstenzel Share this post Link to post Share on other sites
nathanstenzel Report post Posted November 9, 2007 I compared what you wrote in the table to what the EL code was for looking at an item in a bag and looked at the change logs for that code. You had [position][quantity] instead of just [position]. I fixed it for you. Share this post Link to post Share on other sites
nathanstenzel Report post Posted August 2, 2011 Let it be known that I looked for the wiki.beplacid.net page today and it no longer exists. It is now one of those stupid sites with bullcrap links on them. Does anyone else have a valid list of info on the protocol? Share this post Link to post Share on other sites
revi Report post Posted August 2, 2011 Let it be known that I looked for the wiki.beplacid.net page today and it no longer exists. It is now one of those stupid sites with bullcrap links on them. Does anyone else have a valid list of info on the protocol? In a way it is a good thing that that page disappeared, as it was hopelessly outdated. If I need to know about a protocol, I tend to look in the client source code (there at least, I know I have an implementation that works). Also (IF I understood the license correctly), it might be possible to re-use parts of the client code in your bot (but check this to be sure). Using at least 'client_serv.h' will save you a lot of typing Share this post Link to post Share on other sites
Alberich Report post Posted August 2, 2011 This looks like a mirror of the old page. Share this post Link to post Share on other sites
nathanstenzel Report post Posted August 5, 2011 This looks like a mirror of the old page. Thanks much for the link, Alberich. Share this post Link to post Share on other sites
themuntdregger Report post Posted December 24, 2011 Added some content to the code examples based on php. Nope its not the sexiest language, but its simple, easy to understand and virtually self-documenting. Unlike other languages, you can run it from a web account, hence, its got some fairly 'interesting' possibilities, particularly if you use one of the less restricted free hosts. However, it can also be run from the command line, as either a foreground or background process, so its fairly handy as a general programming language, not mention ideal for writing bots ofc. Share this post Link to post Share on other sites
SolarStar Report post Posted April 29, 2015 Let it be known that I looked for the wiki.beplacid.net page today and it no longer exists. It is now one of those stupid sites with bullcrap links on them. Does anyone else have a valid list of info on the protocol? http://www.thefullwiki.org/Eternal_Lands http://wiki.alexcollins.org/articles/Eternal_Lands_Network_Protocol Share this post Link to post Share on other sites
squiz Report post Posted February 24, 2021 None of these sites seem to exist any more. Share this post Link to post Share on other sites
bluap Report post Posted February 25, 2021 (edited) I copied the pages a long time ago but never clean them up. Might help though: https://twinmoons.org.uk/el/protocol/ There's a version here too: https://web.archive.org/web/20130826072014/http://wiki.alexcollins.org/articles/Eternal_Lands_Network_Protocol https://web.archive.org/web/20170705064831/http://www.thefullwiki.org/Eternal_Lands Edited February 25, 2021 by bluap Share this post Link to post Share on other sites
Nogrod Report post Posted February 25, 2021 2 hours ago, bluap said: I copied the pages a long time ago but never clean them up. Might help though: https://twinmoons.org.uk/el/protocol/ There's a version here too: https://web.archive.org/web/20130826072014/http://wiki.alexcollins.org/articles/Eternal_Lands_Network_Protocol https://web.archive.org/web/20170705064831/http://www.thefullwiki.org/Eternal_Lands This would have been useful when fixing my bot code but I assumed it was long gone. I guess all I had to do was ask. Thank you bluap. This will definitely help going foward. Share this post Link to post Share on other sites
bluap Report post Posted February 26, 2021 I wonder if its worth turning this information into markdown and adding it to the client source code? Share this post Link to post Share on other sites
Nogrod Report post Posted February 28, 2021 On 2/26/2021 at 1:34 PM, bluap said: I wonder if its worth turning this information into markdown and adding it to the client source code? If it's not a lot of work and brings programming talent to support the game I say sure. I looked to the client source code as the best reference to figure out how things work so having this there seems like a good fit to me. Share this post Link to post Share on other sites