Showing posts with label google. Show all posts
Showing posts with label google. Show all posts

Wednesday, January 11, 2012

Hangout games pt. 1

 So, It's been awhile, but I did promise you at least three game ideas, so here, dearest readers, is number three.

     A lot of people have heard of Google Plus, and may be familiar with one of its big components, hangouts. However, for those of you who are unfamiliar, let me sum it up. Hangouts is a chatroom with video for up to ten people to video chat on, with adaptive screen scaling, and a developer component called Hangouts with add-ons. That's the part that matters here, because it allows web developers to make apps for hangouts. The idea behind my game is to create an add-on that serves as a full blown game, using hangouts to play. My idea is a dungeon crawler, in the fashion of diablo, where the players co-operate to battle through the dungeon, and must solve puzzles in collaboration. The game uses simple action mechanics, walk, fight, and push, like an oldschool adventure game. Think Legend of Zelda: Link to the Past, as far as mechanics, but with ten players running around at the same time. Obviously, It's a lot for developers to work on, because to develop puzzles for that size group, there's a lot of thought involved.
     That's why the second half of the game is based around building. On a website separate from the played game, players will be invited to create dungeons. The computer will assess the difficulty of the puzzles, as well as the enemies, and pay the player for their maps in in-game gold.
I'll focus more on the dungeon builder in my next post, but I wanted to give you a taste of it.
     As far as plot goes, I actually imagine this game as fairly classic. It's an adventure game set in a somewhat steam-powered fantasy world. Swords and sorcery and steam, if you will. There are five types of class: Fighter, Healer, Mage, Thief, and for lack of a better term, a red mage. The fighter, obviously is geared toward combat, healer toward healing, and mage toward magic. The thief has abilities more geared toward status effects, stealing and light damage, while the red mage is a fair balance between magic and fighting. Each character has two assignable attack slots, one for left click, and one for spacebar. The left click would be especially suited for things like arrows, throwing knives, or spells, which would be aim-able via the mouse. While the spacebar would be good for short-range attacks. However, when the player is standing next to a chest, door, person or switch, the spacebar would become the "Action button" allowing them to acivate those things, or to speak to a person.  Movement would be controlled by WASD.
     I think that most of the plot would be devoted to being roving adventurers, saving princesses, defeating monsters and saving villages. However, through the building system, some dungeons could be linked together into campaigns, with full-blown story archs. It would allow people who are drawn to the dungeons and dragons  to create a full story for their friends to play, without having to worry about managing dice rolls and mechanics, since the game will handle all of that already. Players could even divide the task of dungeon building in an arch, so that no player knows all of the dungeons, and everyone could play together.
     As I said earlier, I'll get into dungeon building in my next post. Hopefully you enjoy the concept so far, I have a lot of Ideas for this game, and would love to work with a team to create it.


P.s. If you decided to create this game, please let me know, and please give me credit for the original concept. If someone does make it, I'll do my very best to help you publicize, and I'd even be willing to collaborate, if needed. Thanks!

Tuesday, October 4, 2011

A poem.... er... paragraph?

     So, readers I am working hard on the haunted house, and have a meeting coming up for the Christmas play I am putting up. But for now, no interesting developments on those yet.
Instead, I'm going to share a pinch of fiction I just whipped up.
I read a prompt on Google+ from Lee Shelly Allen, suggesting that I write a poem based on five elements of a T.S. Elliot Play. Those Elements were: 
The Burial of the Dead
A Game of Chess
The Fire Sermon
Death by Water
What the Thunder Said

I completely forgot that a poem was the goal, and accidentally wrote a pair of paragraphs instead. So, here they are!

     The young man clenched the cold rail of the balcony, sliding side to side, and watching the patterns left in the drops of water there. The rain pressed down on him, heavy as the decisions ahead of him. The clouds flashed above him, casting his shadow straight down. the roar of the thunder started him out of his thoughts. He took a moment to view his surroundings. He was a quarter of a mile above the street, looking over the city he now ruled. Another burst of thunder, this time from over the bridge, reminded him of how it had all happened. The bridge was still smoking, dripping rubble and steel from the terrorist bomb that had killed hundreds, including the old mayor. Like so many others, she had died trapped in her car, after the bridge had collapsed, sunken in the river. The young man swirled the water on the rail again, and it made him feel ill.

     He was pulled from his thoughts by a shout from an advisor, calling him inside from the glass door of the balcony. The young man put on a strong face, and walked inside, his suit clinging to his skeleton. He was shuffled into a tall chair by a fireplace, and several advisors began to talk to him, planning the memorial. He tried to listen, tried to show his best side, but he was lost in his head. The flames held his eyes, whispering, “you’re not ready, boy.” They were right, of course, he knew he was too young for what was coming to him. Then the thunder roared again, as if to cry out “nonsense! You are greatness!” He didn’t know what to believe. This job was supposed to be an opportunity, but suddenly, he felt like he was trapped, with crushing pressure around him. The pressure pushed through the windshield, and his lungs filled with water. The fire popped, and he was back in the meeting.

