6 réponses à ce sujet

[kalbaern]

Bottom line is, don't do it. CEP 2.4 adds to many of the haks used by CEP 2.3. Therefore, if you're building in a CEP 2.3 (or earlier possibly) module, CEP 2.4 will have added to the appearances you find in the toolset even if you've not yet changed/added your hak list.

Since there's no distinction in most appearance names as to which CEP 2.4 added, a builder can easilly add appearances unknowingly into a CEP 2.3 Module. Then players will either encounter invisible placeables or have other issues, up to and including crashes in areas.

The easiest remedy for a Builder seems to be to just rerun the CEP Updater for 2.3. This should fix the haks that 2.4 essentially breaks.

[3RavensMore]

Hasn't the updater been broken for ages?

[kalbaern]

3RavensMore wrote...

Hasn't the updater been broken for ages?

The updater works fine and it's actually required that you run it even with a "so called" full CEP 2.3 Update. The Full 2.3 Update still lacks some things that running the updater will add.

If you use CEP 2.4 however ... you never should run the updater as it'll delete some of the stuff (mainly in the Core6 and SB haks) used by 2.4.

I.e., If you only build and play in a 2.3 module, you should run the updater even after downloading the CEP 2.3 Full install.

[Malagant]

Couldn't all that be avoided if players just had the most recent CEP? CEP was supposedly designed to be backwards compatible (except for the one time it wasn't). Granted the thing does have an unhealthy amount of bloat, it seems the height of redundancy to state not to build in a 2.3 mod with 2.4... it wouldn't be a 2.3 mod at that point once it were saved, much like how the toolset warns when opening any pre-SoU / HotU mod that the new save will require the expansions after that point.

[kalbaern]

Malagant wrote...

Couldn't all that be avoided if players just had the most recent CEP? CEP was supposedly designed to be backwards compatible (except for the one time it wasn't). Granted the thing does have an unhealthy amount of bloat, it seems the height of redundancy to state not to build in a 2.3 mod with 2.4... it wouldn't be a 2.3 mod at that point once it were saved, much like how the toolset warns when opening any pre-SoU / HotU mod that the new save will require the expansions after that point.

A player with either 2.3 or 2.4 is fine in a module built by someone using 2.3.

The issue arises when a builder working on a module set up for 2.3 actually has 2.4 installed themselves. There's a chance they'll end up using an appearance not valid for others using just CEP 2.3, including the server host.

[Tyndrel]

I take it this is because there wasn't a specific 2.4 top hak.  I have little choice now but to continue with my main project, I went to 2.4a when it came out and I suspect I am way too far down that road to turn back. I do have a prefab village pack I was building to match Leybury.  I have deliberately rolled that back to 2.3 in the light of the CEP stagnation, but it seems I did that for nothing, grumble grumble. 

[Malagant]

kalbaern wrote...

A player with either 2.3 or 2.4 is fine in a module built by someone using 2.3.

The issue arises when a builder working on a module set up for 2.3 actually has 2.4 installed themselves. There's a chance they'll end up using an appearance not valid for others using just CEP 2.3, including the server host.

That was kind of the point. If the Builder is using 2.4, it's not exactly a 2.3 module any longer. I'm well aware that anyone with 2.4 can play any post 1.x version without issue. I just thought it was redundant to say not to use 2.4 to build on a 2.3 mod if you want to keep the mod 2.3 specific.

I suppose it's just me. It's doubtful anyone has a complete list of resources to know what to avoid. I'd even doubt CEP has a comprehensive version specific list.