Views: 1,002,974,422
13 users online:  Alex, alviiiN, Cal-of-Gearva, CircleFriendo, ElectroWellyGames, Fox899, Heraga, jorge144p, Maw, MORC, rachmaninov, Ringo, UTF - Guests: 96 - Bots: 302 Users: 54,821 (2,030 active)
Tip: Check this thread for a list of SMW sound effects.
Not logged in.
Universal Auto Patcher v0.1 by double_pmcl
Forum Index - Valley of Bowser - Moderation Questions - Tools - Universal Auto Patcher v0.1 by double_pmcl
Pages: « 1 » Link
File Name: Universal Auto Patcher v0.1
Submitted: by double_pmcl
Authors: double_pmcl
Operating System: Windows
Platforms: SNES
Games: SMW
Source Included: Yes
Featured: No
Website: Link
Description: With this tool you can patch your SMW ROM automatically with the ASM files of your choice.
(Which should be very helpful to patch it much faster and more efficient)

This tool use the patch program asar. (which is not included in the ZIP file!)
Possible asar version to use this tool: Asar 1.50, Asar 1.60

Also be sure to have .NET Framework 4.5 or above, otherwise it will not work.

Read readme.txt for more details too.

Source can be found under this link.
While it's a good idea to automatize patch insertion, and kudos to you for trying to make it easier for the users... sadly, I've got enough reasons to remove your tool. Some of them include:

-> Your tool is hardcoded to accepted only some given Asar versions, like 1.50 and 1.60. As we're currently with Asar 1.61... your tool wouldn't work with newer resources;

-> Your tool creates too much folders and unnecessary work. I liked the idea of an 'ignore patch' list, but let's think: wouldn't be easier to the user just put the patch they want with the tool and be done with it? In this method you created, I'd have to create two files called 'ignore.txt', which is a waste of space (small, but it exists); also, when your tool calls asar to apply the patches in your ROM... they get copied to another folder? More wasted space, I guess. Why don't you create a simple .txt file naming every patch you applied, for instance?

-> You mentioned your program calls asar to apply the patches. Ok, it's natural, but... your tool closes right after it's done. Sadly, if it not pauses before closing, you won't know if, for example, some patch gave errors when applied with Asar. Think about this: you're patching, say, 50 patches in your ROM (exaggeration, I know, but must be done to better exemplify the situation); if one measly patch gets errors because, for example, it has an out-of-bounds branch error, wouldn't be downright frustrating for the user to not know this since your tool does not pause so they can read the errors given by Asar?

-> Last but not least, also being, for me, the main removal reason: You mentioned you have to place your original ROM into a folder in order to run your tool so the ROM gets patched. First: I think this step is too much; Asar works so you can put everything in the same place, and it's interactive enough to enable fast and easy patch applying. But the real problem is, and I'll quote your readme:

Originally posted by Readme
-------------------------------- WARNING!---------------------------------------
DO NOT APPLY IT TWICE IN A ROW! Otherwise both of your files
('smw.smc' and 'orig_rom\smw.smc') will be patched!!!
-------------------------------- WARNING!---------------------------------------

As I understood, there's a possibility that your tool can mess with your backup. This is a no-no situation in this case. So, I think I've got enough reasons to not accept your tool as is; feel free to do some real improvements to it and then resubmit. I recommend, as a final note, to simplify your tool, thus simplifying your readme; it's pretty confusing in my point-of-view.
An additional note: consider simplifying this tool a bit. This isn't related to any of the removal reasons, just for accessibility. This tool's userbase is going to be almost entirely basic users.

For basic users, a complex system of folders, moving files, and ignore lists is complicated and may turn users away. First-time users that need to patch only a few files will take longer setting this up and figuring out how to use it than patching with asar manually, and that's a pretty big turnoff.

For advanced users, you're competing against batch files, and I'm sorry but you just can't compete against batch files.
Pages: « 1 » Link
Forum Index - Valley of Bowser - Moderation Questions - Tools - Universal Auto Patcher v0.1 by double_pmcl

The purpose of this site is not to distribute copyrighted material, but to honor one of our favourite games.

Copyright © 2005 - 2022 - SMW Central
Legal Information - Privacy Policy - Link To Us


Follow Us On

  • YouTube
  • Twitch
  • Twitter


  • Super Mario Bros. X Community
  • Mario Fan Games Galaxy
  • sm64romhacks