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

The Big Blob update, Part 3 (assuming that Part 2 was the Blob HUD) #9957

Merged
merged 6 commits into from May 8, 2016

Conversation

DeityLink
Copy link
Collaborator

@DeityLink DeityLink commented May 7, 2016

blob_update

  • Removed the obsolete and broken Blob random event
  • Added two new random events, Blob Cluster and Blob Conglomerate. The former is like a medium intensity meteor shower, sending a handful of blobs and node blobs at the station (about as rare as Communications Blackout). The later is a high intensity meteor storm, sending blobs, node blobs, and a few blob cores (I had 2-3 cores per showers during testing. This one is much rarer, one of the rarest events in fact, along with alien infestation and electrical storm). Both events can only trigger after 30 minutes have elapsed.
  • Blobs now make sounds when they attack mobs.
  • Added a new meteor gun intended for testing and debugging that lets its user choose which type of meteor to fire.

testing the new meteor gun: http://i.4cdn.org/vg/1462595027361.webm

ghost perspective when selected to become the overmind of a meteor blob core: http://i.4cdn.org/vg/1462601572814.webm

aftermath of a blob conglomerate: http://i.4cdn.org/vg/1462601972747.webm

blob_meteor

@Exxion
Copy link
Member

Exxion commented May 7, 2016

Maybe the lower limit on time for these events should be longer
And what happens if a ghost becomes the overmind of a meteor core and then that core misses the station?

Otherwise, looks cool

@DeityLink
Copy link
Collaborator Author

@Exxion if the core meteor falls off the Z level, it gets destroyed. And the ghost gets freed. (well the ghost can cancel camera view to free himself anytime from the perspective anyway)

@DeityLink
Copy link
Collaborator Author

As confirmed by dylan, meteors aren't supposed to move from a Z Level to the next. So it's getting fixed at last.

@@ -434,7 +434,7 @@ var/list/blob_candidates = list()
blob_candidate = null
..()

/obj/item/projectile/meteor/blob/core/process_step()
/obj/item/projectile/meteor/process_step()
Copy link
Member

Choose a reason for hiding this comment

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

Isn't this now a duplicate definition?

@DeityLink
Copy link
Collaborator Author

Added support for large projectile sprites. (the initial offset is now re-applied after every update_pixel() )

@DeityLink
Copy link
Collaborator Author

DeityLink commented May 7, 2016

@clusterfack That's not what he told me. He even said that you helped him implement Z-level delete.

jpg

@SarahJohnson489 Well blobs represent hardly a challenge when they don't have overminds. Nodes are basically like spacevines that spread through walls but not far.

@CptWad
Copy link
Contributor

CptWad commented May 7, 2016

Did you remove all the maps blobspawn landmarks?

@DeityLink
Copy link
Collaborator Author

I don't do map changes but these can be removed later.

@@ -130,6 +130,11 @@

if(!new_overmind)
candidates = get_candidates(ROLE_BLOB)

for(var/client/candidate in candidates)
if(istype(candidate.eye,/obj/item/projectile/meteor/blob/core))
Copy link
Contributor

Choose a reason for hiding this comment

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

Would this not also filter out anyone following the meteor as an observer?

Copy link
Collaborator Author

@DeityLink DeityLink May 7, 2016

Choose a reason for hiding this comment

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

nope. following someone/an object locks your ghost to that mob/object. Your eye is still tied to your ghost. the only way for your eye to become tied to the meteor is by getting picked as a candidate, or varedit.

@gbasood
Copy link
Contributor

gbasood commented May 8, 2016

A few things:

  • I noticed some people talking about removing blob spawn landmarks. Don't. They're not JUST for blob spawns.
  • Did you really add a random event to rotation that spawns multiple blob cores? Because that is going to end poorly for lowpop especially. I mean it's cool as a admin-firable event but random is maybe a bit much Nevermind, 30 minute requirement, so it's fine.

@gbasood gbasood added the Content Adds something. Neat! label May 8, 2016
@Exxion
Copy link
Member

Exxion commented May 8, 2016

I still think the requirement should be more like an hour

@gbasood
Copy link
Contributor

gbasood commented May 8, 2016

@Exxion If R&D is doing their job then players are more than capable of dealing with blobs at even the 20 minute mark in my opinion

If not, then it's a SUPER RARE EVENT so it should be 👌

@DeityLink
Copy link
Collaborator Author

DeityLink commented May 8, 2016

@Exxion
@gbasood
I was wrong. Random events cannot fire at all before 50 minutes have elapsed, so that 30 minutes check serves no purpose at all. So the minimum requirement will be about an hour.

Don't worry, I didn't touch the landmarks, nor did I plan to.

@gbasood gbasood merged commit 5b3a780 into vgstation-coders:Bleeding-Edge May 8, 2016
@CptWad
Copy link
Contributor

CptWad commented May 8, 2016

The landmarks for blobspawn might be used for something else so removing them might not be wise

@CptWad
Copy link
Contributor

CptWad commented May 8, 2016

Yo diety can you also update the wiki, specifically the random events page

@DeityLink
Copy link
Collaborator Author

will do

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content Adds something. Neat!
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants