Search results

I suggest artists select a Creative Commons license of their choice, and make it known. We also need to keep this fairly clear in the repository - for assets in modules, add some author and license information into the mod.txt. For assets in the engine, we need some similar mapping of art to...

I don't see why not, as long as it supports separate skeleton and animation files (which I would guess it does).

This is the sort of thing I would approach by giving the chunk a selection start and selection end vector and having it shade pixels rendered in that region (assumes AABB).

Sunlight propagation is the main issue with implementing vertical chunks. Sunlight currently assumes that there is only 1 vertical chunk, with sunlight at full strength above that. If the sunlight is blocked, then a shadow is pushed down to the bottom of the chunk. We fundamentally cannot have...

Another week. Implemented many of the improvements above, resulting in bandwidth of 2.3k out, 1.8k in a second. Could be even better, but this is decent enough to continue. Started working towards a proper clientside prediction model for character movement. Have changed the movement system to...

I think the first reason is fair. On the second point, I would recommend 16x64x16, 16x128x16, or 16x256x16. There needs to be enough verticality to support the new sunlight algorithm - sunlight needs to fade in over a reasonable distance, and that distance needs to be less or equal to the...

I don't see any reason to continue to support "classic" chunks. Can you explain why it is important to you? Or is this just a temporary measure?

Seems sensible to me, although I would probably send the event to the instigator, and call it BlockDroppedEvent. Probably should include the dropped block entity rather than (just?) the block.

Well, it needs to be within a registered (@RegisterComponentSystem) component system implementing EventHandlerSystem (I'm thinking of getting rid of that interface and just letting any component system have @EventReceive methods). I'll give it a quick spin and see if I can reproduce though...

Something like @ReceiveEvent(components={InventoryComponent.class, BookshelfComponent.class}, priorty=EventPriority.Critical) public void onRecieveItem(ReceiveItemEvent event, EntityRef entity) { if (!event.getItem().hasComponent(BookComponent.class)) { event.cancel(); } }...

Another update. At this stage clients can now use items in their inventory and attack - which means they can interact with the world a little. The implementation is crude, and will need to be cleaned up when client movement is updated to use a client-predictive model. Before that I want to...

A small update on this one - I added support for asset overrides. This allows modules to replace assets defined in other modules (including engine). Which means it is now possible to create tile packs - to say the least. The way this is done is by adding an "overrides" directory into a...

In Terasology we have the option of not rendering a voxel through the chunk buffers, but instead use the entity rendering system - so then the chest block could be a skeleltal mesh or otherwise and animated. This would be performance costly if done for too many blocks, but for a few...

Ok, a few things: All of those Strings should be MeshAnimations.The nice thing about our asset system is when defining a prefab and filling in an asset field, you can use the asset's uri - for example { "AnimationComponent" : { "walkAnim" : "core:blobWalk" } } And at...

Sounds good to me. :)

I think just having an block count in each chunk would be quite helpful. If you know the local area (chunk) contains 50 grass, 120 dirt and 3 stone, you can make some nice decisions about music, mobs to spawn and probably other things beside.

Those are good questions. We are missing some hooks, which need to be added, but others are present. Primarily it would be good to send "WorldStarted" events to the World entity at start up, then systems can listen for those to do initial entity creation and such (this can't really be done from...

Ok, so apparently I'm "Lead Software Architect". ;) Previously things have been fairly quiet so I have been dedicating time to realising the architecture rather than writing up reports on it (or just generally been slack), but things are picking up now. So in this thread I wanted to share...

Unless UIImage implements Asset, no. ;P

Ideally we should probably set up some flavor of asset to the asset system for atlases/icons - maybe have json files mapping textures to icons, and then you would obtain icons through Assets.getIcon() similar to any other asset. I welcome any change in that direction though, and this looks...