The only thing you need to set as a global variable is %nc.status.on, since it is used in different aliases and commands. All the other variables should be set as local variables using the var command, as to not bulk up users' variables file unnecessarily.
Major setback, had to do a Windows re-install (bleh), and then have been having personal issues around the home. I promise I'll get back on this at some point, when my motivation has returned more.
Used to operate a sorter system with a computer using Win2000 Server. Worked great. Easy interface, of course, and uptime never caused an issue. They did a yearly purge and reset just to be sure, and that was about it.
"$30 for JUST THAT!? Man, at that rate, you may as well think you're missing some zeros there, Movie Company. In fact, I think you're missing some zeros, too. As in, $00 HELLO TORRENT!"
I don't actually torrent, that is just how I imagine torrenters going about their business.
Sounds like how I had to strip DRM from some songs by giving it a go through Audacity to be able to burn them to CD. I bought the songs from Amazon, digital copies of course, and wanted to make my own physical copy of it. TRY TO STOP ME, WILL YOU!? *loads up Audacity*
Yeah, I noticed the diagonal movement. Seems like bullets travel a little faster in those directions, too. I'll just have to do something to compensate and even it all out.
I did the herding, also, running an octagon-like pattern around the edge then pulling off to one corner of the map and firing like mad.
Think about it though, it's kinda like having a square and running a diagonal line through the square. The square is 3 inches on all side. When you travel in a cardinal direction, you're traveling 3 inches to the next point. But when you travel the diagonal, you're actually traveling about 4.24 inches from one point to the next. Ah, back to basic geometry, but this is the same principle showing up in the game.
Well, since I usually run on Guest, and the old lady's got the admin access (her computer, seemed fair enough though I PAID FOR IT lol), thought I couldn't get this going.
Remembered I had a clean-slate version of mIRC 7.17 on a thumb drive. Works great :D
Invincibility Pickup (not only gives you invincibility for a short time, but zombie attacks HEAL you while invincible. Rare pickup.)
Pickups now flash when they are about to disappear.
Slight modification to the rarity of a machinegun pickup. When I played my full round, after building up over 2500 bullets for the machinegun and not being able to get rid of them faster than I could find them, I figured I should balance this out. I may also implement a maximum ammo capacity.
Working on:
Hit "zones." Instead of checking every bullet against every zombie to see if there's a hit, the bullet will now only check zombies within the "zone" it is in. I'm working out the bugs on zombies standing on a borderline between two zones, where a hit doesn't register, and the lag induced by having many zombies onscreen with this setup. However, bullet updates don't seem to affect performance so much now :D
@Kiddo96: After making my previous comment here, I decided to have a play.
I playtested this quite a bit, but I used a lot of hash table manipulation and whatnot to shortcut myself to possible scenarios, and otherwise just played through maybe 250 zombies in a semi-legitimate game. I had never, EVER sat down for a serious session, where I just started it, left the script and hashtable alone, and just tried to honestly see how far I could SERIOUSLY go, rather than just testing for a while and giving up.
Results:
Got a bit bored after a while because I have other things on my mind, and stopped picking up health. Otherwise, who knows how far I would have gone :P
Thanks everyone for the likes so far, and for getting 250 views on this page. I am working on an update to provide more things, but I've been distracted by a lot of other things right now, so I don't currently have as much time as I would like to dedicate to this. I'm sorry for the delay.
Eye-candy suggestion: For the mode where it just shows hours and minutes, have the colon separating them alternate between lit and unlit states, like a watch does.
As for one-upping with the scrollbars, I just did that because I figured it would be a bit easier for the average user to pick up and use. Slide it, and see the result immediately, rather than having to type numbers in to fine-tweak lol. Good knowledge on the did -c :D +1 for that.
Very nicely done. Doing the numbers in-script rather than having to grab more files makes this much more user-friendly, very grab-n-go.
As for the colors, here's my take. It's nowhere near perfect, I'm still tinkering with it. Also I can figure out how to give a scrollbar a value when initializing a dialog... so it's bugged in a way. But works? I dunno.
Code
Use /clockcolors to open the color selection script. The three bars adjust the RGB values of the lit "LEDs," as you move them. There are 32 intensities for each colours channel.
Like I said, my work on custom colors needs (quite a bit) of work. You can either stem off of what I have so far here, or well use your imagination! Having customization is a love of mine, and I would like to see this script have more options in the future. ^_^
Couldn't you just specify w and h in the drawpic command, or use the -s switch, to adjust the picture to the size you need? Of course, looks sloppy when making the pictures bigger, and probably is more costly on resources than just doing a manual resize of the source images yourself before using....
Also... why didn't any of us think to use -c in the drawpic? Probably wouldn't make too much of a difference with the way it runs anyway, but you may as well cache them since you'll be reusing them again and again until the clock is closed.
Also, @pball: Analog clock has already been done by BlueThen, years ago lol. It was the script that I used for reference to learn how to draw lines in any specific angle ^_^
Also, maybe someone could include elements of my Higher-Resolution Timestamp snippet to give the time which includes hundredths of a second, for those who really need to know the EXACT TIME lol. Wonder how laggy it would be?
Having a side listbox with all the notes that are saved shown in there for viewing/editing/deleting would indeed be a good idea, Firstmate. Maybe it's on the to-do list already?
@pball: Ah, okay! Will there be other things like editing entries in the future?
Gotcha gotcha. Been so long since I played with a window in Listbox mode :|
Why not limit the length of a single input, then? I'm sure there are some people who would try to enter in a decent length of text, and will be mad that they have to adjust the window size to see it. They'd be even more mad if for some reason they couldn't figure out that you can adjust the window size to see more text. I do understand the purpose of this is for short little notes, but sometimes people can't trim what they want in one entry down enough to fit the constraints.
And on the note of interacting with notes.... what interaction is built in so far? Because I can't find any... :( is there some feature I'm missing here?
@blacvenomm666: If you would like to replace your original submission with the one I posted in the comments above, go ahead. It's still pretty much your code, just with a lot of redactions that I made. The modifications I made in some areas wouldn't account for much, so it's still within guidelines.
Yeah after playing with it a bit more I realized the format. As for dialogs, just saying it was my taste, @Windows server your purpose just as well don't they? :D
As for the line length, take a look at using the -p switch on your aline command under note entry. This would force it to wrap if it's too long. Otherwise unless I broke everything up manually, it'll be a mess if I do a decent ramble in one entry. When writing what's in the @Window to the save file (or INI when updated), even though one entry is split up amongst two or more lines, mIRC will remember that it's all one line and enter it as such to the file.
Code
Copy that and paste it in your mIRC's editbox. You can see that even with word-wrapping, mIRC still reports there are only 2 lines there.
[Note_1]
title=This is my First Note!
body=And this is the Note I left myself.
??
Unless you're going to have multiple items in a section (like this), INI wouldn't do much good. Of course, title and body are just the beginning... you could have a lot of other settings for a particular note saved in the same section, if you can think more stuff up.
A different way to do things would be to have a dialog with an editbox, a text box, and a list. The list is filled with all currently saved notes' titles, and when you double-click one it opens it up in the textbox (and in the editbox for editing). Of course, there would be a save function on it as well. I myself don't see the @Window being the best form of presentation of your system, but that's just my tastes.
Neo--: Yes, but there's a little more to it than that. The window would have to be resized, or the 12-hour window closed and a 24-hour window opened. If one is using the 24-hour time format, we don't need the AM/PM appended to the end so we could lose the space it takes up.
There is an easy way to condense this, which I saw right off the bat. It could probably be extended further.
Code
This works, while reducing the linecount from 166 to 41.
All the slashes prefixing the commands aren't needed. mIRC is usually pretty smart about determining what are commands. For commands prefixed with a period to silence them, you don't even need a slash there. Just use .timer. For the command run.clock.long and run.clock.short, it is not necessary to put a period in front of the command since they aren't returning any output that will be echoed somewhere.
Use "0" for the number of iterations in the master timer. Otherwise, after 9000 seconds, the clock will stop working. 0 will make it keep going and going until it is stopped (which is already covered under run.clock.short where you did the $dialog() check). I can imagine some people who always leave their computer on and mIRC connected may leave this dialog up all the time as well, and having it fail out after 2 1/2 hours because the timer's iterations were done would be considered "broken" to them.
Also, you should include instructions on where to unzip to. I myself just changed everything to $scriptdir\Clock\<stuff>.jpg and put the folder in where the script is saved.
I changed the $time(tt) part to have the if check only to the A or P of AM/PM, and the M gets done on it's own. It's going to be there either way, so you may as well cut out a little bloat script there. I also changed the first number in hh to do an $iif() check to see if it's greater than 0. If it isn't, then it uses blank.jpg. A lot of common alarm clocks do not light up that group of LEDs at all if there is no number, since the 0 isn't really necessary to show. May also make some people misconstrue it as being in 24-hour format (where the 0 IS appended).
One more thing... a suggestion really... offer the ability to either have this in 12-hour format, or in 24-hour format. :)
Are you sure you want to unfollow this person?
Are you sure you want to delete this?
Click "Unsubscribe" to stop receiving notices pertaining to this post.
Click "Subscribe" to resume notices pertaining to this post.