mojjj it uses SpringFeatures, which is apparently a bad thing?

Someone who makes maps should probably explain why.

Wha... the map comments go from top to bottom now?

@[ffc]killer there is a hidden button appearing as a blue "sort" word at the top of the comments area. Click that to change comment order.

New forum trolls me

Sprung, the features are not low quality. For example all of the features from 0ad are there, all of smoth's harbor features, and nearly every feature ever made for spring.

Yes, there are some old ones, but sometimes the old ones have uses too. Think before you take a giant shit all over other people's work.

AutoWar, Spring Features is a feature library for mappers. They can load their map up in SceneED and have hundreds of map features to add to their map. They get this functionality by simply relying on one central database (that exists in rapid), instead of bloating maps with features that degrade over time and can never be updated.

For example, if someone uses a feature that has been updated in later versions of Spring Features, then all they have to do is release a new version of their map depending on a later version of spring features.

Spring features also includes featuredefs that are defaults but can be copied into the map so that the map author can apply their own rules to the features.

Want a tree that gives 10000000 metal? Not a problem, copy the def into your map and change the metal value.

Want a rock that is indestructible? Likewise. Unfortunately people like Sprung don't understand the relatively simple concept.

Please, tell me more about the low quality features in Spring Features:



An those are BAD examples!

The collections are also not "Random". If you take a look at the repository here: https://github.com/Spring-Helper-Projects/spring-features/tree/master/objects3d/features you will see that they are very nicely organized.

ZKL does not understand how to download map dependencies. Every other lobby has had this functionality for YEARS.

Thanks to whoever registered this map for me. It shows up in SWL/SPADS now.

To clear this up, the assumption of AutoWar re. SpringFeatures was likely prompted by something I said here hypothesising about the "special" tag. To the best of my knowledge maps without SpringFeatures and maps with SpringFeatures v1.0 are not automatically tagged silly (Fairyland was not, at the time it used SF rather than copies of the relevant features) and I see no reason why somebody would manually have done so. Therefore I wonder if SF v1.6, being newer, is perhaps not registered as a "not-silly dependency" at this time.

Sprung could dial back the arrogant dismissal a few notches. I kinda think Forb overreacted but understandably.

quote: I forgot to add, that in the latest spring features, features generally have resource values of 0. This is to prevent oshit imbalances by newbie mappers.

http://zero-k.info/Maps/Detail/31026 :p :p :p

those are some fugly huge hitbox spheres.

please provide visual examples of better ones as brain-bleach!

Let me be very clear. I don't care if ZK can use this or sf at all. Don't care. THe reason I needed my map to be registered is because SWL uses zk's map listing stuff for various things likie minimap thumbnail and such. As a result, if it isn't registered properly here, then in swl it can't really be played.

It's a pretty stupid problem to have, but it is a problem nonetheless.

WRT hitspheres, make sure that you are basing any research off of the latest version.

The hitspheres on the trees you showed are perfectly valid. Haven't you ever paid attention to the boxes on the engine trees? The mapper is free to override them as they see fit.

If they include these features in their maps do you REALLY think that they are going to adjust the hitspheres? As a result, your argument of hitspheres being a mark against sf is completely bogus. You can feel free to berate feature authors for not setting them to your personal standards, but good luck with that.

Usually when I am using them, if a fix is needed, I fix them as I go along and commit to the repo.

Honestly, ZK needs to grow up and stop having features block projectiles anyway. It isn't cute, it isn't tactical, it's just dumb and annoying kludge. Good luck getting that to happen though.

WHY in almighty tits would someone want to have to recreate hundreds of defs??? That would be idiotic. Typically if you are using SF you are using a TON of features from sf. You think people should have to recreate a def each time? Are you nuts? Do you have any idea how long that would take???

You clearly don't understand the number of features that are in this archive. Either that or you're delusional... OR option 3, you think that mappers would only use one or two features here and there.

No, not all of the defs may be perfect, but you may feel free to contribute to the repo in making things better rather than complaining about it here.

Stop being so shortsighted and look at the big picture.
If I sound annoyed, that's because I am. Your argument is classic throw the baby out with the bathwater approach, "a few features aren't perfect so omfg we better start ALL over!", and it's stupid, especially when it can be fixed with defs ffs. This conversation should be about how you want to help, not about ... whatever the hell it is you're trying to prove.

Who makes these Spring Features anyhow?

SF actually does a very nice job at providing the models so if it had ZK-compatible reclaim values it would be the tool to use for ZK mapping (all other issues are not a problem because fixing them does not affect any game negatively).

Let's wait for Forb to say what he thinks of the idea.