9/23/20

Storium Basics: Creating A Character / Applying For Games

Welcome back to Storium Basics. This series of articles is designed to help new players understand Storium in general, and be able to get started on Storium games. For those looking for more, see my more advanced article series, Storium Theory.

Today, we're taking a look at the first thing a player will need to do to get involved in a game: creating a character.

Once you've found a game that you'd like to join, whether through the Browse Games feature, the forums, or some other method, what should you expect to happen, and what should you do?

First, a bit about how narrators set things up:

The system a lot of narrators - myself included - will use for open invitation games is to take applications up until about the end of the default two week application period, then look over all the applications and choose the ones they feel will work best for their game. They'll certainly comment on applications before that point and will let you know if the character just outright doesn't work, but you often won't hear a definitive yes or no until the application period nears its end.

There are exceptions, of course - sometimes your character is just so clearly right for the game that they take it right away, or of course sometimes you're specifically invited to a game—but that's how that style works.

Note that some narrators also use the "Open Lobby" feature of Storium or forum topics to let players discuss character options and ask questions in a place specifically set aside for the game as well - I tend to just take applications, myself, but a lot of narrators love using that feature and if one does, you should certainly feel free to ask questions there! Even if they don't, you can usually ask questions via private messaging. Make sure that you understand the world and the game concepts if you're fuzzy on anything.

Remember, though - whether you are talking to the narrator in the Open Lobby, on the forums, through private messaging, or through any other method, do not construe the narrator saying that it is all right to apply with a particular character as the narrator saying that they will definitely approve a particular character. Narrators will often be willing to help you work through applying for a character or iron out a character idea, but until they actually hit "approve" on your character application, you do not have their approval.

Now...how do you actually apply?

I look at Storium applications as…kind of a job application, honestly. A fun one, but still, the idea as a narrator is to pick out people you're willing to be writing with for potentially several months to a year - these games can last a while, even if they sound short to begin with. You want to get a cast of characters that seems like it can work together, and do your best to pick a group of players that seems like it can gel pretty well.

It's in your interest as a player applying for games to look at things from that perspective too. You need to sell both your character and yourself - your character as an interesting element for the story, and yourself as a player who will be active, reliable, and easy to work with.

