Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Block Damage systems #4

Merged
merged 9 commits into from Jun 5, 2019
Merged

Block Damage systems #4

merged 9 commits into from Jun 5, 2019

Conversation

e-aakash
Copy link
Member

@e-aakash e-aakash commented May 24, 2019

Adds required assets and system for functioning of damage to blocks.

How to test:

  1. Create a new game with BuilderSampleGameplay template with Health Module activated in advanced settings
  2. Try to damage a block. See that the block takes damage before being destroyed.

Copy link

@iaronaraujo iaronaraujo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything looks fine!

@Override
public void renderOverlay() {
if (blockSelectionRenderer == null) {
Texture texture = Assets.getTextureRegion("health:blockdamageeffects#1").get().getTexture();
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Even though the BlockDamageEffects has been moved into the module, this line is creating NoSuchElementException.

{
"location": {},
"particleDataSprite": {
"texture": "core:fx_smoke"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will need to be changed to "health:fx_smoke" and the file should be duplicated to health because I'm fairly sure that there are other modules that use it.

@@ -0,0 +1,5 @@
{
"RigidBody": {
"kinematic": false
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this file still be here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is required, so will remove it.

Copy link

@iaronaraujo iaronaraujo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The regen is working! It would be nice to open an issue to fix the regen speed later though

@e-aakash e-aakash added this to In progress in GSOC 2019: Restoration 100 via automation Jun 5, 2019
@e-aakash e-aakash removed this from In progress in GSOC 2019: Restoration 100 Jun 5, 2019
@syntaxi syntaxi merged commit 184f07c into Terasology:master Jun 5, 2019
@e-aakash e-aakash deleted the block branch June 6, 2019 05:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants