Ecliptic: galaxies should be able to issue planets about azimuth HOT 7 OPEN

As far as I'm aware, this is the only part of the code that explicitly disallows spawning them:

What I don't know is whether the rest of the flow assumes things like "a point's children count fits in a uint16" or "a point's sponsor is always one level up" and whether they could be worked around. I suspect it's possible, but that's the first thing to check.

Obviously, anything in Ecliptic is upgradable, anything in Azimuth isn't really, so keep that in mind.

from azimuth.

For previous discussion, see #2.

When making this change, spawn- and child-related logic needs to be re-checked in all contracts. I'm unsure off the top of my head whether it matters anywhere, but the assumption during development was always "galaxies can spawn max 255 child ships".

from azimuth.

I read over the contracts (lightly) a while back and the data store (Azimuth contract) has either a 2^32 max or 2^256 max on everything. I don't think that much in Ecliptic besides spawn limits is implicated - some things, like escape logic (can only escape to one class higher) are not actually problems in my view (it's okay if escaping from your nonstandard class of parent is one-way).

I anticipate a lot more effort rechecking all the logic than in actually adding new logic.

from azimuth.

That's probably true. Of course, for Urbit to support these there may be changes required in the %jael vane as well. That's easier, though.

from azimuth.

I predate %jael so it's not familiar to me, but I will at least look it over.

from azimuth.

I suspect %ames is more likely to have an issue with this than %jael. The :dns app also might need some adjustment for this case. Happy to take a look when things settle down a little.

from azimuth.

Historically, it worked fine pre-jaeling of ames; depends on how much has been gutted.

from azimuth.