(App) Instanced Boss Timer

Update: Timers no longer reset when changing continents. (Sept. 23 2011)

A simple boss timer designed for instanced bosses, optimized for minimal memory usage.



Get it here.

Oh, that seems pretty cool =o gonna give it a shot~

Looks like it works fine xP though the timers stop if you switch to a different category.
Though you could just open multiple windows of it for each of the categories you need I guess xP

=o I like how the color of the numbers change when it gets close to ending xP

No source code? I'd be curious to know what you used. Must be a native app to be using under 1 MB. Maybe not even a GUI library, just raw win32?

No source code? I'd be curious to know what you used. Must be a native app to be using under 1 MB. Maybe not even a GUI library, just raw win32?

And lo' notepad reveals the cluelessness of this assumption;

System.Resources.Tools.StronglyTypedResourceBuilder 4.0.0.0
Microsoft.VisualStudio.Editors.SettingsDesigner.SettingsSingleFileGenerator 10.0.0.0
Powered by SmartAssembly 6.2.2.215

Now I'm really curious. A console Hello World uses 2 MB and an empty winforms application uses 2 MB before the window appears and 4 MB after. NGen or something?

Oh, that seems pretty cool =o gonna give it a shot~
though the timers stop if you switch to a different category.

Changed so the timers don't reset.

No source code? I'd be curious to know what you used. Must be a native app to be using under 1 MB. Maybe not even a GUI library, just raw win32?

It only uses that little if the timers aren't activated.

And lo' notepad reveals the cluelessness of this assumption;

System.Resources.Tools.StronglyTypedResourceBuilder 4.0.0.0
Microsoft.VisualStudio.Editors.SettingsDesigner.SettingsSingleFileGenerator 10.0.0.0
Powered by SmartAssembly 6.2.2.215

I think I fixed the flaw.

Eos made me facepalm myself for underestimating him.
Seriously. A text editor?

Throwing it Reflector or IDA seemed like a waste when exposed strings are easy enough to read with notepad
Especially since the point was anyone could've done it to answer Spaz's question.

It shouldn't be readable anymore in notepad, hopefully.

It shouldn't be readable anymore in notepad, hopefully.

NotePad; The Great Revealer:

 Spoiler

It's not a secret that I encrypt and obfuscate my files.
I don't see how the information currently revealed is going to be an issue, as its the same with most other .net applications.

Neither was the info previously revealed. The point is obfuscation is a waste of time and resources because if I really cared I'd be able to take it apart with very little effort, as demonstrated by even notepad being sufficient to show every literal in the app.

Well, i'm completely inexperienced and ignorant of your coding knowledge.
You should already know that the main function (countdown timer), consists of only a few lines of code.

Anyways, i'm just a noob passing by who just happened to help the community.

Well, i'm completely inexperienced and ignorant of your coding knowledge.
You should already know that the main function (countdown timer), consists of only a few lines of code.

Anyways, i'm just a noob passing by who just happened to help the community.

I don't know why you'd go to the trouble of encrypting and obfuscating the assembly of such a simple program, unless you were trying to hide something.

Edit: Also for the record, the SupressIldasm attribute you applied is pointless. Anyone who knows how to use Ildasm knows how to remove that attribute from the assembly.

I don't know why you'd go to the trouble of encrypting and obfuscating the assembly of such a simple program, unless you were trying to hide something.

Edit: Also for the record, the SupressIldasm attribute you applied is pointless. Anyone who knows how to use Ildasm knows how to remove that attribute from the assembly.

If there was anything to hide the eye of eos would have saw it and crucified him in an announcement titled "AN EXAMPLE".

If there was anything to hide the eye of eos would have saw it and crucified him in an announcement titled "AN EXAMPLE".

because if I really cared I'd be able to take it apart with very little effort

Meaning he doesn't care, and probably didn't bother looking through it.


I'm just saying, I don't see why he would need to specifically code a check to see whether the app was running in FullTrust mode. You shouldn't need FullTrust to run a simple timer app. I don't see why he's calling CallWindowProcW and GetModuleHandle from kernel32.dll/user32.dll either. Or why he has a reference to WebServices, and serializes data.

Edit: Seriously? An infraction for informing the public about being safe about executables? REALLY?

Posting this here, because this is where it should have been, not my PM box.

I don't know why you'd go to the trouble of encrypting and obfuscating the assembly of such a simple program, unless you were trying to hide something.

Edit: Also for the record, the SupressIldasm attribute you applied is pointless. Anyone who knows how to use Ildasm knows how to remove that attribute from the assembly.

To answer your question: I had my source code stolen and released publicly in the past.

"I don't know why you'd go to the trouble of taking apart the assembly of such a simple program, unless you were trying to steal my code." Is the only conclusion I can draw from you know about Ildasm supression and the encryption.

Maybe i'm just overly paranoid, but everytime I complete an application, I always need to find more ways to deter those who seek to steal my work, no matter how badly done it is.

Or maybe it's because a ton of people have been getting hacked in maplestory recently? Why would I want to steal the code of something I could write in 5 minutes if I cared enough to?

Judging by the references and abnormal ways you're doing things in the code, combined with your obfuscation, it looks very sketchy.

It's ok, I don't believe a word of that junk about the server check hackings.

Still, I believe reports of account hackings have surfaced long before I released anything, so your point is invalid.

You should already know that obfuscating a program is only a few mouseclicks away, and noobs like me just click that magic button and hope everything goes fine, ignorant of how exactly the program does its protection.
Take the SuppressIldasm. It's some sort of default, unable to be disabled, option thats apparently built in to the obfuscator.

Everyone does things differently, and just because i'm bad at coding dosen't mean that you need to rip it apart to confirm to yourself that there's nothing wrong with it. Have you considered the fact that the code looks bad and confusing because I am a bad coder? You should know there's more than one way to do things.

I think you're misunderstanding my point. I too do not agree that people are actually *hacking* others. It is the people who download programs such as yours without checking for sure that they are not malicious.

Your program may very well be safe, but the burden of proof is on YOU, the person releasing the program, to show that it is not malicious. Not the general public. Purposely obfuscating your IL code is the wrong step to take in relieving that burden, and that is what I was pointing out.