Character Moves Project

Jide, yeah I can send you the excel file (2007 or compatible mode). Just PM your email address to me.

 

You are right, the data is massive, but is it possible to organize the massive amount of data in a manageable way, without simplifying it too much or making it more complex than it actually is? I think so. Also, /forums/images/%%GRAEMLIN_URL%%/g.gif-cancels, /forums/images/%%GRAEMLIN_URL%%/p.gif-strings, delays...not something one should worry about unless someone commits to doing a move with those options, right?

I don't expect anyone to get much from what has been posted so far. It mostly set things up for the next update. As I have already admitted, it could end up being a complete failure and have no value. But since the Dojo forums is not too active, might as well try and see if the project would be a nice addition to VFDC.

As for how the community can help, I will elaborate when things become more concrete (next update, maybe).

 

If two attacks have the same execution speed, I used damage as the next criteria in sorting the moves. Maybe I should put moves with dash inputs last...

If anybody have a preference on organization, I am open to suggestions.

Only a minor update to set things up again. If you are really curious on what the heck I am planning, click on the spoiler for the long-winded email I sent to Myke last year that go into details of the project. It is very long...so those that don't want to read it just wait for the major update, hopefully in the coming weeks.

<div class="ubbcode-block"><div class="ubbcode-header">Warning, Spoiler: <input type="button" class="form-button" value="Show" onclick="if (this.parentNode.parentNode.getElementsByTagName('div').getElementsByTagName('div')[0].style.display != '') { this.parentNode.parentNode.getElementsByTagName('div').getElementsByTagName('div')[0].style.display = '';this.innerText = ''; this.value = 'Hide'; } else { this.parentNode.parentNode.getElementsByTagName('div').getElementsByTagName('div')[0].style.display = 'none'; this.innerText = ''; this.value = 'Show'; }" /></div><div class="ubbcode-body"><div style="display: none;">To Myke:

This is a lengthy write-up, as I would like to convince you the positive features of the proposed addendum to VFDC outweighs the negatives.



<u>CURRENT FEATURES OF VFDC</u>
First, an overview of the main contents currently available on VFDC and what I think is lacking about those sections.

1) Command Lists – the black book translated frame data with VFDC updates/revisions. This section of VFDC provides the standard move list, relatively easy to print format, and the useful sorting feature. Negative—not much negative with the current command lists. The organization of the move list could be altered to be more intuitive and comprehensive (see flow charts).

2) Wiki Sections — where Wiki authors can write up more detailed, organized VF information. The organization makes it a wonderful general VF reference or encyclopedia for those that do not look at the forum boards on a regular basis. The format also makes it relatively print friendly. Negative—this section is highly dependent on selected Wiki authors time and effort (for example, I have not contributed to the wiki for a while now, doing other things. In addition, there are certain parts of the wiki I don’t feel comfortable working on). At the moment, there are certain sections lacking in content . With time, those sections most likely will be filled out;

3) Forum Boards — where the VF community can freely discuss about the game, gatherings, etc. Negative—the freedom to post anything in the forums, unfortunately, also lead to a lot of noise and makes it difficult to find certain topics of interest if you do not look at the forums on a daily basis.

<u>PROPOSED ADDENDUM TO VFDC</u>
To me, the three listed contents above are great features of VFDC, but lacks “interaction”—they are relatively independent of each other. This brings to what I am proposing as an additional feature to VFDC—“Flow Charts” and “Topics”—in what I hope would be an “interactive” way of combining certain positive aspects of the three current features on VFDC.

1) Flow Charts — this section would basically be the alternate command lists in what I hope would be an intuitive/interactive way to look at a character’s move list. A very rough example of a “Flow Chart” is attached as an excel file. Organization of the flow chart is prioritized by –
a) the situation it can be used
b) action property – high strike, mid strike, low strike, opponent defense dependent moves, opponent attack dependent moves, opponent independent moves.
c) speed of the move
d) strength of the move
Links to and from the topics. For example, Pai’s /forums/images/%%GRAEMLIN_URL%%/p.gif/forums/images/%%GRAEMLIN_URL%%/k.gif/forums/images/%%GRAEMLIN_URL%%/d.gif to Bokutai. Clicking on Bokutai would bring you to the Bokutai section of the Flow Chart or the Topics section of Bokutai. Negative — not print friendly. Designed mainly for computer use. Does not have frame data or other information immediately available.

