• 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.

_Vicious_

Members
  • Content count

    190
  • Joined

  • Last visited

Community Reputation

330 Neutral

About _Vicious_

  • Rank
    Member
  1. My first idea would be to check the reference count of such objects and print a warning if they exceed 1 (I'm assuming that one reference is reserved for the engine).
  2. Not quite true in case of Go, which features different syntax for short variable declaration and assignment.   a := 0 // declares a variable 'a' and sets it's value to 0, same as 'auto a = 0' a = 0 // sets value of variable 'a' to 0 b = 0 // produces compiler error because assignment only works for variables that have already been declared in this scope
  3. The same kind of argument applies to 'auto', which found its way into AngelScript nonetheless.     I believe you are wrong here. I find it that polluting the code with structs and classes that do not serve any purpose other than storing the return values for non-trivial functions is very much an anti-pattern. You can't have too many of them without making a mess.     Again, this is debatable. I would think that the same kind of argument applies to structs or classes (having to remember which class member corresponds to what).     Overall, it seems to me that neither of you have ever tried go lang, which I recommend you should do. I know you love your C++ but c'mon, there are other languages and technologies out there.
  4. Could you please elaborate on what kind of bugs you think are possible with such approach to variable declaration?
  5. Hi Andreas,   thanks for your continued work on the wonderful language!   I have recently gotten my feet considerably wet with Golang and have found some of its features pretty cool and useful, multiple return values and short variable declarations to name a few. Now I would consider the former to be somewhat more difficult to implement than the later, which seems to be a little more than syntax sugar for the 'auto' declaration.   Is there a chance you would consider implementing some of these features in AngelScript? Now I'm aware your TODO list is already miles long but I figured I'd ask you anyway :)   Best regards, Victor
  6. It's pretty much the same with CreateSemaphoreEx:   http://www.warsow.net/forum/thread/t/223185#post-223185
  7. Confirming as the issue as fixed. Thanks!
  8. void item_weapon( Entity @ent ) { if( (ent.spawnFlags & WEAPON_ROCKET) == WEAPON_ROCKET ) { if( (ent.spawnFlags & WEAPON_BIG) == WEAPON_BIG ) GENERIC_SpawnItem( ent, AMMO_ROCKETS ); else GENERIC_SpawnItem( ent, AMMO_WEAK_ROCKETS ); } else if( (ent.spawnFlags & WEAPON_SPIKES) == WEAPON_SPIKES ) { if( (ent.spawnFlags & WEAPON_BIG) == WEAPON_BIG ) GENERIC_SpawnItem( ent, AMMO_PLASMA ); else GENERIC_SpawnItem( ent, AMMO_WEAK_PLASMA ); } else if( (ent.spawnFlags & WEAPON_SHOTGUN) == WEAPON_SHOTGUN ) { if( (ent.spawnFlags & WEAPON_BIG) == WEAPON_BIG ) GENERIC_SpawnItem( ent, AMMO_SHELLS ); else GENERIC_SpawnItem( ent, AMMO_WEAK_SHELLS ); } } Basically, each '(ent.spawnFlags & WEAPON_ROCKET) == WEAPON_ROCKET'-style comparison throughout the source code results in compilation error.   WEAPON_ROCKET again is an enum, spawnflags is an integer property.
  9. Hm, after updating to WIP Angelscript version, I get loads of the following errors:
  10. Andreas,   are there any plans to incorporate this into 2.28.2? The patches have already started to bitrot...     Best regards, Victor
  11. Thank you :)
  12. Hi Andreas,   did you have the chance to look into the problem? I know it's kinda minor but still rather annoying :)
  13. ok, thanks!
  14. Hi Andreas,   here I am again with another question :)   The following code produces a warning which says "Implicit conversion changed sign of value":         if ( ( G_PointContents( spawn.origin ) & CONTENTS_NODROP ) != 0 ) ...   G_PointContents's declaration is:   int G_PointContents( const Vec3 &in origin )   and CONTENTS_NODROP is an enum. Changing the line to read:   if ( ( G_PointContents( spawn.origin ) & uint( CONTENTS_NODROP ) ) != 0 )   fixes the warning. Why casting an enum to unsigned int fixes the warning, while G_PointContents is obviously a signed integer?
  15. It appears to me that deleting or inserting an element in collection preceeding the iterator internal pointer should increment or decrement the pointer accordingly. Iterator should also hold reference to the collection and the currently pointed element too if it's refcounted. Nothing else has come to my mind so far.