D. V. Devnull

Catching up... Uhm... my kill count here wouldn't be quite THAT big. Maybe a third of that, but only as a "frag count", as everyone blasted and such has respawned, and many of those are more than likely duplicates on the same person. :-k I gotta second what @Arceus said there. I can't let evil win either. :thumbsup: Eh... Just gotta make sure you don't refresh too fast. :lol: Number? 23715 ~D. V. "I think I'm all caught up now?" Devnull

646 Ah. <*is not confused now*> :thumbsup: ~D. V. "Yay!" Devnull

890 ~D. V. Devnull

AHEM. I believe I called that number already. 23,720. And I couldn't have seen this post, as the forum software didn't alert me while I was editing. #-o 23719 ~D. V. "Argh!" Devnull (p.s.: I guess this is what we get when people post too fast on top of each other?)

I'll catch up with this thread later... 23721 ~D. V. "Fresh out of time..." Devnull

You [bleep]! :angry: <*shoves @Gandalf14141 in a large trunk, then closes and locks it*> There! Now the count shall rise! :thumbsup: 886 ~D. V. "To upbound numbers, and success!" Devnull

Hmm... That's understandable. I don't like to sacrifice security, provided that can be avoided, as well. :-k There's got to be some way, however, to dodge making people have to "Run As Admin" as many times as there have been? Doing so creates an even larger dangerous exploit, as the program scope and permissions (at least as I understand them from having been a WinXP user for some time) become unconfined from the User Account that it's running on. :? Could you (or someone else in the SwiftKit team) perhaps design a system service program that only your application could connect with, would only run while your application is up, but could handle the updating work? Maybe then like Valve's Steam client (which kind of gave me this idea, but I'm thinking a little less aggressively), then the critical part that hits all these errors might be able to do its' job, but without having to open up the main program in Admin mode. :huh: ~D. V. "Trying to think of a way to help end the problem..." Devnull

644 :?: :huh: ~D. V. "confused" Devnull

I might be able to suggest a workaround for their issue, even though it's a bit off-the-wall. They'll just have to re-permission the directory that SwiftKit is installed in with... SYSTEM - Full Control Administrators - Full Control Everyone - Full Control ...make sure it trickles into all the subdirectories/files of that directory area only, and that should give SwiftKit a fair chance to either update or spit back a Debug Information file. Which brings me to ask, why don't you just preset permissions similar to these when the program is first installed? :( ~D. V. "seeing one too many of this type of thread created" Devnull

884 ~D. V. Devnull

642 Don't worry, I come back on Mondays, provided nothing goofy happens. :) I guess an even better question would be, "What do I do if all the rest of you disappear, and I became the last Forum Games player?" :ohnoes: ~D. V. "Another reason we have to grow the population here..." Devnull

23727 Eh, basically what will happen is that if someone gets killed, or someone/something starts to murder them, the respawner unit triggers if in range to do so. Usually, it can work up to 200 feet away, but I find it works best within 50 feet of the target. (The closer, the better, maximum effect reached once within 20 feet. And it has to be within 25 feet anyway if I've totally blasted them to ashes.) Anyway, their body will be teleported out, healed, and jump-started back to life within a mere microsecond. Obviously, their ghost ends up sticking with the body due to how fast the revival occurs, and the fact that the respawner unit quickly locks onto the person's natural frequency and attracts them to the respawning point. (If blasted to ashes, their DNA is reconstructed into a full body at current age. As previously happened however, if the respawner is called at a delay after the incident, then it can take a bit longer to completely do its' job, because it's much harder to keep a person's ghost close enough to complete the reviving respawn.) :geek: Just for reference, I don't think there were any respawners around here before I first arrived in the Forum Games area. Good thing I brought my own self-maintaining complement of them. I'm just not a naturally murderous person. Could you imagine the kill count I could have left in my wake? :-k ~Mr. D. V. "Now THAT would have been [bleep] embarrassing!" Devnull

Yeah, weekends have a way of keeping me from getting over here. Family's all home, and getting a chance to get online kind of goes out the window. :-k 640 ~D. V. "Simply, crazy just ensues." Devnull

880 ~D. V. Devnull

Off by 20, huh? Dangit. #-o <*Mr. DVD reluctantly drops a large, opaque, yellow-colored blob on @Star., and within moments it covers her entire body. Unfortunately, no sound is coming out, and nobody can see inside.*> I have no idea what's going to happen in there. I don't even know if that thing will ever move off of her. Heck, rumor exists that these things maintain an oxygen bubble for somebody to breathe within, but I have no idea of the truth of those claims. :( <*Mr. DVD reaches up in front of his self, and his hands move as if he's tapping on a virtual display in front of him. A moment later, a respawner unit floats into the room, and sits approximately 20 feet from @Star.'s position.*> Anything morbidly awful happens to her, that unit will take care of the ensuing issues. :geek: Now, where were we? Right... 23729 ~D. V. "Too many questions..." Devnull

876 ~D. V. Devnull

638 Hasn't "B.C."s blonde guy already taken enough hits to the nose? :arrow: http://www.gocomics.com/bc/2015/05/03 ~D. V. "Masochism's now on the table?" Devnull

636 ~D. V. Devnull

23751 ~D. V. Devnull

872 ~D. V. Devnull

634 ~D. V. Devnull

23753 ~D. V. Devnull

860 ~D. V. Devnull

632 ~D. V. Devnull

23755 ~D. V. Devnull