So, here are a few things I've found can help you be more likely to be accepted for a game:
  • Provide a character picture.
    • Narrators like to see those—it helps show that you've thought about the character more, and honestly just gives a good "at a glance" for the character's appearance and general mood or theme. 
    • Don't worry about getting this exact, necessarily - you don't need to go build your character in an art program or get it commissioned or anything. 
    • There was a good forum topic a while back where someone - I forget who - said that he looked at it as kind of "casting the part" as though this were a movie or some such - he looked less for an exact appearance match and more for a picture that fit the general mood and tone of the character.
    • If you cannot provide a picture for your character - for instance, one player I play with is blind and therefore cannot - then just make sure to state that you could not in your comments along with the application. Narrators will generally be understanding, but it's important to let them know that there was a reason.
  • Card art isn't as required, generally, but do pay attention if the narrator specifically asks for it. Narrators don't like having their instructions ignored.
  • Take some time on the background - you don't have to (in fact, you shouldn't) spell out every detail of a character's life, but there should still be a perception that you know, in general, who the character is.
  • Involve your character in the world. 
    • If the narrator calls out particular kingdoms or locations or tribes or what-have-you, consider having your character be from one of those places, or having run into people from those places. 
    • If he mentions events, particularly disastrous ones, consider having those events influence your character's background.
    • Above all, try to fit your character into the game's world and the game's tone or mood, or be ready to explain why your character can still fit the game despite the differences. Characters that clash with the game's tone or world can sometimes work, but they will make narrators skittish - it is on you to explain how your character can still fit the game.
  • A lot of players will submit characters they played elsewhere, and that's totally fine - I've done it myself with old MUX characters or tabletop characters - but make sure to make that character fit into the story's world all the same, likely with the above methods.
  • You don't have to be perfect (though there are some sticklers for grammar rules on Storium that will say otherwise), but do take the time to do what you can to make your writing clear. 
    • In particular, split your background up into paragraphs (and when you do, hit enter twice to clearly separate them - believe me, it makes it so much clearer). It makes it easier to read, and narrators like to know that they're going to have an easy time reading your posts.
    • Take a little extra time with your app - and with your writing on Storium in general. Again, you don't have to be perfect. Just make it clear that you do care about your writing.
  • Put things into your background that the narrator can use. You don't have to spell them out as bullet points or anything, but characters that provide the narrator with possibilities are more exciting than those who just are what they are. 
    • Leave some mystery in there, or imply that a person that hurt you was involved with some evil force or another the narrator established in the game description.
    • Narrators, by and large, love to have little cues that they can find in a character's description or background. It helps them involve the character more in the story, and make the story about the characters, rather than about events that the characters happen to be involved in.
    • This is a good thing to use comments for as well - when you submit your character and that little box comes up with additional comments, take the time to just briefly talk about some ideas for how the character might tie in to the story, or call out bits in your application that you've intentionally left open for the narrator to use.
  • Take a look at the other existing apps and try to make your character feel different. 
    • If other people are choosing a particular nature, strength, weakness, or subplot, it's a good idea to pick a different one. Storium may not have a tactical need to have different "classes" in your party, but narrators like to have characters that are different from each other. 
    • Work on differentiating Strengths, Weaknesses, and Subplots as well. A game with three people who all have Agile as their Strength card is simply not as fun to read as a game where those three people have different Strength cards. There are definitely story possibilities with overlap, but most narrators I've seen will prefer characters that differ over those that are similar.
  • Write your character as someone who can and will get involved with the story and the other characters. 
    • Characters who feel like they'll want to be separate from the rest of the group a lot of the time (loners, "I work alone" types), or those who feel like they won't care about the story or will actively act against the story (for instance, a totally sensible character in a slasher flick game, who won't go to explore the creepy old house) will make the narrator nervous. 
    • Remember: You are writing a character for this story. Your character doesn't have to be fated to be a hero or something like that. He doesn't have to be thrilled about what he's going to be doing. But, deep down at the very least, he should be the sort of person that will pursue the activities the story demands.
    • If your character appears to be the sort of person who would run screaming in the other direction from the events of the story or otherwise avoid participating in it, take the time in comments to tell the narrator how you'd like to tie the character to the story more firmly - or at least to give the narrator a few ideas for how it might happen. As above, it is on you to explain why a character that doesn't seem to fit can actually fit.
  • Pick the starting cards for your character based on what you want to see come up in the story for that character - not just based on what sounds right for the character. You need to pick starting cards that feel like things that would be interesting to you - things you are going to want to play. 
    • This tends to matter most for Weakness cards, but can also be a factor in choosing a Strength or Subplot. Pick something that interests you and that you want to see as part of the story.
    • I've seen players pick stuff because it "sounded right" or because it was who the character was before the tale, not thinking about where their character's story was quickly going to go and how they actually wanted to portray the character, and it always becomes something frustrating for the player then.
  • Finally, for yourself, try to build a good reputation in general. Narrators can, and do, look at your play history. If they see interesting characters, story participation, group interaction, a good attitude, and completed games, they'll look forward to the possibilities presented by having you in their game.
Narrators aren't professionals and we all work a little differently, and nothing's a guarantee, but the above should generally help you be more likely to be accepted to games, and just help you have more fun and help others have more fun when you're in them.

If you would like to know more about character creation and applying for games in Storium, here are a few of my Storium Theory articles on that topic:

9/22/20

Back? Well, I Never Actually Went Away.


Free Web Site Counter
Free Counter

Blimey, been a long time since I looked at this, lots has happened, both in life and in wargaming.
Anyway, I will be re-visiting this blog. Maybe not as much as I did seven (7!!) years ago, but I feel now it would be fun to do a bit from time to time.
The main reason for not keeping this blog up was that I'd pretty much run out of puff, so, hopefully now I should be able to capitalise on having had a long break to come up with a few things that some folk might be interested in.

Nazis for Big COC currently on the workbench

9/13/20

What The Heck Is Going On?

So, at this point, I'm a week late for a new episode. Don't fear, a new one is coming. Probably next week. I recognize that I've skipped weeks before and haven't ever said why, except perhaps in passing. Normally, it's because I'm off performing my two weeks of annual training for the National Guard. But not this time.

It's like this. I need to get my life to a better place. Mainly with my health, but also my relationship with my wife and kids. I have high blood glucose and I need to get it under control. I've drastically altered my diet and am exercising more. That means earlier mornings, which require earlier nights. That means less time for recording and editing and everything else that goes into making the podcast.

If you're reading this, I assume you're a regular listener. For that I thank you. I owe you quite a bit. For example, I owe you more and better content. It's coming. Exactly what form that is, I don't know.

But back to my main point.

I'm exercising more, eating better, working harder on my Cub Scout commitments (I'm Cub Master for the Pack my son is in), working harder in my National Guard posting (Senior Platoon Trainer NCO for Officer Candidate School), and wanting to do more "hobby stuff." All of this takes time. Unfortunately, all of these things take a higher priority than simply banging out a podcast when it comes due.

