A library that sets client.view to x*2+1 (6x6 = 13x6), sets a mob to watch, then displays that mobs client.eye in the newly added area on your screen. Of course this would only work with small view sizes, but I can think of plenty of uses for it.
A fully-featured save code, basing ideas off Deadron's CharacterHandling, but adding client.screen menus, as well as automatic name checking (to make sure you don't have the same name as somebody else).
A library people can use to make dragable windows on the map screen. Preferribly drag by pixel, although that would be VERY hard, so tile dragging would be good. This could be used for HUDs, popups, and much more.
A small library one could use to click and select/deselect objects and/or mobs (depending on how the proc is called, or a variable is set), and then easily manipulate those mobiles through the list. Preferribly with built-in procs to deselect all mobiles, select mobiles in view, etc.
Hopefully this gives some of you seeking a challenge, just that, a challenge. I look foward to seeing input on this subject, as well as even seeing the libraries in the future.
~Polatrite~
ID:153893
 Nov 7 2002, 1:50 pm
|
|
Good ol' bump action. (ol' being the key word here)
These are some old, but valid ideas if you're looking for something to do, but lack the creativity. ~Pola~ | |
I'm willing to pay for that bad boy if you've got it on the block for sale. I currently only have dimes, but I should be setting up some paypal action in a bit.
~Pola~ | |
I don't sell source code. As many BYONDers know, I don't like to give it away either (though I'd rather give it away than sell it). That demo is quite simple. If you have AIM, then you could page me or e-mail me your screenname and we can have cyb- erm, talk about the code <=)
Edit: I found your screenname in a forum search. Either you have a new screenname or you aren't online at the moment, or you have me blocked for some strange reason =P | |
I started making such a thing for an RTS style engine but decided to wait until right click was a useable proc (and not purely for menus). It would also be useful to be able to have either DblClick or Click called at one time. Currently I believe both are called (it doesn't wait to see if there will be a second click before calling Click) or at least that's the way I remember it working. You can get arround it with some delayed checks but it's a bit messy.
I would really like to see someone make a draggable window based upon pixels but I'm not sure how much lag that would cause.