No problem, thanks for bringing up this issue, hopefully others with the issue will find this.
If I may make a suggestion? putting that info on the OP would probably be most helpful and also unless the person using it is a developer to have the dev options put to false for the general consumption of the non-mod developer users.
Looking for confirmation of working forge versions
I am currently running 13.1.1225 on our server (was min required for another mod) Have had no issues with this forge version and TC 4.2.1.4
I did see mention of the biome fix being implemented in forge 13.1.1229. which i am keen to put in, as in a test world of our current setup, I did not find any taint or magic forest within 5000 blocks of spawn...... just two solitary silverwoods
being vary cautious about upgrading forge so wanting to know, Is anyone running 13.1.1229? any issues?
I also see that 13.2.1230 and 1231 are out as well - anyone running either of these on a server?
think this will answer your question. Look at the last 3 recent versions.
I'd say that site is fan fiction run... But it's all fan faction it's because it works like this:
Royal facehugger -> Preatorian <-- This is the problem, they always make preos because the facehuggers are always put with a humanoid... For a reason
That's with the Alien series. In Aliens vs Predator series they came up with a different method of how Queens emerge. I would assume Ri5 would use the AvP method of Aliens evolving/aging into other forms depending on certain circumstances. So basically there are two established ways for Queens to be brought about. Also I wouldn't discount that site for being completely fan fiction since a lot of the information comes from games and the comics (official comics mind you) as well as novels. It's not like they are making that stuff up and hoping people take it at face value.
As I said in my other post it ultimately comes down to how Ri5 wants to do things.
Ultimately it boils down to how Ri5 wants to do things this is his mod after all, how he wants to develop it is entirely up to him. Although constructive criticism and general ideas from those who play with it will play a part. It is entirely up to him if he wants to include and develop features being suggested along with how he's winging the mod in his mind. Simply put Ri5 has the final say and can decide for certain what is and isn't set in stone for the mod.
I did thats why i did ask for help, i did because was insecure, download the latest MalisisCore-1.7.10-0.9.9.jar and MalisisDoors-1.7.10-1.2.1.jar thrice. So ye, sorry but it doesnt work.
Looks as though your problem is with railcraft and it's hidden block thing. This issue is stated on the OP your option to fix the issue is to go into the railcraft configs and turn the hidden block feature from true to false.
Chestbursters running away will be in the next update
I know for sure the revised Facehugger infestation will be included in the next update also
Chestbursters will already evolve into a Drone after ~2 Minecraft days. But I do see what you mean by other Xenos. I know that the Hive System will be massively updated soon, and it is possible that something like other evolutions will be included (such as a Drone to a Warrior, etc). This might also include changed Ovamorph AI, such as making them hatch almost instantly. However, I'm not 100% sure about this.
As for stuff that is likely:
Different Predator types have been talked about a lot
I made a Runner and Runner Warrior model (yes, I had to take some artistic liberties with the Warrior evolution, based on the original Runner design from Giger himself), but I don't know when/if they will be added. Also I don't think the animal infestation is planned for anytime soon, but that doesn't mean it will never happen.
Not sure about the Guns and Marines
Also, next time please take the time to just skim through the past pages, but I will go ahead and give you these links for upcoming features: Link 1, Link 2
Take it that the runner and runner warrior eventually will evolve into a Crusher? I read on xenopedia it was implied that the Crusher was a Praetorian that evolved from a runner.
It's either Project Red that's the culprit or it's TiC and the other addon mods for it. Like Mechworks and Steelworks. Maybe the person currently in charge of the mod could take a look into it?
yeah... there's quite a few vids on youtube in how to set up an automated smeltery. Like having faucets with casting tables or even the block casting thing and having three faucets on two sides and using a timer for each side so the faucets activate to pour. So far I haven't been able to reproduce those kind of builds successfully. Usually only 1 or 2 of the faucets work. Half the time only one works. It's as if they faucets are ignoring the red alloy wire or if in the case of a timer is ignoring the signal completely.
I think something is screwed up as far as blocks being powerd ect. Not sure what and haven't cared enough. I use a timer from project red to automate a corner. Oddly it only works sometimes on both sides of the corner... never figured that out either but meh. I just leave it going after smelting a few hundred ore.
Yeah I was wondering why my timer set up wasn't working. It's a pain to cast liquid metal in an automated system due to that.
in the 1.7.10_AM2_1.4.0.005 version i get a potion id conflikt with reika's mods.
Reika.DragonAPI.Exception.IDConflictException: The mods were not installed correctly:
CONFLICT: Potion IDs: am2.buffs.ArsMagicaPotion@6c2d1ced @ 52
Check your IDs and change them if possible.
I take it its the potion id 52 from reika's that it refears to. However if i change reika's id (cant seam to find the AM2 potion id in the config) i get
Reika.DragonAPI.Exception.IDConflictException: The mods were not installed correctly:
CONFLICT: Potion IDs: am2.buffs.ArsMagicaPotion@1fddd5ee @ 61
Check your IDs and change them if possible.
Eny fix for this? (Made a NEI potion id dump to find what id's that was not used)
keep changing the ID's until you find one that doesn't cause that crash. It's trial and error at that point.
Also, crash related to a deprecated Buildcraft API in DragonAPI when using the version above.
Removing the "buildcraft" folder in DragonAPI fixed the problem.
Mind you that's a pre pre release of the new buildcraft, it's meant to really be tested in separate instances.
0
If I may make a suggestion? putting that info on the OP would probably be most helpful and also unless the person using it is a developer to have the dev options put to false for the general consumption of the non-mod developer users.
0
think this will answer your question. Look at the last 3 recent versions.
http://files.minecraftforge.net/maven/net/minecraftforge/forge/1.7.10-10.13.2.1231/forge-1.7.10-10.13.2.1231-changelog.txt
0
That's with the Alien series. In Aliens vs Predator series they came up with a different method of how Queens emerge. I would assume Ri5 would use the AvP method of Aliens evolving/aging into other forms depending on certain circumstances. So basically there are two established ways for Queens to be brought about. Also I wouldn't discount that site for being completely fan fiction since a lot of the information comes from games and the comics (official comics mind you) as well as novels. It's not like they are making that stuff up and hoping people take it at face value.
As I said in my other post it ultimately comes down to how Ri5 wants to do things.
0
0
As am I seeing as what that's being said pretty much contradicts a lot of the Alien series and AvP lore that I've seen on Xenopedia.
0
Looks as though your problem is with railcraft and it's hidden block thing. This issue is stated on the OP your option to fix the issue is to go into the railcraft configs and turn the hidden block feature from true to false.
2
Unless someone picks up the project with Mithion's blessings
0
Take it that the runner and runner warrior eventually will evolve into a Crusher? I read on xenopedia it was implied that the Crusher was a Praetorian that evolved from a runner.
0
0
0
Yeah I was wondering why my timer set up wasn't working. It's a pain to cast liquid metal in an automated system due to that.
0
keep changing the ID's until you find one that doesn't cause that crash. It's trial and error at that point.
1
Mind you that's a pre pre release of the new buildcraft, it's meant to really be tested in separate instances.
0
0
my mistake... lol I posted really late last night so my mind was sort of out of it.