i sent the creator a personal message saying the same thing so hopefully hell be able to help me.. i really don't want to start ovr
Copy your modded jar, then revert to the vanilla jar, either from your backup (you did keep a backup, right?) or by doing a force update, then use AMIDST, once you're done, revert back to your modded jar.
Rollback Post to RevisionRollBack
D_B
To tell them how to live is to prevent them living.
Copy your modded jar, then revert to the vanilla jar, either from your backup (you did keep a backup, right?) or by doing a force update, then use AMIDST, once you're done, revert back to your modded jar.
i just did that & i'm still getting the same message, but it does work with a fresh .jar but when i
re installed the mods i was useing i got the message again i think the mods are the reason its not working properly
At least Dweller_Benthos's way work for me.
I has an un-modded original clean 1.4.5 minecraft.jar backup. For me, just rename the recent modded minecraft.jar to any name, and then rename the original clean backup to "minecraft.jar", the Amidst can run perfectly now.
GSAHeppner4724 can go download a 1.4.5 minecraft from somewhere else, replace it to your "bin" folder and try, to see is it your backup version has problem or not.
i just did that & i'm still getting the same message, but it does work with a fresh .jar but when i
re installed the mods i was useing i got the message again i think the mods are the reason its not working properly
Mods i'm useing are: MC forge universal
Optifine Ultra
ThebombzeAPI
AutoSwitch
InvTweaks
TreeCapitator_Core Mod
ReiMinimap
Recipe book
The very first post in this thread (where you have to get the download link from) has a FAQ and in there, in blue text it says this
Q: When I run AMIDST & then either open my level.dat or enter a seed - nothing happens
A: Have you got a modded minecraft.jar ?? - Amidst won't work with those.... full stop!!
You need a clean version, so backup your minecraft.jar & do a force update using the default launcher to get a clean version
At post #2499 I tried with Modloader, Audio Mod, or Forge alone, even one of that single mod cause Amidst not work.
So, at this moment, let us use our backup pure minecraft.jar when we wanna open Amidst, until Skidoodle fixed it.
Perhaps, Skidoodle can add a new feature to Amidst.
I'm sure there must be a way to determine is 'minecraft.jar' has been modified or not (After all 'Magic launcher 'knows') so how about the IF Amidst sees a modified 'minecraft.jar' - it then automatically uses a 'clean_minecraft.jar' in the same folder.
THEN all we have to do is do a force update (to get clean minecraft.jar)
> Copy & rename it to 'clean_minecraft.jar'
> People can then modify their 'minecraft.jar' however they like but AMIDST will still work 'cos if it see the modified version - it'll THEN use the clean version instead
Perhaps, Skidoodle can add a new feature to Amidst.
I'm sure there must be a way to determine is 'minecraft.jar' has been modified or not (After all 'Magic launcher 'knows') so how about the IF Amidst sees a modified 'minecraft.jar' - it then automatically uses a 'clean_minecraft.jar' in the same folder.
THEN all we have to do is do a force update (to get clean minecraft.jar)
> Copy & rename it to 'clean_minecraft.jar'
> People can then modify their 'minecraft.jar' however they like but AMIDST will still work 'cos if it see the modified version - it'll THEN use the clean version instead
I would think a check for the meta-inf folder in the jar would be sufficient, as that is a good indicator if the jar is modded or not. Unless you're modding manually, most of the other methods leave a clean copy of the jar, so pointing AMIDST at that would be the way to go. Or, having it remember a specific jar instead of defaulting to the one in the bin folder.
Rollback Post to RevisionRollBack
D_B
To tell them how to live is to prevent them living.
I would think a check for the meta-inf folder in the jar would be sufficient, as that is a good indicator if the jar is modded or not. Unless you're modding manually, most of the other methods leave a clean copy of the jar, so pointing AMIDST at that would be the way to go. Or, having it remember a specific jar instead of defaulting to the one in the bin folder.
Oh yeah - sort of forgot about how you usually have to delete meta_inf folder when adding MOD's (I been using magic for quite a while & never had to deal with THAT ),
so yeah - just get AMIDST to see if meta_inf exists.. if it doesn't THEN use 'clean_minecraft.jar' found in the same folder should fix ~50% of 'AMIDST only shows grey screen' posts
Oh yeah - sort of forgot about how you usually have to delete meta_inf folder when adding MOD's (I been using magic for quite a while & never had to deal with THAT ),
so yeah - just get AMIDST to see if meta_inf exists.. if it doesn't THEN use 'clean_minecraft.jar' found in the same folder should fix ~50% of 'AMIDST only shows grey screen' posts
Alternatively, I could just have it search for clean_minecraft.jar, and use that if it exists.
Alternatively, I could just have it search for clean_minecraft.jar, and use that if it exists.
If this is going to be the option then i have an idea. You could add the jar to the download by calling the file cleanmc.jar and have the program just search for the jar within the same folder.
Although this may have the redistribution legal crap on it but i dunno.
If this is going to be the option then i have an idea. You could add the jar to the download by calling the file cleanmc.jar and have the program just search for the jar within the same folder.
Although this may have the redistribution legal crap on it but i dunno.
It is, but there's no rules against making AMIDST download a fresh copy from the minecraft website... is there?
Maybe I shouldn't post that, but it's not really a secret.... I would think a check for a modded jar (no meta-inf? - must be modded) or an error trap for the noverify error that pops up a dialog that says the jar is modded, choose an unmodded jar and use it from now on?
Rollback Post to RevisionRollBack
D_B
To tell them how to live is to prevent them living.
How about possibly making a way to choose the jar to use whenever you want?
For example, I use MultiMC, and have 9 instances. Between them, I am using 6 different versions of Minecraft (some modded, some not), ranging from beta 1.7 all the way up to the current version (I keep a vanilla one that I always update so I can copy it for modded instances). That way, instead of always having to make sure you have an unmodded minecraft.jar in a specific folder, you could just tell it to check a specific jar file that is wherever you want it to be.
You could also rename several jars to minecraft(version).jar (depending on their version. Example: minecraft145.jar), because terrain generation differs between certain versions (the biggest one I can think of is when the Adventure Update was released)
Whenever I try to activate both the .exe file and .jar file for it (I got the 7zip download), the same message comes up for both saying "Amidst ran in JAR mode without -noverify! Use:java -noverify -jar AMIDST.jar" help?
Whenever I try to activate both the .exe file and .jar file for it (I got the 7zip download), the same message comes up for both saying "Amidst ran in JAR mode without -noverify! Use:java -noverify -jar AMIDST.jar" help?
Getting the same problem.. Windows 8 btw.
When I launch it the way it wants me to it loads up but errors out in the console and in the actual application nothing happens when I try to load up my level.dat... version 1.4.4
Usually the noverify problem is from having a modified jar file, get a clean jar and try again.
Rollback Post to RevisionRollBack
D_B
To tell them how to live is to prevent them living.
Copy your modded jar, then revert to the vanilla jar, either from your backup (you did keep a backup, right?) or by doing a force update, then use AMIDST, once you're done, revert back to your modded jar.
D_B
To tell them how to live is to prevent them living.
re installed the mods i was useing i got the message again i think the mods are the reason its not working properly
Mods i'm useing are: MC forge universal
Optifine Ultra
ThebombzeAPI
AutoSwitch
InvTweaks
TreeCapitator_Core Mod
ReiMinimap
Recipe book
I has an un-modded original clean 1.4.5 minecraft.jar backup. For me, just rename the recent modded minecraft.jar to any name, and then rename the original clean backup to "minecraft.jar", the Amidst can run perfectly now.
GSAHeppner4724 can go download a 1.4.5 minecraft from somewhere else, replace it to your "bin" folder and try, to see is it your backup version has problem or not.
The very first post in this thread (where you have to get the download link from) has a FAQ and in there, in blue text it says this
So, at this moment, let us use our backup pure minecraft.jar when we wanna open Amidst, until Skidoodle fixed it.
I'm sure there must be a way to determine is 'minecraft.jar' has been modified or not (After all 'Magic launcher 'knows') so how about the IF Amidst sees a modified 'minecraft.jar' - it then automatically uses a 'clean_minecraft.jar' in the same folder.
THEN all we have to do is do a force update (to get clean minecraft.jar)
> Copy & rename it to 'clean_minecraft.jar'
> People can then modify their 'minecraft.jar' however they like but AMIDST will still work 'cos if it see the modified version - it'll THEN use the clean version instead
I would think a check for the meta-inf folder in the jar would be sufficient, as that is a good indicator if the jar is modded or not. Unless you're modding manually, most of the other methods leave a clean copy of the jar, so pointing AMIDST at that would be the way to go. Or, having it remember a specific jar instead of defaulting to the one in the bin folder.
D_B
To tell them how to live is to prevent them living.
so yeah - just get AMIDST to see if meta_inf exists.. if it doesn't THEN use 'clean_minecraft.jar' found in the same folder should fix ~50% of 'AMIDST only shows grey screen' posts
Alternatively, I could just have it search for clean_minecraft.jar, and use that if it exists.
Although this may have the redistribution legal crap on it but i dunno.
It is, but there's no rules against making AMIDST download a fresh copy from the minecraft website... is there?
I dunno.....
http://assets.minecraft.net/1_4_5/minecraft.jar
Maybe I shouldn't post that, but it's not really a secret.... I would think a check for a modded jar (no meta-inf? - must be modded) or an error trap for the noverify error that pops up a dialog that says the jar is modded, choose an unmodded jar and use it from now on?
D_B
To tell them how to live is to prevent them living.
For example, I use MultiMC, and have 9 instances. Between them, I am using 6 different versions of Minecraft (some modded, some not), ranging from beta 1.7 all the way up to the current version (I keep a vanilla one that I always update so I can copy it for modded instances). That way, instead of always having to make sure you have an unmodded minecraft.jar in a specific folder, you could just tell it to check a specific jar file that is wherever you want it to be.
You could also rename several jars to minecraft(version).jar (depending on their version. Example: minecraft145.jar), because terrain generation differs between certain versions (the biggest one I can think of is when the Adventure Update was released)
https://soundcloud.com/masterfireheart (Music)
http://www.minecraftforum.net/user/1764 ... fireheart/ (MCForum)
http://steamcommunity.com/id/masterfireheart (Steam)
http://www.reddit.com/user/Masterfireheart/ (Reddit)
https://twitter.com/masterfireheart (Twitter)
http://masterfireheart.deviantart.com/ (DeviantART)
This has nothing to do with MCPatcher... AMIDST is a completely different program that does a completely different thing...
Usually the noverify problem is from having a modified jar file, get a clean jar and try again.
D_B
To tell them how to live is to prevent them living.