Skip to main content

Making an Arcade Game: Input, Collisions, and Putting It All Together

  • Chapter
  • First Online:
  • 4517 Accesses

Abstract

In this chapter we’ll make our own 2D arcade games, putting together what we’ve got so far for a time-wasting experience to make others goof off so we can shine. Or something like that. The new things we need are better mouse and keyboard interaction, and collisions of objects.

This is a preview of subscription content, log in via an institution.

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   34.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Notes

  1. 1.

    using newTypeName = existingType; makes newTypeName an alias for the existingType. Use it for clarity as needed.

    The old style of this, which you may see sometimes, is typedef existingType newTypeName;.

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2019 Will Briggs

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Briggs, W. (2019). Making an Arcade Game: Input, Collisions, and Putting It All Together. In: C++ for Lazy Programmers. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-5187-4_12

Download citation

Publish with us

Policies and ethics