Now, there is some cross-pollination in there. It's especially evident when it comes to my National Guard pursuits and my hobby. For example, Henry Hyde will be publishing an article I wrote as a direct result of my recent military education. Additionally, I'll be writing about my experience in planning a staff ride for the Officer Candidates. More on that later. Furthermore, I'm planning more articles for Henry.

As for the hobby stuff, I want to spend more time with my kids. Luckily, they both want to paint figures with me and play more games. Anticipate that generating more content for the podcast and maybe more blog posts here. For example, the projects I'm actively pursuing include:
- A semi-secret Seven-Years War project
- My son's 40k Orks
- A Full Thrust project using Halo ships
- A microarmor game I'm developing with my brother Chris
- Rommel in 3mm
- The Commands & Colors Epic Fantasy (not BattleLore) project (and I might have a writing partner for this one now)
- The space station project I talked about previously for sci-fi skirmish (possibly Oldhammerish)

Lots of other stuff is ruminating as well. What can I say, I'm a gaming magpie from way back. In the meantime, I'm trying to read more history, historical fiction, self-help, US Army doctrine publications and even the occasional hobby magazine!

I'm a busy guy. Part of this little pause has been taken up with some thought, soul searching, prioritizing, planning, and figuring what the hell I'm doing next. Part of that is going to take me becoming more personally disciplined in how I go about things. I've never scheduled "free time" before, but I might have to start.

We're all busy. So, I hope you can understand why I might be late with the podcast. I hope you'll forgive me. One of these days, you might even think what I produce was worth what you paid for it.

That is all.

(218 MB) GTA Vice City Download For Free

(218 MB) GTA Vice City Download For Free




Screenshot



System Requirements of GTA Vice City Free Download

  • Tested on Windows 7 64-Bit
  • Operating System: Windows Vista/7/8/8.1/10
  • CPU: 800 MHz Intel Pentium III or 800 MHz AMD Athlon or 1.2GHz Intel Celeron or 1.2 GHz AMD Duron processor
  • RAM: 512MB
  • Setup Size:218 MB
  • Hard Disk Space:450 MB












9/4/20

I Will Be Speaking At EGLX In Toronto!

#SuzyCube #gamedev #indiedev #madewithunity @EGLXofficial 
EGLX is coming to Toronto from October 26 to the 28th and I will be giving an updated version of the talk I gave in Ottawa for CGX a few months ago! 
Read more »

8/31/20

ATTPwn En El Red Team Village De DefCon 28 Safemode & 8Dot8 Las Vegas

Ya hemos hablado bastante de ATTPwn en este blog. Es el resultado del estudio y análisis que hemos ido haciendo en estos últimos meses de la matriz ATT&CK de MITRE. Una forma de ordenar el conocimiento de las amenazas, a través del uso de tácticas, técnicas y procedimientos. En el mes de agosto hemos estado participando en diferentes eventos gracias al trabajo realizado con ATTPwn, el cual ha dado como resultado la herramienta colaborativa que tenéis en el Github de ElevenPaths.

