OpenBoR Manual Updates

[Bloodbane]

 This thread is about OpenBoR Manual.
 Here's the link:

1.  http://dcemulation.org/index.php5?title=OpenBORManual

2.  http://www.dreamcast-scene.com/index.php/Main/OpenBoRManual

 And here's the link to update it:

3.  http://www.dreamcast-scene.com/index.php/Main/OpenBoRManual?action=edit

 Chris post those links previously not me so don't ask me anything about the site.
 I'm going to take part in updating this although I'm not online everyday.
 I'm going to add new features to the current manual but mind you that I don't understand or even tried all features. I hope others can help if someone asks about a feature I don't understand.

 Anyway, anyone who would like to update the manual too please post here your update:

 I'll start with mine:
-Added uTunnels in the credits
-Added 'throwframewait'
-Fixed several stuffs

[CE]

Chris post those links previously not me so don't ask me anything about the site.

Thanks Bloodbane! I always appreciated your participation in keeping everyone else up-to-date about the new features. Your contributions to the Wiki version of the manual are really welcome. 

Sooner or later, SamuraiX plans on mirroring the WIKI over at the OpenBoR Sourceforge page here:
http://sourceforge.net/projects/openbor/

The website hosting the manual currently is www.Dreamcast-Scene.com, a site that tries to cover anything Dreamcast and Sega. I'm staff member over there, mainly focussing on moderating the forums, contributing to the Wiki and doing occassional newsposts.

The WIKI database is freely editable by anyone, so if you want to add infos about Sega stuff or your BoR mod in the Beats of Rage section, please go ahead, you are welcome

At the moment the Beats of Rage section feels a bit 'empty' and does not reflect the importance Beats of Rage does have for the Dreamcast homebrew scene.

Here's a link to the Beats of Rage stub:
http://www.dreamcast-scene.com/index.php/Main/BeatsOfRage

If anyone has questions about how to edit the Wiki or how to upload pictures, links, etc. please do ask and I will try to answer to the best of my knowledge.

[Bloodbane]

OK here's today's update:
-Added 'atchain', 'death' and 'charge'.
-Updated 'attack'.
-Added BDIE,SDIE, ATTACK4, CHARGEATTACK, CHARGE, JUMPCANT and BACKWALK.
-Update ATTACK1,ATTACK2,ATTACK3,PAIN,FALL & DEATH.
-Added some info in JUMP and RUNATTACK
-Fixed mistake in 'bomb'.

BTW Chris any tutorials about how to use Wiki page? I only understand adding and deleting text but know nothing else.

[Bloodbane]

I'm updating the manual again. I'm currently adding Fugue's features excluding the ones which don't work.

[Bloodbane]

 In my mod, ALL grabattacks including grab finishers are unblockable. That solves lots of problem including issues I had with one fake trick I'm using.

 Anyway, as usual I'm updating the manual again today. Well there are too many features to mention so basicly I was adding new features from ver2.0048.
 I haven't added some features from ver2.0051 yet cause I need to understand what it is first.

 After I'm done, I'll update other parts like FAQ.
 Speaking of FAQ, one of the FAQ is about sound problems in playing BoR in Win XP but I heard that latest OpenBoR has solved that issue. Is that true?

[Bloodbane]

 No haven't noticed that since I haven't use weapons yet.

 OK I've inserted new features from ver2.0048 to ver2.0055 in the manual. Not all of new features are inserted though since some of them are buggy and probably I've missed some.

 I would like to ask, what's 'p1smenu - p4smenu' are for? I really have no clue what they are.

[SX]

I would like to ask, what's 'p1smenu - p4smenu' are for? I really have no clue what they are.

Used for customizable player placement in select menu

p1smenu [x,y] [x,y]

1st pair is player position in select menu.
2nd pair is ready! text position in select menu.

example:

p1smenu 100 200 100 220

[Damon Caskey]

Manual updated:

• Added npc to types, follow to subtypes.
• added candamage, projectilehit, and hostile.

[baritonomarchetto77]

- "scomplete" command updated to "showcomplete" in the manual

- for "dive" command, added "Note that a move with dive in it always starts diving at the first frame."

 

[baritonomarchetto77]

since "nograb" have been removed, there is no reason for having  it on the commands descriptions   

so, i have removed it and substituted with "cantgrab" from the description of:

subtype, "notgrab" line

grabattack, first line

throw, first line

[CE]

I deleted my previous post to expand it a little and to answer a question of Bloodbane. - I had not noticed your reply, baritonomarchetto77. ^^

BTW Chris any tutorials about how to use Wiki page? I only understand adding and deleting text but know nothing else.

Here's the PmWiki Documentation at DCS:
http://www.dreamcast-scene.com/index.php/PmWiki/DocumentationIndex

The Review Template has some more basic examples:
http://www.dreamcast-scene.com/index.php/Main/Reviewtemplate

And here's how to implement and upload screenshots:

Type

Img:Name_of_the_image.jpg

within the article you're editing and after submitting your changes, you click on the link to get to the upload center where you can upload your screenshot/cover/etc.

It will be renamed to the name you've given it ("Name_of_the_image" in the example above).

I'm curious, is there any way to split the topics across multiple pages?

It is. When I converted the manual from TXT to Wiki I made the decision to keep it on one page to stay true to Fugue's original work.

Also, a problem when splitting the manual's sections to multiple pages would be that you couldn't use your browser's "Search/Find" function anymore.

Another advantage with the entire manual on one page would be that you also can 'download' the manual in its entirety to your HDD for offline browsing.


However, this is an entirely democratic thing. A possible solution could be to split the less important parts from the main command index of the manual. I am thinking of the (as of yet unfinished) introduction, FAQ, credits, etc. - That way we would keep the commands on one page to keep the browser based search function intact.

What do you guys think ?

[zamuel]

Perhaps there could be the current page with everything on it and another set of pages with the sections split off.  The long page is good for searches but the individual sections would work well for more elaborate examples with multiple links to tutorials and such.

[Bloodbane]

However, this is an entirely democratic thing. A possible solution could be to split the less important parts from the main command index of the manual. I am thinking of the (as of yet unfinished) introduction, FAQ, credits, etc. - That way we would keep the commands on one page to keep the browser based search function intact.

What do you guys think ?

Hmmmm.... maybe we could have main page containing just 'command's. So anyone could search/find certain command easily. This is just like Quicksheet that Fugue also made with the complete manual.

The details of 'command's is placed on another page whose link is the command's group. For instance,

hiscorebg {bi}

is only typed like that in main page. To get the detail of it, browser needs to click "Levels.txt - General Settings". Then a page containing only General settings commands with their details will be entered.

[CE]

I think that's a very good idea Bloodbane

...so I set up an index with what are the sections of the manual and stuff like that + the Quicksheet index, and link from there to the different sections at the manual ? - I think I could try to set up something like that tomorrow. Shouldn't take too long.

The best thing with a Wiki is that if we aren't happy with how it turns out, we could still restore the current version of them manual

[Bloodbane]

 OK, I have fixed some features and added new features. Not all features in Features Archive are added though. I'll add the rest someday.