Wyrdysm Games

Anna wrote:This forum is not a democracy

It would appear that Le' Seraph is displeased with his subjects, lol.

Anna wrote:You should absolutely not be including the Fraxy_112 sprite in the Doodads folder. It belongs in the fucking /Fraxy Sprites/ folder, which I already have three goddamn duplicates of, because idiots wouldn't leave sprites where they belonged, or wouldn't name folders the way they were told, so all the fraxy sprites ended up getting spread around under "/Fraxy Sprites/" or "/FraxySprites/" or even just "/fraxy/". We do not want people to require duplicates of sections. The fraxy_112 does not belong in the "/Doodads/" folder. Do not put it there, do not use it from there.
Likewise, the SS Windows sprites do not go in the /Doodads/ folder. They are meant to just be extracted into the Custom sprites folder, and not in any sub-folder.

That is just inefficient. It's like someone starting a project and putting most of the pieces in the work area and a few on a shelf. I personally do not understand why, but I'll do it your way anyway. I left the copies of the doodads in the doodads folder as well. If people don't want them there, they can delete them. Just copy and paste into the custom sprites folder, it will still function your way.
A new version is available with the ini file done this way.(version 1.01)
I still think it's backwards.

Why is it inefficient? It doesn't matter what folder things are in when you compile them in an ini file and we have a streamlined method of sprite naming rules that allows for easy access to each other's ships. Defying those rules is just stupid.
Also, Anna is right. Always. Every time.

I guess. But, what if we wanted to compile these doodads into a file for export. If someone was newer to the forums, we would have to hunt down all of those separate files and put them into it. I just think that it would make exporting doodads that aren't with the original game much easier. It would get annoying having to hunt those doodad files down for every custom export. (in case the users don't have them).

Extra doodads removed from the file. 2x2, 3x3 blinkfaders and teamstripes are still in the doodad folder though.
New version posted. v1.02

version 1.01 removed

Doogie12 wrote:Also, Anna is right. Always. Every time.

There are rare times when even he makes mistakes, but usually because someone else doesn't do their homework and causes confusion.

Anna wrote:I made a mistake. The last two ones are from the latest download, which I didn't have because HorseMonster is dumb and didn't post the latest update in his thread, only adding it to the OP instead, so I somehow missed it.

The Kuparax is the only one containing a section which doesn't actually exist in the official download, Custom sprites\HorseMonster_DetailedWeapons\HM_wepMachinegun01fixed_noanimation.gif

Still, problems like this wouldn't occur if people included sprites in their downloads.

What I learned about Anna today. . .
If you think he's mad at you, he thinks you're stupid.
If you continue, then he's mad at you.

Zalausai wrote:That is just inefficient. It's like someone starting a project and putting most of the pieces in the work area and a few on a shelf. I personally do not understand why, but I'll do it your way anyway.

To avoid having superfluous, unnecessary fucking sprites.

It's for the same reason that I don't lump all the sections I like to use into 'Custom Sprites/Good Sprites/', because then for every ship I make, people will be getting duplicates of sections that they probably already have. It leads to confusion and irritation and just general annoyance. I used to get newbies regularly who'd just toss their custom sprites in any folder they wanted, ignoring where they were actually meant to go, and it resulted in those newbies posting ships that nobody could use without errors.

So basically, moving sections from the folders they're meant to go in is bad, and you shouldn't do it.

Zalausai wrote:What I learned about Anna today. . .
If you think he's mad at you, he thinks you're stupid.
If you continue, then he's mad at you.

I tend to adopt the approach of assuming people are stupid and hoping that they prove me wrong, now.

The team stripes, larger glow faders, and stuff that was already there is still in the right place at least. Or was the ship maker repack affected by the above mentioned newb sorting problem?

The latest file is set up correctly. The copies have been removed and the doodads are in their proper places. The ini file is set up this way.

Glow faders and team stripes and stuff go in the /Doodads/ folder, yes.

The download for the doodads v1.02 has been corrected. The correct file is now present.

A new ini file and sprite pack has arrived.
Living Vessel from the shipmaker repack
On group 1 is bio sprites to construct a skeleton as the undercarriage of a living ship.
On group 2 is machingbioshipNC to construct the fleshy parts over said skeleton.

An associated ini file is provided.

May be a good choice for some darkness ships.

Are those new flare sprites included yet?

They are in the "extra sprites" thread.

Zal, could you make the 'Noc_Rune' sprites work as doodads in an ini., im not sure how to do it myself.

I'll get to work on it after I finish the "Drone" tutorial. I've decided to do it next instead of other plans, but they'll still get done.
The Noc_Rune that I have has 20 sprites. It came with the shipmaker repack. I'll be using that unless specified otherwise.

What exactly are you having trouble with, Necrontyr? It's really easy. It's stupidly easy.

Anna wrote:What exactly are you having trouble with, Necrontyr? It's really easy. It's stupidly easy.

It is fairly simple. Just takes some time getting used to.

Well I don't use often doodads that arn't default and if I do, I add them directly from the file. After seeing doogies new WFTU fleets I wanted to try the same rune/tatoo effect but I don't know how to get them all together.

Open smsprites.ini

There's a bit that says
[Doodads]

Add the sections in under there in the same way the doodads there are already listed, like:

pos31 = Noc_runes\Noc_Doo1.gif
pos32 = Noc_runes\Noc_Doo2.gif
pos33 = Noc_runes\Noc_Doo3.gif
pos34 = Noc_runes\Noc_Doo4.gif
pos35 = Noc_runes\Noc_Doo5.gif
...etc

Each one should have a unique pos#, and once you're done, change the "doonum=" bit to be the same as the number of doodads there are in your doodad list.

Presto, it's done.