iceReaper/SpoutMaterials — comment on commit f15ff40e64f0b4143352933189fcef0085780491
File:  line 0
By kburdack:

Ok great. Your changes are a good direction. In particular the
"object" list which I did something similar to unify naming of
materials.

In case it helps prevent overlap I'm implementing in no particular order:

- server version of smgive
- dynamically colored blocks and recipes (batch processing)
- texture packing of local textures. Ie send 256x256 texture packed
with custom textures instead of lots of little ones. In particular
helps with explosion of combinations available from colorized blocks
- overriding of base materials by again using texture packing but
automatically assembling the texture pack zip to send to the client

On 18/01/2012, at 11:06 AM, iceReaper

wrote:

> however: i would not fork this version, cause im still refactoring some parts. i want to make materials and packs be loaded / unloaded at will. also make the materials accessable for other plugins, so they can rely on spoutMaterials for their custom materials. This should basicaly make SpoutMaterials an widely usable plugin. People just have to create an instance of the (under construction) SmpManager and then load the smp files for their plugin and voila, they can add their custom functions to the materials.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/iceReaper/SpoutMaterials/commit/f15ff40e64f0b4143352933189fcef0085780491#commitcomment-876448