Develop Your Plan (Savage) - Revision history

Rob: Develop Your Plan (Skeleton) moved to Develop Your Plan (Savage)

2008-12-18T04:16:48Z

Develop Your Plan (Skeleton) moved to Develop Your Plan (Savage)

← Older revision	Revision as of 04:16, 18 December 2008
(No difference)

Rob at 01:35, 17 December 2008

2008-12-17T01:35:10Z

← Older revision		Revision as of 01:35, 17 December 2008
Line 25:		Line 25:
	===Look and Feel===		===Look and Feel===

	~~?????????????????????????????????????????????????????????????????~~		Now take some time to evaluate how everything will behave for the user. The overall organization of the interface is critical to highly usable data files, such as what gets presented, how and where it gets presented, and how the user is allowed to make appropriate selections. Also give some thought to how you'll provide feedback to the user about the characters being created and any errors that might arise.
	visual layout ~~and organization~~
	~~interactive behavior -~~ where to use tables, choosers, menus, etc.		Once you have you have your visual organization and layout mapped out, you can translate that into the mechanisms provided by the Kit. This includes assessing where to use tables, choosers, menus, etc. It also entails determining what the contents of tables will look like and what portals the user will interact with.
	~~add scans~~ of ~~original~~ sketches
			We highly recommend that you sketch out how everything will look on paper. Sketches of each tab and how the information will be organized on each are invaluable. For some tables, additional sketches of the contents of each item in the table are also extremely helpful.

	===Visual Skins===		===Visual Skins===

	~~?????????????????????????????????????????????????????????????????~~		The last planning step is how you intend to visually "skin" the interface. The skin is the set of colors, fonts, textures, icons, and bitmaps that comprise how everything looks to the user. We highly recommend you defer any work on the skin until after your data files are otherwise completed. Once you have all the core behaviors operating correctly, you can switch your attention to the skin details. That being said, though, it is always a good idea to give a little thought to how everything will look at the outset, just in case there are layout implications due to your intended final look that need to be considered along the way.
	colors
	fonts
	~~graphics -~~ textures, ~~buttons~~, ~~icons~~

Rob at 01:16, 17 December 2008

2008-12-17T01:16:41Z

← Older revision		Revision as of 01:16, 17 December 2008
Line 7:		Line 7:
	===Implementation Strategy===		===Implementation Strategy===

	The first thing you need is to figure out how you are going to go about developing your data files. We've provided you with a solid starting point in the Skeleton data files.		The first thing you need is to figure out how you are going to go about developing your data files. We've provided you with a solid starting point in the Skeleton data files, and now those files need to be adapted. The sequence used for the Savage Worlds data files leverages a methodology that has worked well for a number of game systems. You are welcome to come up with your own approach, as there is no "right" way to do it, although we recommend you start with the methodology we've presented and adapt it to suit your needs.
	~~That manual outlines a proven methodology~~ for ~~creating~~ the data files for a ~~new game system. This document you are now reading leverages the outlined strategy for the Savage Worlds~~ game ~~system~~. You are welcome to come up with your own approach, as there is no "right" way to do it, although we recommend you start with the methodology we've presented and adapt it to suit your needs.

	===Building Blocks===		===Building Blocks===

	~~?????????????????????????????????????????????????????????????????~~		Take the time to look '''''closely''''' at the game system for which you are developing data files. There are probably lots of subtle facets of the rules mechanics that you take for granted, but that will introduce complexities in writing the data files. In some cases, you will uncover holes in the wording of the rules that the game designers didn't intend. When you embark on writing data files for a game system, you have to tell HL exactly how things work, with none of the grey areas that the human brain adapts to so well.
	components and ~~compsets~~
	~~entities~~		Put together an outline of all the various building blocks for the game system. Map these pieces to the corresponding mechanism for representing each piece via the Kit. Also look at the various supplement books for the game system to get a concrete grasp of the new wrinkles introduced in those books, then figure out how those will impact your initial outline. When you're done, you should have a detailed outline of the various game system elements and a good idea of how you're going to manage them within HL.
	~~things~~
	tag groups		The following is a list of some of the key Kit mechanisms to focus on during this process:
	~~phases~~ and evaluation cycle
			*components and fields
			*component sets
			*tag groups and tags
			*phase and evaluation cycle
			*entities

	===Look and Feel===		===Look and Feel===

Rob: New page: {{context|Authoring Examples|Savage Worlds Walk-Through}} ===Overview=== Before writing any data files, it's critical that you first do your homework. If you launch into writing the data...

2008-12-17T00:59:12Z

New page: {{context|Authoring Examples|Savage Worlds Walk-Through}} ===Overview=== Before writing any data files, it's critical that you first do your homework. If you launch into writing the data...

New page

{{context|Authoring Examples|Savage Worlds Walk-Through}}

===Overview===

Before writing any data files, it's critical that you first do your homework. If you launch into writing the data files without a good plan, you will likely run into a number of surprises and setbacks along the way. While such events won't stop you from successfully creating the data files, they will almost certainly cause unnecessary delays and frustration. So you will fare best if you take the time upfront to develop your basic implementation strategy, map out all of the basic building blocks you'll need, and design how everything should look and behave for the user.

===Implementation Strategy===

The first thing you need is to figure out how you are going to go about developing your data files. We've provided you with a solid starting point in the Skeleton data files.
That manual outlines a proven methodology for creating the data files for a new game system. This document you are now reading leverages the outlined strategy for the Savage Worlds game system. You are welcome to come up with your own approach, as there is no "right" way to do it, although we recommend you start with the methodology we've presented and adapt it to suit your needs.

===Building Blocks===

?????????????????????????????????????????????????????????????????
components and compsets
entities
things
tag groups
phases and evaluation cycle

===Look and Feel===

?????????????????????????????????????????????????????????????????
visual layout and organization
interactive behavior - where to use tables, choosers, menus, etc.
add scans of original sketches

===Visual Skins===

?????????????????????????????????????????????????????????????????
colors
fonts
graphics - textures, buttons, icons