Figura 1: ATTPwn en el Red Team Village de DefCon 28 Safemode & 8dot8 Las Vegas

Como comentamos en BlackHat, ante algunas preguntas, seguimos actualizando y metiendo funcionalidades la herramienta. Es un esfuerzo importante, ya que la herramienta tiene un gran recorrido y muchas posibilidades a realizar. Es más, pensamos en una API, en un GameScore, en añadir mayor conocimiento y en facilitar la inclusión de la implementación de cualquier usuario dentro de la herramienta. No es un proyecto que nace y muere en breve, es un proyecto para seguir creciendo y sumando. Además, cualquier ayuda en forma de colaboración será bienvenida.

Figura 2: ATTPwn en GitHub
  
El sábado, 8 de agosto, nos tocaba participar en DefCon en un horario muy matutino. Eran las 6:20 de la madrugada hora España y Fran Ramírez y yo estábamos delante del ordenador para poder exponer la conferencia en el Red Team Village. En el horario de Las Vegas, la charla era a las 22.00, por lo que nos tocaba esperar hasta las 7.00 de la mañana, hora España. Sea como sea, encantados de poder estar en uno de los grandes eventos.


Unos días antes estuvimos haciendo pequeños cambios en la herramienta. Por ejemplo, el fichero data.py sufrió algún cambio para evitar que implementaciones futuras de técnicas que estaban en un plan de una amenaza "crasheasen" la ejecución de la amenaza, precisamente por no tener la implementación indicada. 

Como digo es un proyecto vivo en el que seguimos añadiendo funcionalidades e implementaciones cuando podemos, por lo que en algunas ocasiones podemos definir el plan de una amenaza con las técnicas mapeadas del MITRE y no disponer de ningún tipo de implementación todavía.  Alguna idea como integrar Red Atomic en ATTPwn o dar la posibilidad de utilizar ciertas funcionalidades de Atomic Red en ATTPwn pueden ayudar a paliar esto que os comentaba y, por supuesto, enriquecería el proyecto con un marco de trabajo muy interesante, como es el proyecto Atomic Red.

Figura 4: Proyecto Atomic Red

Hace tiempo, ya comenté que hablaríamos algún día de este proyecto en profundidad, porque es algo muy interesante. Esos ficheros YAML y las posibilidades de integración que ofrecen son dignos de estudio. Hasta aquí os puedo leer.


Eso sí, la importancia de crear inteligencia de amenazas mapeadas con la matriz de ATT&CK tiene su importancia, tanto para un Red Team como para un Blue Team. La idea final es que lances esto sobre un activo para verificar que tus controles, es decir, tu inversión en seguridad, funcionan correctamente, es decir, son eficientes y eficaces. 

Defcon 20 Safemode & 8dot8 Las Vegas

Ahora, os dejamos el vídeo de la charla del Red Team Village de DefCon en inglés, en el que podéis ver cómo se adapta el proyecto a la matriz de ATT&CK, la arquitectura de la herramienta, diferentes casos de uso y cómo se puede colaborar con el proyecto, ya que éste último punto es el más importante, desde mi punto de vista. 

Figura 6: ATTPwn en DefCON 28 Safemode Red Team Village

Pronto terminaremos de volver de vacaciones, unas vacaciones merecidas tras este extraño año que nos ha tocado vivir, pero del que seguro podemos sacar lecturas positivas. Al menos, tenemos que hacer ese ejercicio. Cuando parece que todo se acaba, podremos sacar algo positivo y saldremos con más fuerza.

Figura 7: ATPwn en 8dot8 Las Vegas en español

Tras pasar por BlackHat USA y DefCon, nuestro amigo y compañero Gabriel Bergel (CSA de ElevenPaths) nos invitó a asistir a 8dot8 LasVegas. Esta edición especial de la 8dot8 se suele celebrar en una suite del Flamingo en LasVegas, pero en esta ocasión tocó hacerla online. Es una edición para ponentes hispanoamericanos que presentan en BlackHat o en DefCon. Siempre es un placer poder estar con Ragnar y el enorme equipo de 8dot8

