Skip to Content

Newsfeeds

Webfactory

New Drupal Modules - 16 March 2015 - 2:59am

This module aims to extend Drupal 8 multisite capabilities.

Categories: Drupal

Hot Button: Mechanical Transparency

Gnome Stew - 16 March 2015 - 12:00am

During my last session one of my players was trying to pick between two powers to use against a foe and, in the process of debating, asked me what he needed to hit. Without thinking I blurted out the number. I was caught off-guard; normally I don’t share those things, and I was pretty upset about it (more with me for responding without thinking than with him for asking).

I was upset because I like to keep the players guessing. I don’t like to let them know exactly what they need to succeed; if they figure it out in play then that’s fine, but otherwise I enjoy keeping them in the dark, using terms like “you just missed!” or “that shot went really wild” to indicate how close they are to hitting. Similarly, I keep my NPC modifiers secret, in spite of a “no fudging” policy (I go back and forth on “showing the roll”).

By contrast, I usually let my players keep damage tallies for NPCs (not the total health, just how much damage they’ve done). This flies in the face of my “keep them in the dark” policy, as they can observe how much damage opponents take before falling (would they really remember if they weren’t keeping totals?), but I prefer the ease on my bookkeeping more than the integrity of keeping them in the dark.

So how about you? Do you worry about mechanical transparency? Do you keep your players in the dark at all times or do you simply hold off transparency until, for example, the initial encounter is over? Or are you the type of GM that gives out mechanical information at the outset?

Have you ever taken mechanical obfuscation to extremes? Have you, for example, refused to tell players how much damage their characters have taken (restricting info to “you took a solid hit” or “you don’t think you’ll survive another blow”)? Have you kept modifiers hidden (i.e. “your magic sword gives off a minor blue glow”)?



Categories: Game Theory & Design

Fuzzy Thinking: He Keeps Going and Going ...

RPGNet - 16 March 2015 - 12:00am
Fuzzy Wars!
Categories: Game Theory & Design

The Sound Design of inFamous Second Son: Concrete Powers - by Rev Dr Bradley Meyer

Gamasutra.com Blogs - 15 March 2015 - 10:02pm
Rev. Dr. Bradley D Meyer, audio director at Sucker Punch, recounts how the concrete powers of inFamous Second Son were conceived and recorded.
Categories: Game Theory & Design

Interactive Game Music of LittleBigPlanet 3 (Concepts from the GDC Talk) - by Winifred Phillips

Gamasutra.com Blogs - 15 March 2015 - 10:02pm
On Fri. March 6th I gave a talk called "LittleBigPlanet 3 & Beyond: Taking Your Score to Vertical Extremes." Some audience members said the section on the Pod Menu music of LittleBigPlanet 3 was particularly interesting, so let's expand on those concepts.
Categories: Game Theory & Design

Monday Morning Game Design I - by Tom Nietfeld

Gamasutra.com Blogs - 15 March 2015 - 10:02pm
Weekly Game Design Blog. Part I
Categories: Game Theory & Design

Puzzle design through forecasting and assumptions - by Roy van de Mortel

Gamasutra.com Blogs - 15 March 2015 - 10:02pm
This write-up is about how I used the player’s expectations about the puzzle platform genre to create puzzles with the aid of some examples from Metrico.
Categories: Game Theory & Design

GDC2015: A week of infinite awesomeness - by Richard Atlas

Gamasutra.com Blogs - 15 March 2015 - 10:02pm
We made it back from GDC alive and well, having learned a trillion things. I wanted to share some of my post-GDC thoughts with you, and hear yours in the comments.
Categories: Game Theory & Design

Is “Apple Compliant” the same as “COPPA Compliant”? - by Roy Smith

Gamasutra.com Blogs - 15 March 2015 - 10:02pm
Fresh off the plane from GDC, I'd like to cover something I heard for the first time at the show. Several game developers I spoke to described their games as being “Apple Compliant”. What does that mean? And is it the same as being COPPA compliant?
Categories: Game Theory & Design

Marketing Channels for Indie Devs: A Crash Course - by Taylor Bair