Hopefully you enjoyed that. Also, feel free to follow me on Google Plus!

Wednesday, June 8, 2011

Fixing School Libraries.

     I've spent a couple of days now over the last couple of weeks working with my mother at the library where she works. It's an elementary school library, which means that at the end of the year, most of the work she is doing is handling, cataloging, and storing textbooks. What I've realized while I was helping her is that the entire textbook system is completely ridiculous, and needs to be re-vamped. My brother has written on the subject of the broken education subject HERE, and while I agree that incorporating games into the curriculum is a great way to encourage students to learn, I think that starting with the books they are learning from is the way to go about fixing education. So, here I go.
     Next week, Google is launching its Chromebook, a laptop based on the new Chrome OS. I've been using a Chromebook to update this blog since I started it, and today, it gave me an idea for a complete new infrastructure for books. The basic idea is that Chromebooks operate entirely in the cloud, using only the internet to do its work, rather than depending on built in storage space.
     Every year, the library spends more than $200 per student on textbooks. Now, let's imagine that rather than spending that money every year, the school invested it into Chromebooks, which cost about $200 each. The laptops would be bar coded, inventoried, and checked out, exactly the same as the textbooks, but the secret is that the books would be designed specifically for the purpose of education. Every Chromebook is designed to link to a central server on campus, and on that server is the entire curriculum, every textbook is digitized, the workbooks are webpages, the homework comes in emails, and multiple choice grades itself.  Students would keep their laptops through the course of the year, charging them in class, and if the teacher requires it, using their 8-hour battery overnight for homework time. The Chromebooks are designed with built-in 3G connectivity, which means that students who cannot afford internet at home could register for the 3G through the schools, so they could do homework.
     Two years ago, the elementary school upgraded it's math curriculum, to the latest standards. (I'll talk about the quality of the standards another time) The school had to buy entirely new books for every student they had. If, however, they were using Chromebooks, all the curriculum update would take is the installation of new software on the central server, saving literally tons of paper every time the curriculum is updated. On top of that, the next year, the publisher told the school district that the math they had used for the year wasn't the right set, and sent them an entirely new set of papers! That's another ton of paper wasted, as well as more trouble for librarians! With Chromebooks, if there was a mistake like that, The solution would waste, at most a case of CDs, and at least, nothing, because the update could come over the internet, just like updates on any program on your computer.
     A lot of people worry about students (especially elementary age) being on the internet. That's entirely reasonable, but the Chromebook can be developed to have network controls to keep students on a safe-network, so that the computer can only connect to the school's server. Or, pending parent sign-off, etc. the book could be allowed onto the full internet, or have various levels of parental control allowed.
     Another interesting aspect of the Chromebooks is the centralized login. To log on to Chrome OS, you enter in your Gmail address and password, and all of your information is linked to that. For this system, the students (and teachers, staff, etc.) would each have a login account, which would store grades, homework, bookmarks (literal bookmarks in the e-books, for example) it could have links to a student's favorite educational games attached to the account, or a list of reminders on the home page for upcoming events, or homework. The real advantage of this is that without having to have the student's actual laptop, the parents or teacher of that student can look it up from literally anywhere that there is internet, regardless of whether or not they were using a Chromebook. Students could also use their home computers to do their homework, if one is available. On the other side of that coin, since every laptop is identical, and can all use the same accounts, if a student forgets (or "forgets") their Chromebook at home, the teacher can simply have a few spare laptops in the class. The students can log in and do their work anyway.
     Now, I'm not saying that libraries should be abolished, or that all books should be burned, or anything silly like that. Rather, I'm suggesting that we ditch the business model of replacing books every two years, and only buy books that have a genuine lifespan. If we focused on a system that is built to last rather than being recycled (or sometimes thrown away) every two years, we can focus on the education, and not the money-making. The budget required for books would be cut in half (there would of course need to be some laptops replaced each year) and all of that money could be spent on other things, like after school programs, or art supplies. The Chromebook cloud computing system could make our schools more efficient, less expensive, and more fun for students, and who wouldn't want that?