Saludos,

Autor: Pablo González Pérez (@pablogonzalezpe), escritor de los libros "Metasploit para Pentesters", "Hacking con Metasploit: Advanced Pentesting" "Hacking Windows", "Ethical Hacking", "Got Root",  "Pentesting con Powershell", "Pentesting con Kali Silver Edition" y de "Empire: Hacking Avanzado en el Red Team", Microsoft MVP en Seguridad y Security Researcher en el equipo de "Ideas Locas" de la unidad CDCO de Telefónica.  Para consultas puedes usar el Buzón Público para contactar con Pablo González

Figura 8: Contactar con Pablo González

Related news


How To Start | How To Become An Ethical Hacker

Are you tired of reading endless news stories about ethical hacking and not really knowing what that means? Let's change that!
This Post is for the people that:

  • Have No Experience With Cybersecurity (Ethical Hacking)
  • Have Limited Experience.
  • Those That Just Can't Get A Break


OK, let's dive into the post and suggest some ways that you can get ahead in Cybersecurity.
I receive many messages on how to become a hacker. "I'm a beginner in hacking, how should I start?" or "I want to be able to hack my friend's Facebook account" are some of the more frequent queries. Hacking is a skill. And you must remember that if you want to learn hacking solely for the fun of hacking into your friend's Facebook account or email, things will not work out for you. You should decide to learn hacking because of your fascination for technology and your desire to be an expert in computer systems. Its time to change the color of your hat 😀

 I've had my good share of Hats. Black, white or sometimes a blackish shade of grey. The darker it gets, the more fun you have.

If you have no experience don't worry. We ALL had to start somewhere, and we ALL needed help to get where we are today. No one is an island and no one is born with all the necessary skills. Period.OK, so you have zero experience and limited skills…my advice in this instance is that you teach yourself some absolute fundamentals.
Let's get this party started.
  •  What is hacking?
Hacking is identifying weakness and vulnerabilities of some system and gaining access with it.
Hacker gets unauthorized access by targeting system while ethical hacker have an official permission in a lawful and legitimate manner to assess the security posture of a target system(s)

 There's some types of hackers, a bit of "terminology".
White hat — ethical hacker.
Black hat — classical hacker, get unauthorized access.
Grey hat — person who gets unauthorized access but reveals the weaknesses to the company.
Script kiddie — person with no technical skills just used pre-made tools.
Hacktivist — person who hacks for some idea and leaves some messages. For example strike against copyright.
  •  Skills required to become ethical hacker.
  1. Curosity anf exploration
  2. Operating System
  3. Fundamentals of Networking
*Note this sites





Related word


8/30/20

$$$ Bug Bounty $$$

What is Bug Bounty ?



A bug bounty program, also called a vulnerability rewards program (VRP), is a crowdsourcing initiative that rewards individuals for discovering and reporting software bugs. Bug bounty programs are often initiated to supplement internal code audits and penetration tests as part of an organization's vulnerability management strategy.




Many software vendors and websites run bug bounty programs, paying out cash rewards to software security researchers and white hat hackers who report software vulnerabilities that have the potential to be exploited. Bug reports must document enough information for for the organization offering the bounty to be able to reproduce the vulnerability. Typically, payment amounts are commensurate with the size of the organization, the difficulty in hacking the system and how much impact on users a bug might have.


Mozilla paid out a $3,000 flat rate bounty for bugs that fit its criteria, while Facebook has given out as much as $20,000 for a single bug report. Google paid Chrome operating system bug reporters a combined $700,000 in 2012 and Microsoft paid UK researcher James Forshaw $100,000 for an attack vulnerability in Windows 8.1.  In 2016, Apple announced rewards that max out at $200,000 for a flaw in the iOS secure boot firmware components and up to $50,000 for execution of arbitrary code with kernel privileges or unauthorized iCloud access.


While the use of ethical hackers to find bugs can be very effective, such programs can also be controversial. To limit potential risk, some organizations are offering closed bug bounty programs that require an invitation. Apple, for example, has limited bug bounty participation to few dozen researchers.
Related word