No Early Access update this week


#1

FYI, there won’t be an update to CIU over the weekend of 9-10 March 2019.

The reason is that Apple decided to deprecate all existing IA games on the Mac Store, and CIU development has been suspended until this particular emergency can be resolved.

:angry:


CIU Development has suspended
#2

Bad Apple


#3

I think CIU development team has some conflict


#4

I’m still waiting 2 weeks with some boring


#5

This isn’t the first time that apple blocks the developement of universe
In one of the plain updates was said that the developement was interrupted due to the imminent removal of all games without a specific resolution (old games)

AppleCore

We alwais supported you
And now we will wait


#6

Can you provide some more detailed info about why they did that?


#7

Feminists didn’t find Girl version of Chicken.
image


#8

But… all of them deploy eggs


#10

“Hang in there!”


#11

I will des… I mean, I will buy a little Chihuahua and train it to bite Apple’s employees feet!


#12

We can help chickens to destroy apple markets in world.


#13

Apple know about the CIU development and do it on purpose.


#14

I’ve been always neutral to Apple in the sense I don’t give a damn what they do.

Now I’m leaning to hate them.

LET. US. SAVE. THE. UNIVERSE.

I’ve been waiting so long for a new chicken invaders. I will wait as much as it’s needed.


#15

Well, shoot.

Well, good luck trying to solve the issue. You have my support. :wink:


#16

cortex%20the%20nature%20guy%202
Apple.

you had one job you fools.


#17

Is that from Crash?


#18

yeah, it is.


#19

Everyone, grab your neutron guns. It’s time to get to the core of this.


#20

Shoot The Bad Apple


#21

Ok, work on Apple has been completed and we can resume CIU development next week.

Also, next weekend we’ll be moving the IA website to another provider. The forum and the CIU servers should not be affected by this move. More when the time comes.

@qbus371: The reason was that the game was “non-public” APIs (actually the fault of SDL 1.2). We’ve upgraded to SDL 2.0 and that seems to have fixed the issue.