No portal was created on the Arcana side.
Appeared in the middle of fire traps blocks.
Spawners get broken with a single hit. - Fixed
Spawners are not generating any mobs.

What about having a single specific "portal room" generate in arcana and always link that portal?

Hmm. It looks like Arcana spawners got destroyed from a single hit with just your hand. Was that a bug or was it intended?

Bug. They should be unbreakable.

Is that true of all arcana blocks?

Not arcanite tubes, but yes to everything else

Whenever we set a block to UnBreakable should we by default set it also to have a blast resistance to 18,000,000?

Yeah

What do you think about the portal room gen? I think it would be a nice solution to the portal glitches that occur in Arcana.

Maybe. It would have to be at the same chunk coords as the portal in the overworld.

Hmm. Why the same?

When sending the player back, there's no way to easily save where the overworld portal is

NBT field on the player.dat?

Spawners created by the Arcana worldgen emit particles, but do not spawn mobs. If in creative you destroy the spawner and replace it, it will spawn mobs.

Guys, I'm a little off topic, but do you have the source code of the old divine RPG on github? I have a guess as to correct a surprising number of bugs, including vethea crash in multiplayer, and crash when killing Ender-triplets with the sword.

I cant reproduce this issue. They spawn mobs fine for me. Are you sure you didnt just not wait long enough?

No. All we have is the decompiled src. Besides, the old version won't be updated. 1.4.7 is just way too old

Yeah I've seen them work. There's no reason it wouldn't update server side. Have you tried multiple types of spawners?

I waited long enough. (Just to be sure I waited a good ten minutes). I am talking about the BlockStupidSpawner blocks not spawning, the "trader creatures" spawn as they should.

I spent quite a bit of time in eclipse on this. It looked like by using the setBlock() functions from ArcanaChunk rather than the one from the worldObj, the server side misses getting the TileEntity registered. So you see the spawners "particles" in TileEntityStupidSpawner.updateEntity() because the client side is O.K., but it never enters the "if(!this.worldObj.isRemote) {" server side part that deals with the spawnTimer because the server side does not know about the TileEntity.

If for some reason you are seeing the BlockStupidSpawner working in Arcana, we need to figure out what is different.

Yes. All of them fail. When I place a spawner it works. :/

When should it update the server side?

I just ran the latest pull with the latest Forge in eclipse. Same problem. I will PM you a dropbox of the jar file I just built which also shows the problem.

Yeah I was able to reproduce this in the copy of the jar you sent me. Did you change anything related to the spawner flames? They seem a lot faster in that version.

And are you getting the issue in your dev environment, or just the obfuscated version?

All environments, dev and obfuscated versions. I have been trying to figure out the problem in eclipse that is why I gave so much info on what I observed above. I did not change anything from the github pull. As a matter of fact a did a full clean re-install of Forge/Eclipse to the latest version and then did a clean pull from github and then ran it from eclipse.

I am getting the same problem as @krwminer.
Dev environment, Forge 1230, Linux.

So I am not going crazy... That is good to hear.

UP arcana spawners can`t be destroyed...

They aren't meant to be.

I am sure I am stating to obvious, but you tried this on a new world right when you said you see them spawning? (Just trying to figure this out).

Yeah. I'll keep trying to reproduce this.

Would it help to zip up my dev environment and dropbox it too you?