The [Prop Stop] - It's online

[Enjay]

To be fair, a lot of the potential submissions for the prop stop probably don't really need any DECORATE. I mean, submissions like a single frame sprite that just sits there (a pillar etc) might be better, as chrono suggested, without any decorate or possibly evern being in a WAD (ie just right click the pic on the site and save it).

Anything more fancy - an animated thing, something that can die/explode or something with a special effect attached should be DECORATEd though.

[ShadesMaster]

I have an unfinished CacoPod - basically the DooM equivalent of Heretic's exploding pod. I just never got around to finishing the death frames!

[chronoteeth]

Exactly. Things like just a single pillar, a dead body, etc dont really need any sort of code at all. There's a lotta stock decorations to replace with 1 sprite. Besides, it makes it easier for the people who dont use zdoom on stuff. Sure its the most used port, but it aint up to stuff for everyone. This way though, it makes at least the decorations up to stuff for every port.

[Gez]

You mean "down to stuff" for everyone. Just because it's not plug-n-play for ZDoom doesn't make it more plug-n-play for other ports.

[chronoteeth]

Nada mister, I meant up to stuff. >:v

[Tormentor667]

To be fair, a lot of the potential submissions for the prop stop probably don't really need any DECORATE. I mean, submissions like a single frame sprite that just sits there (a pillar etc) might be better, as chrono suggested, without any decorate or possibly evern being in a WAD (ie just right click the pic on the site and save it).

I don't think so. Already adding a DECORATE isn't a bad thing, if you want to use that prop in other engines, you can still just delete the file. Though if you already have a DECORATE in the wad, you can just add the stuff right away to your resources without doing any thinking or coding I mean, it's saving another 3-4 minutes and that's what the Realm667 repositories are there fore - saving time and work so you can concentrate on other things.

[chronoteeth]

Does a single frame pillar that has no animation or glow whatsoever really need a wad or decorate? If anything, things like that would make it more of a hassle than just a single image.

[Gez]

If anything, things like that would make it more of a hassle than just a single image.

How? Why?

Before it can get into the game, an actor definition has to be made anyway. I don't see how copy-pasting an existing lump is more of a hassle than writing it.

[Ghastly]

I don't see how copy-pasting an existing lump is more of a hassle than remembering what flags and properties work for static decorations and trying to find a good radius and height.

Fixed.

[Tormentor667]

Before it can get into the game, an actor definition has to be made anyway. I don't see how copy-pasting an existing lump is more of a hassle than writing it.

Exactly!

[Enjay]

However, to consolidate the lumps, the thing usually needs to be dismantled and copied into the main DECORATE (etc) lump for the project anyway. Personally, I'd find that easier (for simply things) if I was just provided with the individual lumps and a copy/paste bit of text for the decorate from the website. I can, however, accept that wouldn't suit everyone.

My suggestion: If it isn't already the plan, make the files available in PK3 format. That way, it will be easier for people to load/extract/edit lumps using standard file management tools rather than having to use dedicated WAD managers.

Anyway, I don't want to dwell on this point. Ultimately, it's a minor issue and the far more important thing of this new service and good idea is being lost in the fog. Tormentor has clearly made his decision. How about we just go with that and provide stuff in the format he asks for?

[Tormentor667]

[quote="Enjay"My suggestion: If it isn't already the plan, make the files available in PK3 format. That way, it will be easier for people to load/extract/edit lumps using standard file management tools rather than having to use dedicated WAD managers.[/quote]
That's something I have thought about as well... converting the whole resources to PK3 format, as it's more editing friendly than having to fiddle around with wads.

[Ghastly]

My suggestion: If it isn't already the plan, make the files available in PK3 format. That way, it will be easier for people to load/extract/edit lumps using standard file management tools rather than having to use dedicated WAD managers.

It isn't that much harder opening with XWE, SLumpEd or something else, saving the resources to different folders and copy/pasting the code. Especially if the sprites are pngs anyway. I've done this several times for three mods (None of which I've worked much on, just compiled and severely edited the resources).

However, moving files from a pk3 to a wad is a little more annoying.

[Enjay]

Really? Given that everyone already has the capability to open zips as part of their OS if they have any recent version of Windows, or they will already have standard zipping tools, it's just the same as manipulating any other file. Compare that to the quirkier nature of dedicated WAD tools (which we are constantly being told "suck ass") and I think it is probably easier to use WADs for supplying lumps that will then need to be worked with .

Anyway, it is highly unlikely that someone is going to be able to use a resource from the Prop Stop "out of the box". Chances are that they are going to need to extract the DECORATE in order to paste its contents into another DECORATE lump and, if I am to believe what I'm told, a lot of people have problems getting XWE to do anything with PNGs without it "totally messing up the colours".

Anyway, as I said before, it really is a minor issue. Which ever way the resources are provided (wad, pk3 or separate lumps) the end user will have to manipulate them somehow and each of the possible formats have advantages and disadvantages. From what I can see, the relative merits don't seem to give any particular method a clear advantage over the others.

[chronoteeth]

The PK3 set up is a much better idea for the individual stuff, but for larger things or more defined/more sprites/more etc. things are, PK3s actually tend to be much more confusing to pick apart and use instead of a single wad file