• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
AaronWizardstar

How do you feel about using dead/unmaintained libraries?

3 posts in this topic

Say I'm looking for a certain kind of third-party library/framework/engine to fill some role in my game. I find a library that fits my requirements, or at the very least fits my requirements better than similar libraries. The only drawback is that the project is apparently dead. The web site hasn't been updated in years, the forums are empty, and the source repository seems inactive.

 

The library is open source, so it's not necessarily lost. But then I'd have the responsibility of maintaining the library myself in my own project. The alternatives are (a) using a worse but active library or (b) implementing the library functionality myself and possibly killing my project again.

 

How do people here feel about using libraries that aren't maintained by anyone anymore? Does it ever depend on the project and/or what the library does?

0

Share this post


Link to post
Share on other sites

Depends on how mature it was before it was abandoned. If it was fairly mature (ie, no game-breaking bugs) then no biggie. Additionally, it depends upon your ability and willingness to fix for yourself any bugs that do occur. If it's so complex that a bug would stymie you, then maybe don't use it. Finally, it might also depend on the availability of other, more active, libraries that can fill the same need.

2

Share this post


Link to post
Share on other sites

I would look for for the following criteria:

 

- Does it at the moment (ie. in the state it was left in) fill my needs with no major missing features or bugs? If yes, I wouldn't be that afraid of what happens in the future.

- If I would need to fix or modify it, does the code look like it would be manageable?

- Does the code interface with system-level APIs and potentially need updates for new operating system or API versions? (libraries like SDL or OGRE) Or is it just self-contained and operates on data? (image loaders, physics libraries etc.) For the former being a dead library is a bigger deal.

Edited by AgentC
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0