Talk:Updates - Revision history

Pokeblink at 03:50, 4 September 2012

2012-09-04T03:50:11Z

← Older revision		Revision as of 03:50, 4 September 2012
Line 5:		Line 5:

	{{Reply\|space=:\|agree=ty\|user=Feanturi\|reply=Thanks for mentioning ^^}}		{{Reply\|space=:\|agree=ty\|user=Feanturi\|reply=Thanks for mentioning ^^}}

			==Nano armor==
			The armor now lasts only 10 seconds when you fall in lava, is this correct? I though it would last a bit more, diamond is a better choice if this is intended making nano nearly useless.

Feanturi at 23:41, 1 June 2012

2012-06-01T23:41:22Z

@@ Line 1: / Line 1: @@
 == Wikitext mistake on Updates page ==
 Maybe that's nothing, but 1.337b Changelog section is not closed(last two <nowiki>"}"</nowiki> not placed) so it all is shown as  plain text.
 Can someone with permission fix it plz? [[User:LitTLE|LitTLE]] 14:46, 1 June 2012 (CEST)

LitTLE: /* Wikitext mistake on Updates page */ new section

2012-06-01T12:46:51Z

Wikitext mistake on Updates page: new section

← Older revision		Revision as of 12:46, 1 June 2012
Line 18:		Line 18:

	{{Reply\|space=::::\|agree=\|user=Trifler\|reply=This can be resolved to everyone's satisfaction just by adding the sentence I requested to be added on [[Talk:Download]].}}		{{Reply\|space=::::\|agree=\|user=Trifler\|reply=This can be resolved to everyone's satisfaction just by adding the sentence I requested to be added on [[Talk:Download]].}}

			== Wikitext mistake on Updates page ==

			Maybe that's nothing, but 1.337b Changelog section is not closed(last two <nowiki>"}"</nowiki> not placed) so it all is shown as plain text.
			Can someone with permission fix it plz? [[User:LitTLE\|LitTLE]] 14:46, 1 June 2012 (CEST)

Ouroborus: undoing my changes

2012-02-29T02:23:28Z

undoing my changes

← Older revision		Revision as of 02:23, 29 February 2012
Line 1:		Line 1:
	~~==Bugs==~~
	Display or update bug in 1.71 on SMP. Nano Saber doesn't display it's state properly. With a Lappack equiped, when the saber is right-clicked, it briefly shows it's active state, then reverts to it's inactive state, regardless of wether it's actually active or not. Without a Lappack equipped, it's appearance rapidly switches between active and inactive appearances (along with repeatedly doing the 'wield new item' animation). Holding the saber out of the inventory (with the cursor) shows the state correctly. [[User:Ouroborus\|Ouroborus]] 13:43, 28 February 2012 (CET)

	==Dependencies==		==Dependencies==

Ouroborus at 12:43, 28 February 2012

2012-02-28T12:43:09Z

← Older revision		Revision as of 12:43, 28 February 2012
Line 1:		Line 1:
			==Bugs==
			Display or update bug in 1.71 on SMP. Nano Saber doesn't display it's state properly. With a Lappack equiped, when the saber is right-clicked, it briefly shows it's active state, then reverts to it's inactive state, regardless of wether it's actually active or not. Without a Lappack equipped, it's appearance rapidly switches between active and inactive appearances (along with repeatedly doing the 'wield new item' animation). Holding the saber out of the inventory (with the cursor) shows the state correctly. [[User:Ouroborus\|Ouroborus]] 13:43, 28 February 2012 (CET)

	==Dependencies==		==Dependencies==

Trifler: Reply to both Thejoshwolfe and Feanturi

2011-11-01T01:54:46Z

Reply to both Thejoshwolfe and Feanturi

