If you were logged in you would gain 3 XP for posting a reply.
You are replying to:
I very much prefer the "Projects" portion as opposed to individual maps, unless you can easily "attach" older revisions of a map to a new revision.
Say for example, I update my TD. Now, there are about 5 revisions on nibbits that are of "release" quality, and when I update I attach it to my project, and if someone hovers over the old version they are notified by the little red banner saying X is the newest version.
Now, for example, if I say "X is the new version" and I upload that, (which I will be soon, actually) how will someone easily know that 1.00 is the newest, and that .30b is older (without noticing the version number) and more importantly, how will they be informed if such an update even exists? Also, will past revisions appear in a list as they do now with projects? I'm a huge fan of seeing past revisions on project pages.
I very much prefer the "Projects" portion as opposed to individual maps, unless you can easily "attach" older revisions of a map to a new revision.
Say for example, I update my TD. Now, there are about 5 revisions on nibbits that are of "release" quality, and when I update I attach it to my project, and if someone hovers over the old version they are notified by the little red banner saying X is the newest version.
Now, for example, if I say "X is the new version" and I upload that, (which I will be soon, actually) how will someone easily know that 1.00 is the newest, and that .30b is older (without noticing the version number) and more importantly, how will they be informed if such an update even exists? Also, will past revisions appear in a list as they do now with projects? I'm a huge fan of seeing past revisions on project pages.