![]() Notification Timeliness - We want to show notifications only when necessary, and hide them when they’re not needed anymore.(Bonus question: How can you stop harvesting without displaying the “You stopped harvesting” message? It’s a tricky one… if you’re not sure, try harvesting some Seridium until you run out of Matter Essences.) Our initial program tagged harvest completion, but that was all. Event Notification - We want to see a message when something happens in Eternal Lands.But first, a general overview of what we want, and why our last plugin is no longer sufficient: We’ll discuss some alternative approaches. In light of that, this section will take it slow and explain why we chose to do things the way we did. Most of the problems in our last notifier stemmed from hastiness. The EL team has volunteered their time and creativity for your benefit, and I won’t have my code used to cause trouble for them. Finally, you cannot modify the thread priority of the event handler. ![]() You cannot inject events, nor can you delay sending them between the client and server. Basically, it prohibits you from using this code to automate, or to modify it in any way that causes undue strain on the servers. This license is not for my benefit, but for the benefit of the EL servers and admins. Scroll to the bottom of the post to read it. While I normally provide all code in the public domain, I am restricting this post’s code with a license. Don’t slow down the client or the server. Make it operate external to the Eternal Lands program. (What if the developer released the next version in Haskell or Forth? What if he closed the client source for the next release? What if -and this is the most likely- we don’t want to make our notifier any fancier using Win32 C++?) We need a new solution, and that means it’s time to pull out the big guns. It was also heavily coupled with the client program’s source, which might not be such a good idea. □īack-story: Our previous notifier was pretty hackneyed. Quick Note: I’m still trying to fix some of the formatting, but the content’s all here, so I decided just to post it. If you can follow along, you’ll know more than enough to continue on your own from here. Fortunately, I managed to get its basic functionality all done by press time. Blog Info: I finally did it: I took on a task that was too big for me to finish.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |