CleverNickName
Limit Break Dancing (He/They)
*quietly places his M40 back into its case*That was a sniper taking me out.
I just accidentlied all over the new HIVE! lol
- Thread starter Relique du Madde
- Start date
CleverNickName
Limit Break Dancing (He/They)
True, the art is downright beautiful...much better than what has been coming out of Hasbro lately, IMO. And the Combat Maneuver system, where you use the same simplified mechanic for all kinds of special combat moves like grappling and tripping and whatnot? It's smooth like butter.No, not by a far shot... But, maybe we just put priority into different things... Now the art I've seen, if it's as good in the whole book, I'm willing to dish out the cash... Once I have enough to spend
It's just that the skill system in 3.x had frustrated me for so long...so when Pathfinder showed me a better way to handle it, well, I sort of fell in love. Once I saw that streamlined, condensed list of skills, I knew that the two of us would be very happy together.
Aeson
I am the mysterious professor.
While not clear on the method I was aware of the result. But instead of you it'd be me.That was a sniper taking me out. You know like a Monty Python type of sketch along the lines of how not to hide, but instead of hiding you blow up when ever your about to say something vital.
Aeson
I am the mysterious professor.
The class changes were nice. I've always like wizards and sorcerers. A bump in hit dice is always welcome. Druids get wildshape sooner and can use it more often. A perception skill to replace spot, search and listen is good.
I have all of my Pathfinder books with me here at work if anyone has questions I can look stuff up.
Druids get wildshape sooner and can use it more often. A perception skill to replace spot, search and listen is good. I have all of my Pathfinder books with me here at work if anyone has questions I can look stuff up.
CleverNickName
Limit Break Dancing (He/They)
*quietly removes his M40 from its case*
Blackrat
He Who Lurks Beyond The Veil
CleverNickName
Limit Break Dancing (He/They)
Relique du Madde
Adventurer
A fun show to watch is Locked n Loaded on the History channel. Nothing is more awesome then watching a 60 year old ex-marine talk about weapons, especially when they get a psychotic gleam in their eye as they are doing it.
Last edited:
Mustrum_Ridcully
Legend
Haven't been a while here, too.
I am also more the laid back type. Take it from Picard - listen to the others and than decide the approach.
Figure out where you (or the class teacher or whatever) wants to go with your project, and how you want to do it.
Decide on teams, on iteration steps you take (these steps might include figuring out where you want to go next or if you are still going the expected route or the destination has changed.)
Try to estimate how long individual tasks get (which should first be done by those that are planning to do). They will be off. You will be off. That's okay. Compare expectation and reality, and use that to improve your estimates.
It is important to organize tasks in smaller chunks. The more complex a task is, the worse it will be defined, the harder it will be to achieve it, and the higher will be the difference between expectation and reality. (Hint: Any task usually take longer than expected, not shorter.)
Organize your teams discussions. Either moderate them yourself or set someone to moderate them. Only one persons should speak at a time, and if two people want to speak at the same time, figure out the order in which they get to speak. (By the way: I think it's a good thing when you need to do this often - it's a sign for motivation). If no one has to say anything, you need to bring up questions.
In software development, having two people (pair programming, extreme programming) work on one task has shown good results. I don't think that is limited to software development. You need someone to bounce ideas off, someone that questions your approach or someone that helps you when you are stuck. But if the team is too large, you will quickly run in circles and not achieve anything (especially without a moderator).
Another technique are short (typically daily) meetings (typically done standing) where everyone quickly presents what he did (and any issues that still need resolving) and what he will do until the next meeting.
Generally it's good to have a good "feedback loop". Regularly giving feedback enables people to see if they are still on track and allows you to correct mistakes and address. But at the same time - don't let it become "micro-management". Trust that people do their job and don't move your targets around.
You know wrong.
I am also more the laid back type. Take it from Picard - listen to the others and than decide the approach.
Figure out where you (or the class teacher or whatever) wants to go with your project, and how you want to do it.
Decide on teams, on iteration steps you take (these steps might include figuring out where you want to go next or if you are still going the expected route or the destination has changed.)
Try to estimate how long individual tasks get (which should first be done by those that are planning to do). They will be off. You will be off. That's okay. Compare expectation and reality, and use that to improve your estimates.
It is important to organize tasks in smaller chunks. The more complex a task is, the worse it will be defined, the harder it will be to achieve it, and the higher will be the difference between expectation and reality. (Hint: Any task usually take longer than expected, not shorter.)
Organize your teams discussions. Either moderate them yourself or set someone to moderate them. Only one persons should speak at a time, and if two people want to speak at the same time, figure out the order in which they get to speak. (By the way: I think it's a good thing when you need to do this often - it's a sign for motivation). If no one has to say anything, you need to bring up questions.
In software development, having two people (pair programming, extreme programming) work on one task has shown good results. I don't think that is limited to software development. You need someone to bounce ideas off, someone that questions your approach or someone that helps you when you are stuck. But if the team is too large, you will quickly run in circles and not achieve anything (especially without a moderator).
Another technique are short (typically daily) meetings (typically done standing) where everyone quickly presents what he did (and any issues that still need resolving) and what he will do until the next meeting.
Generally it's good to have a good "feedback loop". Regularly giving feedback enables people to see if they are still on track and allows you to correct mistakes and address. But at the same time - don't let it become "micro-management". Trust that people do their job and don't move your targets around.
CleverNickName
Limit Break Dancing (He/They)
I don't know if anyone is interested, but there is a slot available in the Iron DM 2009 competition. We had a last minute cancellation, and there weren't any alternates signed up.
I've never competed before, but it sounds like a lot of fun. You have 48 hours to create an adventure, using a list of ingredients. It's a single-elimination tournament, and the DM who makes the most original, interesting, and entertaining adventure advances to the next bracket.
At the very least, it's a virtual gold mine of free adventures.
Sign up here. Or just stop in to watch the madness.
I've never competed before, but it sounds like a lot of fun. You have 48 hours to create an adventure, using a list of ingredients. It's a single-elimination tournament, and the DM who makes the most original, interesting, and entertaining adventure advances to the next bracket.
At the very least, it's a virtual gold mine of free adventures.
Sign up here. Or just stop in to watch the madness.
Similar Threads
