Staredit Network

After a couple hundred downloads, I have realized how long it would take for EVERYONE to update their version unless I made a news post for every major version I make. This will perhaps be the last of the major version news posts but there is a newer and better way to get updates!

Inspired by Suicidal Insanity's SCMDraft2, I learned that VB had internet capabilities. I soon programmed an "AutoUpdater" that would help you get the latest version in seconds! This is a huge add-on to the protection and how fast people can get their map protected with the latest! If protection were cracked just yesterday, I could update uBeR@TiOn hours and release the next protection method in days!

This is not the only major thing that I am posting about. Another large component of programs is user input and suggestions. So I was going to make a sort of website about uBeR@TiOn and why I made it and the latest version and troubleshooting. I realized there isn't much to talk about so this website would be worthless. Instead, I deleted my old forum (died way back then) and created a small page that would allow people to make suggestions and report bugs (again inspired by SI). This page is simple no doubt but will have a perhaps huge effect.

Latest v1.0.0.5 uBeR@TiOn:
http://www.staredit.net/index.php?download=2596

Bug report and Suggestions page:
http://lgcyfrms.superihost.com/uberate.php

This is where I sign off and say, "Enjoy!"

Wow, cool. It's nice to see that you're still keeping up with this. Hopefully by the time my map is complete, this will have a new protection level. I'll be sure to use it regardless, but I do hope you come out with an update sometime in the next few weeks.

I want to keep the protection updates low because I that way I have some sort of fallback plan incase someone cracks it.

You know, most protections aren't hard to crack at all if you know what you're doing.

bye legacy!
I'm gonna get this

You know, releasing new versions every day isn't a good way to fight unprotection. The maps themselves that were protected with the old versions will be vulnerable. And nobody wants to be updating every single map every day.

U make a great change. Tho i cant download it. One day ill use it.

Moose, the only reason he's updating his is because ProEdit was updated.

Will ProEdit ever get a new protection level?

Actually, that's partly true. I want to make it so that PROEdit will never be able to open the maps protected by uBeR@TiOn but I doubt it will stay that way forever if Yoshi updates it a lot

When I say unable to be openned by PROEdit, I mean screws up PROEdit when you try to open it.

Moose knows how to do that. I helped him figure out how to crash the previous version of proedit. So you should drop him a line if you need to know how to do that.

(side note: I don't actually have this version and don't know if it does that so I apologize if it does).

Then just download it?

Of course it crashes the older versions of PROEdit and screws with the new one

I can't crash the newer version if PROEdit doesn't find the scenario.chk without a listfile.

Out of curiosity, why all the 0's? Why not something simple like 1.0.5

I believe the version umber system is like this:

Number I --- Primary Version Number
0 - Beta///Pre-beta
1 - Final Release
Add 1 to this number every time you completely change your production utterly

Number II --- Secondary Version Number
starts at 0
Add 1 to this number every time you make a substantial change but not complte change

Number III --- Update Number
Add 1 to this number every tiem you change anything


So like 1.8.11 would mean it was first version in final release, features were added chnaged or modified 8 times since 1.0.x and there were 11 fixes and mini-releases since 1.8.0

You know ... I never really knew that. I used a 1.(0-9) system where I would just count up for every change I made. So 1.2 would indicate 12 changes since the original.

It doesn't let me edit the number there:

v1.0.0.5
v1.0.^
That one

So I do

First number: same as you
Second number: Protection method change (huge program addon/change)
Third number: can't touch that
Fourth number: minor revisions

Actually, DT_BC is correct. Version numbers work by Major, Minor, Fixes.

Very cool! It's good that there's a new protection program out there that seems to be pretty robust. I didn't even know that there were guidelines for version numbers! And if I ever need map protection, looks like I'll be using uBeR@TiOn!

What would be excellent would be if ProEdit was update to support external plug-ins. That way, verified plug-ins would be added as buttons (caption of the program name) into ProEdit so that the protection would be all in one step.

uBeR@TiOn should save the files that it has protected on the disk drive, so that when it loads, it could check for maps (the ones that you previously protected) using old uBeR@TiOn versions, and automatically update them. That would be great, because then nobody would have to manually re-protect all of their maps with each version.

I think LW is saying the program won't let him edit 3rd digit? Or maybe i misunderstand.

Yeah ... what is he programming this in?

That is correct DT_BK, strangely I tried multiple times and it wouldn't work.

I'm using VB6 Enterprise Edition.

Enterprise Edition? Perhaps it is used by the program.

Maybe just use a different VB program?
It can't be so hard if a lot of other programs do it.

try writing a two digits number in the last section. I'm not sure how it works but two numbers might be the same in VB, or maybe that number was added when the windows NT core was made (VB6 is for windows98).