T-Shaped Dojo Connector Just Won't Die!

[Haku2049]

Today I got a message from my only Sage about dojo construction. I think he went ahead and decided to go back and do the early elevator thing, but a T-Shaped dojo connector towards the back (labeled: Haku, Try destroying this room, goodluck.) just refuses to get destroyed! I get the message: "Could not queue for destruction."

 

That's the first time a room has been stubborn like this to me! First connection problems with the AresUnited clan dojo, then this?!?

 

I just made and uploaded a Youtube video:

Edited August 24, 2013 by Haku2049

[Shion963]

I think he went ahead and decided to go back and do the early elevator thing

 

I don't understand what you mean by "early elevator thing". Some more information outside of "this problem occurred" would probably be helpful in deducing the cause, and possibly fix.

 

Anyways, here's the mundane run-through list: Are you sure that the tile you want to destroy isn't connected to anything else? Would deleting it orphan any tiles?

 

Sometimes I get the "Could not queue for destruction" message, and I just retried again and again until it came through.

[Haku2049]

I don't understand what you mean by "early elevator thing". Some more information outside of "this problem occurred" would probably be helpful in deducing the cause, and possibly fix.

 

Anyways, here's the mundane run-through list: Are you sure that the tile you want to destroy isn't connected to anything else? Would deleting it orphan any tiles?

 

Sometimes I get the "Could not queue for destruction" message, and I just retried again and again until it came through.

 

The first T-intersection in the Youtube video I wanted to make a + sign, allowing for easy elevator access. Like I posted with the video, we only have one new reactor (at the opposite side where the fun stuff is), You can see that just several hallway pieces remain. Nothing attached past what you see thanks to the doors I look at being red.

 

Tried to delete it repetitively, 100+ times, and it still refuses...

 

Then contacting tech support got things back on track!

Edited September 8, 2013 by Haku2049