Yet another inane question..

[HandsOn]

These one's are for the wise and not so weary
Is it possible, after a download, to find which out which of a custom lot is the ploppable and which is the growable, and then - for example - keep only the ploppable?

And on the subject of buldings: I've reached the stage in my region when pink seems to rule. In particular the Freytag Building, a nice enough attempt at classicism, suddenly begins to take over entire streets. Is there a way to limit this (I doubt it - but am hoping)..

Cheers..

[JoeST]

It usually says in the file name witch is the Plop and which is the Grow. If not it will be a property in iLive's Reader. The building exemplar will show its Occupancy Group as the RCI type and its wealth or Landmark or Reward

at least I think thats the case...

Joe

[HandsOn]

It usually says in the file name witch is the Plop and which is the Grow. If not it will be a property in iLive's Reader. The building exemplar will show its Occupancy Group as the RCI type and its wealth or Landmark or Reward

at least I think thats the case...

Joe

Thanks - I'll check that out and try it with those downloads that showed up as empty lots (removing the growables, that is). But there's a tag-on question: I've found various duplicate files (using the DupChecker), with identical dates, sizes and of course names. One example is the Retro Gasstation - it cam up with ten duplicates. I've naturally wondered if that could harm, slow down, or otherwise impact the game and if these doppelgaengers could be removed?

[JoeST]

It indeed will... because SC4 loads EVERY file in your plugins, then checks if its a valid file, and if a file has properties that then get overwritten in a subsequent file, then thats tough, but the first file still gets read...

Joe

[BarbyW]

Most BSC buildings that are growable will start their filename with the type, wealth and growth stage - i.e. R$3_ - and ploppables with the creator's initials - i.e. BLS_ - as per Maxis.
Having said that not all uploaders follow the naming convention so sometimes it is not easy to see which is which.

[HandsOn]

It indeed will... because SC4 loads EVERY file in your plugins, then checks if its a valid file, and if a file has properties that then get overwritten in a subsequent file, then thats tough, but the first file still gets read...

Joe

Joe: Thus cleaning up duplicates would definitely be a good thing, methinks..?

BarbyW: Would it be save to remove the growables of, in this case, BCS (sorry) BSC lots?

[wouanagaine]

Joe: Thus cleaning up duplicates would definitely be a good thing, methinks..?

BarbyW: Would it be save to remove the growables of, in this case, BCS (sorry) BSC lots?

Removing duplicates is always good, but if they are true duplicates like you said, it only helps loading time
Removing growables ( BSC ones ) is safe AFAIK

[HandsOn]

Removing duplicates is always good, but if they are true duplicates like you said, it only helps loading time
Removing growables ( BSC ones ) is safe AFAIK

Merci bien, maitre Wou..

[xxdita]

You can use Cleanitol, along with the Remove file found here to get rid of all currently known Empty Growable Lots.

[HandsOn]

You can use Cleanitol, along with the Remove file found here to get rid of all currently known Empty Growable Lots.

That "little" tool of yours is an absolute marvel. Since you are parsing text files, I am wondering which file type you are looking for to calculate the dependencies. Because I would have no problem, using a special browser I wrote a little while ago, to produce a list of all plug-ins in a given folder and then feed it to CT to determine what am I missing. But I would need to know what I am looking for..? Or am I asking for trade secrets here?

[xxdita]

Not my tool, Wouanagaine's.
I use SaveDir to list files when necessary, but for the Mega Packs, I keep a cheat sheet.
The filetypes for dependencies are either *.sc4model and *.sc4desc, or *.dat. Though sc4desc files are necessary for lots as well (unless the files have been merged).
Generally I use SC4tool to determine dependencies if for some reason the ReadMe is inadequate.