OpenBOR Wiki

[Fightn Words]

the community needs and has often mentioned it wanted an OpenBOR wiki...
Now we have one

Yeah, and it has allot of potential for growth & usefulness. We just need more content besides the manuals...

maybe I could update both but it would take more time. Usually I list the updates in a text file. When I edit the page, I find the place to edit or add and copy n paste the updates from that text. I could do the same with this one provided it has same format.

Thats all I honestly did- until you updated the original. Then even using the history it was a little difficult (but not impossible) to figure out where you'd updated it. I would say updating it is more important then formatting, but either way it's still your decision what you decide to do.

[Damon Caskey]

Hey FW, I know you have contributed the majority of the wiki stuff, but I was hoping to ask another small favor.

It needs a logo, and from past experience, you are just the guy to make one. I like the Galford pic, but there is no text or anything else that says "I'm the OpenBOR wiki". Think you might be able to come up with something? The exact demensions needed are 135 * 135. A bit smaller is OK (The Galford pic I stuck in there is), but anything bigger won't work.

Or tell me to get lost. 

DC

[Fightn Words]

I'll see what I can come up with!

[Damon Caskey]

Here is something else I'm going to try doing, and reccomend for anyone adding new stuff to the manual: Including the version number when the feature first came online. It would be ridiculous to try and backlog that, but for new things, why not? Only takes about 10 seconds to do it.

So here is the concept I've been going with:

Command {param1} {param2} - 2.xxxxx

Brief colloquial description of what I do. This is NOT bulleted. In this and every other part of the entry, link to anything in the manual that I mention.

• {param1} (default: 0)
  0 = What 0 means.
  1 = What 2 means.
  
• {param2} (default: Hello)
  What my non list setting will do.
  
• Some truly specific point about the command overall. Use this sparingly so the manual is more of a manual and less of a big checklist.

And here is one right from the manual:
mpblock {bi}

Resource consumed by block damage (see blockratio).

• {bi} (default: 0)
  0 = Block damage is applied to health only.
  1 = Block damage is applied to mp. If mp is insufficient, damage will be applied to health.
  
• This has no effect if blockratio is not active.

[Fightn Words]

Here you are:

[Bloodbane]

I find the DC community version difficult to read, slow, and most annoyingly, it seems to go down about once a week.

 Difficult to read? hmm.... seems fine to me. To be honest, I need to learn using Wiki more. There are probably other commands I could use which I missed.

Besides, the community needs and has often mentioned it wanted an OpenBOR wiki, and some half hearted attempts have been made to get one that quickly got abandoned. Now we have one, and thanks to FW it's off to a solid start.

 Oh yeah, thanks Fight n Words! You make my work easier  .
 Seems like there are couple updates which is not added here. Here's the update text so you can find out what have I added before.

[Damon Caskey]

I find the DC community version difficult to read, slow, and most annoyingly, it seems to go down about once a week.

 Difficult to read? hmm.... seems fine to me.

It's a matter of taste. The use of tilde markers instead of points, little to no bold text, overly colloquial descriptions about the parameters, and lack of indenting is fine for some, but it's just difficult for me to pick out what I need. Compare it to the finished areas in thee wiki (models.txt is done) and I think you can see the difference. But again, it's not a matter of "better" or "worse", it's a matter of personal taste.

The other stuff though is not. For whatever reason, that site is just flat out not stable from a technical standpoint, it's filled to the brim with ads, and it's not controlled by anyone in the community. None of those things is a selling point for hosting something so important when a stable non ad supported host is available.

DC

[Fightn Words]

Oh yeah, thanks Fight n Words! You make my work easier  .

If not for you Bloodbane, our OpenBor manual wouldn't have been updated as often (or even at all), so thank you very much. I'll further update with the stuff I missed.

it's not a matter of "better" or "worse", it's a matter of personal taste.

I personally like the wiki format better, but thats because it's a bit cleaner & more stable (as you pointed out).

Nice job making the graphic transparent DC, I didn't even consider that when I made it.

[Damon Caskey]

Yeah, since the wallpaper has some texture, it would have stuck out a bit to not have a transparent background in the logo. I do think we still need something that sticks out a bit more though. I like the dragon idea you mentioned.

I think really what we need is to get some logo designs for OpenBOR overall going, have the community vote on it's favorite, and then use that for Lavalit/wiki/etc. In the meantime, I have started on cleaning up the Levels.Txt General Settings section. It's slow going, but I think getting everything in a nice format adds enough readability to be worth it.

DC

[danno]

 I could do afew designs, should I post them here?

[Damon Caskey]

Sure, toss em up! That goes for anyone else who wants to try their hand as well.

DC

[danno]

[Fightn Words]

*Ahem* I'm already working on this with SX. Of course, nothing is final, especially the colors.



Danno, I really like the middle example, but not the scan lines.

[Damon Caskey]

I like everything so far (from both of you), but my favorite is the dragon on the far right. Mainly because the visual icon (the dragon) gives it a little something extra, while the white can be made transparent so as not to clash with wallpapers.

DC

[Fightn Words]

It's in a vector format for that reason, so basically you can chose any color(s) you need.