-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
80 lines (59 loc) · 3.46 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
<!DOCTYPE html>
<html>
<head>
<meta charset='utf-8' />
<meta http-equiv="X-UA-Compatible" content="chrome=1" />
<meta name="description" content="CCM-Modding : " />
<link rel="stylesheet" type="text/css" media="screen" href="stylesheets/stylesheet.css">
<title>CCM-Modding</title>
</head>
<body>
<!-- HEADER -->
<div id="header_wrap" class="outer">
<header class="inner">
<a id="forkme_banner" href="https://github.com/CCM-Modding">View on GitHub</a>
<h1 id="project_title">CCM-Modding</h1>
<h2 id="project_tagline"></h2>
</header>
</div>
<!-- MAIN CONTENT -->
<div id="main_content_wrap" class="outer">
<section id="main_content" class="inner">
<h3>
<a name="welcome-to-ccm-modding" class="anchor" href="#welcome-to-ccm-modding"><span class="octicon octicon-link"></span></a>Welcome to CCM Modding.</h3>
<p>We make Minecraft mods, all kinds of them. <br>
Our official build server can be found <a href="http://jenkins.dries007.net">here</a>. <br>
If you want the maven repo, click <a href="http://maven.dries007.net/content/repositories/ccm/">here</a>. <br>
We can be found in #CCM on esper.net. <br></p>
<h3>
<a name="our-mods" class="anchor" href="#our-mods"><span class="octicon octicon-link"></span></a>Our mods</h3>
<p>Most of us have fun modding, this means that we don't have releases out 2 hours after a major MC update.
We try to keep stuff up to date, and finish projects every once in a while, but no promises. If a mod isn't updated within a month or if the repo is tagged as [Inactive], feel free to ask us for an update/progress report.<br>
Configurability is key with CCM, if you'd like something to be configurable and it isn't, we'll try to add an option somewhere. That said, always have a look at the .cfg file before you do, it might already exist.</p>
<h3>
<a name="you-have-a-mod-idea" class="anchor" href="#you-have-a-mod-idea"><span class="octicon octicon-link"></span></a>You have a mod idea?</h3>
<p>Feel free to post suggestions on the relevant issue list on github. If you have a general suggestion, use the Nucleum-Omnium repo, that's our core.<br>
If you want a mod made, send us the idea and specs. We like working on suggestions, as they are often a lot of fun to play with.<br></p>
<h3>
<a name="issues-and-bugs" class="anchor" href="#issues-and-bugs"><span class="octicon octicon-link"></span></a>Issues and bugs</h3>
<p>When you report a bug, please have screenshots, logs and stacktraces. The more the better.<br>
If you can't provide us with stacktraces or logs, we can't help.</p>
<h3>
<a name="developers-and-other-contributors" class="anchor" href="#developers-and-other-contributors"><span class="octicon octicon-link"></span></a>Developers and other contributors</h3>
<ul>
<li><a href="https://github.com/Dries007" class="user-mention">@Dries007</a></li>
<li><a href="https://github.com/Claycorp" class="user-mention">@Claycorp</a></li>
<li><a href="https://github.com/phillykiller777" class="user-mention">@phillykiller777</a></li>
<li><a href="https://github.com/CaptainShadows" class="user-mention">@CaptainShadows</a></li>
<li><a href="https://github.com/Morton00000" class="user-mention">@Morton00000</a></li>
</ul>
</section>
</div>
<!-- FOOTER -->
<div id="footer_wrap" class="outer">
<footer class="inner">
<p>Published with <a href="http://pages.github.com">GitHub Pages</a></p>
</footer>
</div>
</body>
</html>