← Older revision		Revision as of 01:54, 1 November 2011
Line 16:		Line 16:

	{{Reply\|space=:::::\|agree=\|user=Feanturi\|reply=I won't mention it at the update page öÖ IC² will always use the recent version of MCF}}		{{Reply\|space=:::::\|agree=\|user=Feanturi\|reply=I won't mention it at the update page öÖ IC² will always use the recent version of MCF}}

			{{Reply\|space=::::\|agree=\|user=Trifler\|reply=This can be resolved to everyone's satisfaction just by adding the sentence I requested to be added on [[Talk:Download]].}}

Feanturi at 11:06, 31 October 2011

2011-10-31T11:06:14Z

← Older revision		Revision as of 11:06, 31 October 2011
Line 14:		Line 14:

	{{Reply\|space=::::\|agree=facepalm\|user=Thejoshwolfe\|reply=It seems [[User:Feanturi\|Feanturi]] is missing the crux of what I'm saying. I want to know the version number of MCForge that IC2 depends on. I want it to be written down in the [[Updates]] page so that when it changes people can know when to remod their minecraft.jar.}}		{{Reply\|space=::::\|agree=facepalm\|user=Thejoshwolfe\|reply=It seems [[User:Feanturi\|Feanturi]] is missing the crux of what I'm saying. I want to know the version number of MCForge that IC2 depends on. I want it to be written down in the [[Updates]] page so that when it changes people can know when to remod their minecraft.jar.}}

			{{Reply\|space=:::::\|agree=\|user=Feanturi\|reply=I won't mention it at the update page öÖ IC² will always use the recent version of MCF}}

Thejoshwolfe at 04:01, 31 October 2011

2011-10-31T04:01:16Z

← Older revision		Revision as of 04:01, 31 October 2011
Line 7:		Line 7:
	{{Reply\|space=:\|agree=\|user=Feanturi\|reply=Read the Download Page and you will find the versions... derp}}		{{Reply\|space=:\|agree=\|user=Feanturi\|reply=Read the Download Page and you will find the versions... derp}}

	{{Reply\|space=::\|agree=\|user=Thejoshwolfe\|reply=~~EDIT:~~ to clarify, I want to know which version of MCForge IC2 depends on. The information is not on [[Download]] page; the information is not on the [[Updates]] page. Simply saying "always the latest" is actually wrong, because any update to MCForge that isn't exactly synchronized with an update to IC2 depending on it will violate the claim.<br/><br/>Here's the problem: I was running IC2 version 1.15 and I wanted to update to the latests version. I looked at the [[Updates]] page and saw that there was a new version out (1.23). I downloaded it, swapped out the jars in the mods/ folder, and ran minecraft. It crashed on initialization with an error as cryptic as "failed to load mod_IC2". The reason is that I needed to remod my minecraft.jar with a new version of MCForge (possibly one of the ModLoaders changed too; idk.). This is not obvious. If the [[Updates]] page had said something as simple as "Now depending on MCForge version x.x.x", this situation would have been avoided.}}		{{Reply\|space=::\|agree=\|user=Thejoshwolfe\|reply=to clarify, I want to know which version of MCForge IC2 depends on. The information is not on [[Download]] page; the information is not on the [[Updates]] page. Simply saying "always the latest" is actually wrong, because any update to MCForge that isn't exactly synchronized with an update to IC2 depending on it will violate the claim.<br/><br/>Here's the problem: I was running IC2 version 1.15 and I wanted to update to the latests version. I looked at the [[Updates]] page and saw that there was a new version out (1.23). I downloaded it, swapped out the jars in the mods/ folder, and ran minecraft. It crashed on initialization with an error as cryptic as "failed to load mod_IC2". The reason is that I needed to remod my minecraft.jar with a new version of MCForge (possibly one of the ModLoaders changed too; idk.). This is not obvious. If the [[Updates]] page had said something as simple as "Now depending on MCForge version x.x.x", this situation would have been avoided.}}

	{{Reply\|space=:::\|agree=\|user=Feanturi\|reply=The newest version of IC² uses always the newest version of forge (if its not for 1.9)}}		{{Reply\|space=:::\|agree=\|user=Feanturi\|reply=The newest version of IC² uses always the newest version of forge (if its not for 1.9)}}

Thejoshwolfe at 04:00, 31 October 2011

2011-10-31T04:00:31Z

← Older revision		Revision as of 04:00, 31 October 2011
Line 12:		Line 12:

	{{Reply\|space=::::\|agree=\|user=Trifler\|reply=In case anyone was wondering, it is confirmed that IC2 1.23 will not run with MCForge 1.1.1. --[[User:Trifler\|Trifler]] 02:30, 30 October 2011 (CET)}}		{{Reply\|space=::::\|agree=\|user=Trifler\|reply=In case anyone was wondering, it is confirmed that IC2 1.23 will not run with MCForge 1.1.1. --[[User:Trifler\|Trifler]] 02:30, 30 October 2011 (CET)}}

			{{Reply\|space=::::\|agree=facepalm\|user=Thejoshwolfe\|reply=It seems [[User:Feanturi\|Feanturi]] is missing the crux of what I'm saying. I want to know the version number of MCForge that IC2 depends on. I want it to be written down in the [[Updates]] page so that when it changes people can know when to remod their minecraft.jar.}}

Thejoshwolfe: restoring discussion about dependencies. Formatting with the Reply template.

2011-10-31T03:57:04Z

restoring discussion about dependencies. Formatting with the Reply template.

← Older revision		Revision as of 03:57, 31 October 2011
Line 1:		Line 1:
	~~The newest version of IC² uses always the newest version of forge (if its not for 1.9)~~		==Dependencies==

	:* In case anyone was wondering, it is confirmed that IC2 1.23 will not run with MCForge 1.1.1. --[[User:Trifler\|Trifler]] 02:30, 30 October 2011 (CET)		It looks like between 1.15 and 1.23, the dependent version of MCForge changed. Since the typical update usecase is to swap jars in the mods/ folder, it's very important to note updated dependencies.

			- [[User:Thejoshwolfe\|Thejoshwolfe]]

			{{Reply\|space=:\|agree=\|user=Feanturi\|reply=Read the Download Page and you will find the versions... derp}}

			{{Reply\|space=::\|agree=\|user=Thejoshwolfe\|reply=EDIT: to clarify, I want to know which version of MCForge IC2 depends on. The information is not on [[Download]] page; the information is not on the [[Updates]] page. Simply saying "always the latest" is actually wrong, because any update to MCForge that isn't exactly synchronized with an update to IC2 depending on it will violate the claim.<br/><br/>Here's the problem: I was running IC2 version 1.15 and I wanted to update to the latests version. I looked at the [[Updates]] page and saw that there was a new version out (1.23). I downloaded it, swapped out the jars in the mods/ folder, and ran minecraft. It crashed on initialization with an error as cryptic as "failed to load mod_IC2". The reason is that I needed to remod my minecraft.jar with a new version of MCForge (possibly one of the ModLoaders changed too; idk.). This is not obvious. If the [[Updates]] page had said something as simple as "Now depending on MCForge version x.x.x", this situation would have been avoided.}}

			{{Reply\|space=:::\|agree=\|user=Feanturi\|reply=The newest version of IC² uses always the newest version of forge (if its not for 1.9)}}

			{{Reply\|space=::::\|agree=\|user=Trifler\|reply=In case anyone was wondering, it is confirmed that IC2 1.23 will not run with MCForge 1.1.1. --[[User:Trifler\|Trifler]] 02:30, 30 October 2011 (CET)}}

← Older revision		Revision as of 04:01, 31 October 2011
Line 7:		Line 7:
	{{Reply\|space=:\|agree=\|user=Feanturi\|reply=Read the Download Page and you will find the versions... derp}}		{{Reply\|space=:\|agree=\|user=Feanturi\|reply=Read the Download Page and you will find the versions... derp}}

	{{Reply\|space=::\|agree=\|user=Thejoshwolfe\|reply=~~EDIT:~~ to clarify, I want to know which version of MCForge IC2 depends on. The information is not on [[Download]] page; the information is not on the [[Updates]] page. Simply saying "always the latest" is actually wrong, because any update to MCForge that isn't exactly synchronized with an update to IC2 depending on it will violate the claim.<br/><br/>Here's the problem: I was running IC2 version 1.15 and I wanted to update to the latests version. I looked at the [[Updates]] page and saw that there was a new version out (1.23). I downloaded it, swapped out the jars in the mods/ folder, and ran minecraft. It crashed on initialization with an error as cryptic as "failed to load mod_IC2". The reason is that I needed to remod my minecraft.jar with a new version of MCForge (possibly one of the ModLoaders changed too; idk.). This is not obvious. If the [[Updates]] page had said something as simple as "Now depending on MCForge version x.x.x", this situation would have been avoided.}}		{{Reply\|space=::\|agree=\|user=Thejoshwolfe\|reply=to clarify, I want to know which version of MCForge IC2 depends on. The information is not on [[Download]] page; the information is not on the [[Updates]] page. Simply saying "always the latest" is actually wrong, because any update to MCForge that isn't exactly synchronized with an update to IC2 depending on it will violate the claim.<br/><br/>Here's the problem: I was running IC2 version 1.15 and I wanted to update to the latests version. I looked at the [[Updates]] page and saw that there was a new version out (1.23). I downloaded it, swapped out the jars in the mods/ folder, and ran minecraft. It crashed on initialization with an error as cryptic as "failed to load mod_IC2". The reason is that I needed to remod my minecraft.jar with a new version of MCForge (possibly one of the ModLoaders changed too; idk.). This is not obvious. If the [[Updates]] page had said something as simple as "Now depending on MCForge version x.x.x", this situation would have been avoided.}}

	{{Reply\|space=:::\|agree=\|user=Feanturi\|reply=The newest version of IC² uses always the newest version of forge (if its not for 1.9)}}		{{Reply\|space=:::\|agree=\|user=Feanturi\|reply=The newest version of IC² uses always the newest version of forge (if its not for 1.9)}}