DataShare

[LegoEggo]

I got an idea while I was unloading the dishwasher (lol). It's this: we could put together a file of a load of datablocks that can be used for add-ons and all that good stuff, so people don't keep making datablocks that are probably already made.

So basically this is just going to be a file full of datablocks. But unless I'm horribly misunderstanding something, people will just reference them for their add-ons, and everything will be dandy! So, here's how it works:

To submit a datablock:
1. Get the datablock made. (Duh...)
2. Add a comment, e.g. //A basic bullet.
3. Post it here as an attachment to your post, with a name like this: projectile_bullet_normal, or summat.

I'll make some soon, but I have to leave in fifteen minutes, so ya know.

[Ad Bot]

[Stratofortress]

Nice idea. The bad part is that people that post stuff like "HOW THE HELL DO I MAKE ADDONS?" will get more steps to memorise.

[Space Guy]

That's what the Support_* files are for.

[laremere]

I think in V9 that all data blocks should be in their own file, so other mods can use them without activating the main mod...

[LegoEggo]

That's what the Support_* files are for.

Yes, but this will include more.

[Dilt]

While this SEEMS like a good idea, it won't really be. If a datablock goes unusued from the datashare file, it'll essentially be defeating the purpose of this mod, for example.

[Terror]

I think in V9 that all data blocks should be in their own file, so other mods can use them without activating the main mod...

How stupid are you?
You know how hard that is to manage? And it would look fugly.

[Dilt]

I think in V9 that all data blocks should be in their own file, so other mods can use them without activating the main mod...

How stupid are you?
You know how hard that is to manage? And it would look fugly.

Pretty smart. Look at how Trader handles JVS. He puts them in .code and executes them through a single .cs file. It's quite beautiful, if you ask me.

If you use DataShare like that, then I can take back my earlier comments - this might work.

[LegoEggo]

So you kind of lost me... what? All datablocks in different files? I'm confused.

[Vidios]

This wouldn't be needed if people learned to script decently.

[LegoEggo]

But it would also cut time on how long it took to make a weapon, if the datablocks were already done. I'll submit some when I get home from school.

[Monty]

No it wouldn't reusing and mimicking datablocks is far better than putting them all into one fat file, which people might not exec.

[Space Guy]

This basically is generic datablocks for people to use and/or mimic with code.

[LegoEggo]

Ok people, this is how it's going to work: Once you make a datablock, put it in it's own file with a name that describes it (we could work out a format). Since each of the datablocks is in it's own file, we'll have a folder hierarchy. Once this is all worked out, we'll do that.

[Trader]

It might be useful to have a library of datablocks for certain things.  Projectiles, particles / emitters, player types, sounds, etc. would be just fine to use with a system like this.  Although it would probably take an experienced group of talented modders to pull it off.

On the reverse, it'd only really be useful for noobs who don't know how to make Add-Ons other than weapon and map edits and who can't comprehend the meaning of "don't overwrite the game's built-in datablocks".

Overall, it probably wouldn't be worth the effort it would take.

@ Dilt:
I'm glad you approve of my code organization.