2) Topics — links to and from the flow charts. This is where the community as a whole can contribute. Basically Topics are single forum topics for each move. The first two posts are reserved to the moderators. The first post is the “Facts” post of the move providing summary of all information that is purely factual, for better or worse. The second post is “Applications” post for a “frequently asked questions section” and suggestive information. Anyone can post in the topics, asking question or discussion specific to the move, application of the move or dealing against the move. Unlike the regular forum boards, these topics will be heavily moderated to keep these topics from being cluttered in the long run. Negative — Similar to the wiki it depends on the VFDC community to be contributing. However, the advantage is that the Topics are already pre-organized allowing the whole community to contribute rather than a select few wiki authors. This also may alleviate some of the redundant threads in the Forum Boards. The Topics section can also be the backbone to complete the Wiki sections.

SUMMARY / OUTLOOK
I am not trying to replace the features currently available on VFDC, but to add new features that can flesh out VFDC. Note, we are all busy people and this email is not an attempt of me asking you or others to take the time to help get the project up and running. What I will be doing for my own purpose is the flow charts first, then the “facts post” for each topic.

The main negatives about the proposed feature is 1) the time required to actually get the core of the Flow Charts and Topics completed, and 2) time required to actually maintain/update it. No estimated time of completing the core of the flow charts and topics, at the moment. Ultimately, this could be a prelude for VF5:R(of course this is assuming the version will be released to consoles outside of Japan).

If this is something you would like to implement into VFDC, great, let me know what I should have to modify, so that It can be adapted for website use. I have no experience on making web pages or how much work it will take to set it up. If this is something you don’t think is suited for VFDC, that is fine with me also. But, if you don’t mind me asking once in a while about formatting once in a while ie, how to get the command input images to replace text code we use? Or if this spurns a new/different way of improving VFDC, I am up to hearing about it (for example, don’t like the flow charts, but like the topics idea…integrate it to the current command lists…).

If you have questions on what the project actually is, please ask. Hope this was not a complete waste of your time and thanks for reading this,

- Akai
</div></div></div>

...if you actually did read the letter: instead of making something entirely new now, I am trying to incorporate the ideas into the Dojo forums and Wiki.

 

Boy, have time passed. Hopefully I will be less busy in the coming weeks to put some additional stuff/tidbits onto the website.

 

I need some opinion on viewing images on this website.

Below are images taken at different parameters. I would like to know what image size (50% or 25%) and quality (high/medium/low) do you prefer to view or have on the website. Also take into consideration of download time of images (smaller image size/lower quality = faster loading).

At the moment, for the forum pages, the "4 frame image" at 50% is too large. For the wiki, it fits (at least on a widescreen monitor). There appears to be very little differences between high/medium/low image quality. Seems only noticeable when there is a strong area of contrast (black Dural getting hit with the jab).

Any suggestions on a different format of the images would be welcomed and appreciated. Thanks.

50% image size/high quality/2 frames

50% image size/medium quality/2 frames

50% image size/low quality/2 frames


25% image size /high quality/2 frames

25% image size/medium quality/2 frames

25% image size/low quality/2 frames


50% image size /high quality/4 frames

50% image size/medium quality/4 frames

50% image size/low quality/4 frames

 

All of the low qual stuff still looks fine, so i'd go with those. I myself prefer the smaller pics. You can still see what's happening, but can fit more pictures on a screen so it's easier to compare stuff.

 

So you actually prefer to have all the images displayed on the same page? My plan was to normally have one or a couple of images at most to be displayed on a page. Would having a downloadable PDF of all the images be of interest?

Nothing is set in stone, so any comments or suggestions are appreciated. But I want to have a good idea of what would be the most useful/intuitive for others before I go formatting all the images for the web. Thanks again.

 

My preference is the 25%/low quality image setting.

Use a single image/frame for the majority of moves, and only a sequence (2 or 3 max) of images for the longer animating ones.

The VF5 White Book could be used as a reference. Refer to these sample scans:
Jacky (1)
Jacky (2)

 

Okay, reduced size, low quality, and 3 frames(images) max per each move.

Second thing, I would like some opinions on: some moves have longer/dramatic animation (compared to a straight jab or kick) that still images (at least to me) are unable to capture. Does having a drawn line/arrow help visualize the move in motion (top example, first image frame) or do you found it not necessary or even more of a distraction than without additional graphic (bottom example, first image frame)?

 

Good! Less work on my part if it is more of a distraction.