Gamasutra.com Blogs - 15 March 2015 - 10:02pm
Let's face it, some marketing avenues aren't suited for indie developers. They either waste our time or precious money and give nothing in return, as one developer found out. So which are worth pursuing so we can get back to development? We rate them.
Categories: Game Theory & Design

5 Motivational Truths Every Game Developer Must Know - by Daniel Doan

Gamasutra.com Blogs - 15 March 2015 - 10:02pm
You're tired and miserable. You've stayed up until 5AM trying to figure out why your build keeps crashing. The last thing you want to do is continue working on your game. You're barely making any progress, and you're struggling to stay focused.
Categories: Game Theory & Design

How to create an addictive puzzle game? - by Antonina Tkachuk

Gamasutra.com Blogs - 15 March 2015 - 10:02pm
We often dedicate our free time to games, and puzzle (match-three in particular) are among the most popular ones. Have you ever wondered what makes them so addictive?
Categories: Game Theory & Design

The relation between videogame preferences and career interests - by Wai Yen Tang

Gamasutra.com Blogs - 15 March 2015 - 10:02pm
The study examined if there is a relation between video game preferences and career interests.
Categories: Game Theory & Design

First time publisher, long time player - by Gilan Israel

Gamasutra.com Blogs - 15 March 2015 - 10:02pm
I'm starting this blog to keep track of and share my experiences as a first time game publisher. I've been playing and trying to write computer games for more than 25 years, and I finally published a complete game last week.
Categories: Game Theory & Design

Drupal core announcements: Drupal core security release window on Wednesday, March 18

Planet Drupal - 15 March 2015 - 9:12pm
Start:  2015-03-18 (All day) America/New_York Online meeting (eg. IRC meeting) Organizers:  David_Rothstein

The monthly security release window for Drupal 6 and Drupal 7 core will take place on Wednesday, March 18.

This does not mean that a Drupal core security release will necessarily take place on that date for either the Drupal 6 or Drupal 7 branches, only that you should prepare to look out for one (and be ready to update your Drupal sites in the event that the Drupal security team decides to make a release).

There will be no bug fix/feature release on this date; the next window for a Drupal core bug fix/feature release is Wednesday, April 1.

For more information on Drupal core release windows, see the documentation on release timing and security releases, and the discussion that led to this policy being implemented.

Categories: Drupal

Google Sitelinks Search Box

New Drupal Modules - 15 March 2015 - 9:37am

With Google Sitelinks search box, people can reach your content more quickly from search results. Search users sometimes use navigational queries—typing in the brand name or URL of a known site—only to do a more detailed query once on that site. For example, suppose someone wants to find that video about the guilty dog on YouTube. They type YouTube, or you-tube, or youtube.com into Google Search, follow the link to YouTube, and then actually search for the dog video.

Categories: Drupal

Chris Hall on Drupal 8: D8 blog Alpha to Beta migration

Planet Drupal - 15 March 2015 - 8:08am
D8 blog Alpha to Beta migration Sun, 03/15/2015 - 15:08 chrishu Still running on Drupal 8

Somewhat shocked to find that I have been running on Drupal 8 for well over 1.5 years now, not surprisingly the sense of urgency has kind of dropped off, but getting back into Drupal 8 again now. This site was originally based on Alpha 3  D8 and I even tried 'chasing head' for one iteratation, so it was alpha 3 with some crazy ass fixes.

Then I got a bit experimental, customised a couple of things etc. and fixed the brokeness that kept happening. Utimately as I focused on it again (whilst having experimented a little on dev site with Beta 3 in preparation for migration), I touched something and it went poof! I am somewhat used to the white screen of death on this site even the white screen of death that doesn't fix itself when you rollback the database, this time I didn't want to roll up my sleaves and attempt a fix, as far as I was concerned my site was the Norwegian Blue Parrot of Drupal installs.

Note: if working on a non-supported version of D8 kittens don't die if you hack core, in fact coping with Drupageddon etc. they are more likely to die if you don't.

Alpha to Beta problem, Mysql to the rescue

