| 1 |
[size=4]Today, we at Lobster Roll are beginning a new project for the spring RTS community as a whole, which includes Zero-K.[/size]
|
1 |
[size=4]Today, we at Lobster Roll are beginning a new project for the spring RTS community as a whole, which includes Zero-K.[/size]
|
| 2 |
\n
|
2 |
\n
|
| 3 |
https://i.imgur.com/wiZ0706.png
|
3 |
https://i.imgur.com/wiZ0706.png
|
| 4 |
\n
|
4 |
\n
|
| 5 |
We are proud to announce [i]Fightorder[/i], our new community wiki and data repository for projects and games using SpringRTS, as well as the spring engine itself.
|
5 |
We are proud to announce [i]Fightorder[/i], our new community wiki and data repository for projects and games using SpringRTS, as well as the spring engine itself.
|
| 6 |
\n
|
6 |
\n
|
| 7 |
----
|
7 |
----
|
| 8 |
\n
|
8 |
\n
|
| 9 |
[size=4]Why a wiki?[/size]
|
9 |
[size=4]Why a wiki?[/size]
|
| 10 |
\n
|
10 |
\n
|
| 11 |
Currently, many pages on the spring engine have not been updated in quite some time, and trying to find resources for game development using the Spring engine can be quite a task. Additionally, many tools such as springboard are very outdated, clunky, or just hard to use.
|
11 |
Currently, many pages on the spring engine have not been updated in quite some time, and trying to find resources for game development using the Spring engine can be quite a task. Additionally, many tools such as springboard are very outdated, clunky, or just hard to use.
|
| 12 |
\n
|
12 |
\n
|
| 13 |
\n
|
13 |
\n
|
| 14 |
One of our primary goals with Fightorder moving forward will be to perform a [i]complete modernization[/i] of Spring resources and tools moving forwards. While we will not be doing any direct engine improvements, we will be attempting to compile and make resources pertaining to development and tool use easier to find than they are presently. Additionally, our roadmap includes remaking some tools such as springboard for map development and potentially also attempting to create a better way to access springfiles.
|
14 |
One of our primary goals with Fightorder moving forward will be to perform a [i]complete modernization[/i] of Spring resources and tools moving forwards. While we will not be doing any direct engine improvements, we will be attempting to compile and make resources pertaining to development and tool use easier to find than they are presently. Additionally, our roadmap includes remaking some tools such as springboard for map development and potentially also attempting to create a better way to access springfiles.
|
| 15 |
\n
|
15 |
\n
|
| 16 |
\n
|
16 |
\n
|
| 17 |
Considering our goal, it seemed easiest to proceed with using a wiki CMS as our foundation rather than attempt to compile our information in text or PDF form.
|
17 |
Considering our goal, it seemed easiest to proceed with using a wiki CMS as our foundation rather than attempt to compile our information in text or PDF form.
|
| 18 |
\n
|
18 |
\n
|
| 19 |
----
|
19 |
----
|
| 20 |
\n
|
20 |
\n
|
| 21 |
[size=4]Why not use the Zero-K/Spring wiki?[/size]
|
21 |
[size=4]Why not use the Zero-K/Spring wiki?[/size]
|
| 22 |
\n
|
22 |
\n
|
| 23 |
\n
|
23 |
\n
|
| 24 |
While this was a possibility we considered, we have decided to take the approach of creating a new site for a few different reasons. One primary reason is that we simply have a larger scope than would fit on either of those respective wikis, and we think that there is value in consolidating that information for ease of access. Additionally, we plan on doing integrations with our site that extend beyond the capabilities of Zero-K or Spring wiki.
|
24 |
While this was a possibility we considered, we have decided to take the approach of creating a new site for a few different reasons. One primary reason is that we simply have a larger scope than would fit on either of those respective wikis, and we think that there is value in consolidating that information for ease of access. Additionally, we plan on doing integrations with our site that extend beyond the capabilities of Zero-K or Spring wiki.
|
| 25 |
\n
|
25 |
\n
|
| 26 |
Please note that while we are starting off as primarily a wiki, we will add other features later on that expand beyond simple wiki functionality.
|
26 |
Please note that while we are starting off as primarily a wiki, we will add other features later on that expand beyond simple wiki functionality.
|
| 27 |
\n
|
27 |
\n
|
| 28 |
----
|
28 |
----
|
| 29 |
\n
|
29 |
\n
|
| 30 |
[size=4]What are the primary features that are on the roadmap for Fightorder?[/size]
|
30 |
[size=4]What are the primary features that are on the roadmap for Fightorder?[/size]
|
| 31 |
\n
|
31 |
\n
|
| 32 |
Our primary roadmap for the first month or two includes:
|
32 |
Our primary roadmap for the first month or two includes:
|
| 33 |
\n
|
33 |
\n
|
| 34 |
* Scraping and updating all information from Zero-K, Spring, and BAR wikis
|
34 |
* Scraping and updating all information from Zero-K, Spring, and BAR wikis
|
| 35 |
\n
|
35 |
\n
|
| 36 |
* Assembling teams and preparing workflows for tool modernization
|
36 |
* Assembling teams and preparing workflows for tool modernization
|
| 37 |
\n
|
37 |
\n
|
| 38 |
* Finalizing site features and basic implementation of templates, etc
|
38 |
* Finalizing site features and basic implementation of templates, etc
|
| 39 |
\n
|
39 |
\n
|
| 40 |
* Making the site not look like garbage
|
40 |
* Making the site not look like garbage
|
| 41 |
\n
|
41 |
\n
|
| 42 |
Future feature implementation:
|
42 |
Future feature implementation:
|
| 43 |
\n
|
43 |
\n
|
| 44 |
* In depth statistics tracking for each individual game
|
44 |
* In depth statistics tracking for each individual game
|
| 45 |
\n
|
45 |
\n
|
| 46 |
* Tournament backend/bracketing
|
46 |
* Tournament backend/bracketing
|
| 47 |
\n
|
47 |
\n
|
| 48 |
* Event tracker
|
48 |
* Event tracker
|
| 49 |
\n
|
49 |
\n
|
| 50 |
* And more!
|
50 |
* And more!
|
| 51 |
\n
|
51 |
\n
|
| 52 |
If you wish to help us, please message me directly on discord (username: naiteiru).
|
52 |
If you wish to help us, please message me directly on discord (username: naiteiru).
|
| 53 |
\n
|
53 |
\n
|
| 54 |
The wiki will be open to edit by all, so if you have something you want to add feel free to do so.
|
54 |
The wiki will be open to edit by all, so if you have something you want to add feel free to do so.
|
| 55 |
\n
|
55 |
\n
|
| 56 |
----
|
56 |
----
|
| 57 |
\n
|
57 |
\n
|
| 58 |
[size=4]Why is the name Fightorder...?[/size]
|
58 |
[size=4]Why is the name Fightorder...?[/size]
|
| 59 |
\n
|
59 |
\n
|
| 60 |
It's a joke referencing a site named Dustloop that has a somewhat similar goal for a different series of games.
|
60 |
It's a joke referencing a site named Dustloop that has a somewhat similar goal for a different series of games.
|
| 61 |
\n
|
61 |
\n
|
| 62 |
----
|
62 |
----
|
| 63 |
\n
|
63 |
\n
|
| 64 |
\n
|
64 |
\n
|
| 65 |
[size=4]LET ME IN![/size]
|
65 |
[size=4]LET ME IN![/size]
|
| 66 |
\n
|
66 |
\n
|
| 67 |
You can access the (heavily under construction) site at https://www.fightorder.net/wiki/index.php?title=Main_Page
|
67 |
You can access the (heavily under construction) site at https://www.fightorder.net/wiki/index.php?title=Main_Page
|
| 68 |
\n
|
68 |
\n
|
| 69 |
If you have questions, please ask them below.
|
69 |
If you have questions, please ask them below.
|
| 70 |
\n
|
70 |
\n
|
[Community] Fightorder Wiki v1.1.0