A quick assessment of options, I could look at the migration code already in D8 and attempt something but two things stopped me, firstly I have spent a lot of time working on D6 - D7 and D7 - D7 migrations recently and great though it is I am sick of it, secondly I needed something really quick, I had very little spare time over the next week, I slapped up a new site on a shiny new Ubuntu 14.04 VPS and posted a page to explain what was going on. 

More annoyingly for speed I need content to have the same node ids etc. not having any automated path functionality I had too many /node/{nid} urls already.

It turns out that the thing that has changed the least over the intervening time is the database structure (well there are some important differences but nothing that cannot be fixed on the fly). When I got some time a couple of beers and the following strategy:

  1. dump the orginal site from Mysql.
  2. prefix all the tables from the original alpha site with prefix (eg. in my case 'node' became 'rr_node'.
  3. load the alpha site tables into the beta site database (they are just ignored and do no harm).
  4. copy a dev version of the site and move the data from the alpha tables to the beta tables, making changes as needed.
  5. move the dev version to live.

It worked a charm (although at the point of writing this I still have to do the comments, I was just getting bored). A few hours effort in total to get the old content into the new site.  Nice to see that the database tables are pretty clean and fairly easy to interpret by eye if all else fails.

Some Mysql pointers

To replicate this approach you need to be able to fire up a Mysql client and be pretty comfortable looking around moving data around. A few things that may help follow.

You can wildcard show tables. show tables like '%node%';  will show you node related tables for example.

You can view the structure of a table with describe  eg. describe node;

Tables that have the same structure are very easy to populate insert into url_alias select * from rr_url_alias; tables where the structure varies (missing fields, field in a different order etc.) require the fields and field order to be specified insert into node_field_revision (nid, vid, langcode, title, uid, status, created, changed, promote, sticky, default_langcode) select nid, vid, langcode, title, uid, status, created, changed, promote, sticky, default_langcode from rr_node_field_revision;

Language codes have to match, my old database was full of 'und' the new one needed 'en'

Revisions are better flattened, a lot of the complication in folding the two structures together are around revisions, I did have revisions in my original alpha site (not because I needed them, just to kick the tyres). It was much easier to flatten the revisions, in simple tables just making vid = nid or revision_id = entity_id does the job BUT in tables like field tables where multiple revisions are tracked for the same entity you want to delete all the older revision and then keep the last one matching the revision_id to entity_id as appropriate. Drupal then just sees the content as having one revision and the last change will match the state as the last revision you had previously.

Give me a shout if you need help

I appeciate all the above is a bit holistic, as I said it took a few hours and a couple of beers from start to finish and was fairly hacky (I was cooking a meal at the same time etc.) I had no time to compile a structured migration guide (which may be different for your particular version of the site anyway), if you are confident with Mysql then a content migration (included taxonomy terms, etc etc. ) is a very feasible way to get ancient D8 content into a new spanking new D8 Beta and I FEEL GOOD

Happy to chip in if anyone else needs a hand.

Looking forward to trying out themeing now I have an up to date Drupal 8. 

Blog tags Comments Add new comment Your name Subject Comment About text formats Restricted HTML
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd> <h4> <h5> <h6>
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.
Leave this field blank
Categories: Drupal

DrupalOnWindows: Benchmarking Drupal 7 on PHP 7-dev

Planet Drupal - 15 March 2015 - 7:58am
Language English

There are big expectations surrounding PHP7.

PHP has seen the threat and needs to keep up with competitors such as HHVM or the recently open source and cross platform compatible .Net Framework. Even a while ago (2011) the .Net implementation of PHP (Phalanger) already was light years superior and much better performant than Zend Engine, and was proposed as a replacement of the Zend Engine (read the full story here).

More articles...
Categories: Drupal

Work days

New Drupal Modules - 15 March 2015 - 12:28am

This module provides field with calendar. You can fill work days for your organization or active days for your event.

Dependencies
This project using library MultiDatesPicker
and requires module jQuery Update

Categories: Drupal
Syndicate content


Google+
about seo