H-Ext (Halo Extension), Support for Trial, PC, and CE! Both client and dedi!

[RadWolfie]

Why would you reimplement all of the functionality provided by the CRT instead of just using it like you claim the add-ons will be able to?

The main H-Ext doesn't even need those CRT's functionality as we have made our own better optimized code to serve specific things instead of generally. I think I might not answer to this question right, so just say it doesn't.

On another note, you really need to look for another host for your website. Nobody wants to dig around on a site with 30 second+ page load times just to find the documentation, assuming they can find it at all.

It's a non-profit organization which doesn't originally focus on Halo, so hence the reason of using the mini-computer. And I do agree with not wanting to dig around 30 second+ page load time, it's due to many plugins on WordPress + the Bug Tracker take little less longer to load. We have been working on site v2 to remove the WordPress and its plugins and possibility the Bug Tracker section too. The site v2's result about 300-500% more faster load page time than what we have now. We did have plan to custom build our server, yet it kept on postponing a lot. To be honest, it's a lot of work on our free time.

[Btcc22]

The main H-Ext doesn't even need those CRT's functionality as we have made our own better optimized code to serve specific things instead of generally. I think I might not answer to this question right, so just say it doesn't.

A cardinal rule of programming is not to reinvent the wheel, especially when it comes to something like the CRT and you don't have any evidence to justify the decision. At best, you'll gain a performance boost that nobody's going to notice and at worst, a bunch of security holes and stability problems.

It's a non-profit organization

Fair enough but so is every other mod project. If you can't get the site working, you could think about posting the code and documentation on some source-control site like GitHub, Google Code, BitBucket or any other service that looks suitable.

[RadWolfie]

So, security holes as in modules that is hacking the functions than it should be? Since we have experenced with reverse engineering (I do know you have more experence than me), I don't see how that would fix the security holes. And we do perform some tests with our custom coding to meet our expectation as it should be than leaving the functionality to constant crash as we're done with coding it.


GitHub is pretty much limited and not really satisfied with their features. Google Code may be likely better to use. BitBucket is a lot less featured and required to be paid in order to host the code. In summary, we only perferred free service similar to Google Code has to offer.

P.S. We really need to finish our site v2 and replace our old site due big performance improvement on reduce page load time. (Still working on the forum section.)

[sehe]

Quote from his PM to me:

My friends has read the posts you made and gave me advice not to response back to you due to your judging me and very ignorant troll as well.

By now it's pretty clear for everyone here that you are an ignorant retard and it's useless to tell you anything because you don't even try to think about that maybe we are right, since your pathetic arrogance would not allow you to admit that what you have done is just completely useless.

Sehe, you and Btcc22 chose to ignored my posts and questioning my skills repeatly.

Yes, we are questioning your skills because so far you only proved that you are a complete moron and lack of knowledge in every field you are working in.
Funny that you still think that we do not understand what we are talking about. But then, what did you achieve in the past 2 years? I was working on SAPP for example, and more than 300 servers are running on SAPP atm.

Well, just go on ignoring our posts, it's your problem, not ours, I stop wasting my time replying here anyways.

[Kornman00]

GitHub is pretty much limited and not really satisfied with their features. Google Code may be likely better to use. BitBucket is a lot less featured and required to be paid in order to host the code. In summary, we only perferred free service similar to Google Code has to offer.

How is GitHub limited? Google Code is doing away with their downloads system, while GitHub is making a first-class releases system.

BitBucket doesn't require you to pay anything unless you are hosting private repos, and even then you don't pay anything until you go over 5 developers (upgradeable to 8 if you invite more people to BB). GitHub, on the other hand, doesn't offer -any- sort of limited private repo hosting.

GitHub, Google Code, BitBucket, they're all free (the first two only for 'open' repos) and offer the same set of features at varying levels of integration (though, again, Google Code is doing away with the downloads system).

[RadWolfie]

Looks like GitHub has changed. And the first-class releases system you have reference is pretty much what we need. Since our Add-on API is open source and doesn't even need to be complie at all. So, this is a big benefit for all of us without the need to go through the svn in order to obtain every files. Google Code's separate download system and the source code isn't what we like for Add-on API's releases including some minor fixes.


Meaning we will be likely go with GitHub for Add-on API's code and the documentations. Thanks to Kornman00's questioning about our old research on the GitHub limitation.

Btcc22, I just realized the documentation link isn't on the Add-on API's FAQ and it's own page. I will have that fixed by tomorrow or until I have the GitHub for it to be ready and make the link to there instead. Can't believe I had overlooked that.

[RadWolfie]

We have added the Add-on API repository to the GitHub including the documentation from our Bug Tracker section. The library and header interfaces will be posted on Nov 1st, 2013. All of the export hooks for plugin to be used in H-Ext 0.4.0.0 and above are available to be view in our documentation too. Any feedbacks are welcome.

Also, I have updated the Add-on API's main and FAQ pages to be link for our documentation either on GitHub or Bug Tracker section.

[RadWolfie]

We have released H-Ext 0.5.0.0 and Add-on API 3.0 and ready for public usage. (We noticed a few are missing from the S-Ext transfer and will be updated in the next release.)

[Limited]

Bitbucket Limited? Ha yeah right. You realise its built by Atlassian? And therefore has direct compatability (and features) for JIRA, Confluence and other tools?

[RadWolfie]

GitHub has no limited to contributors per application code whilst BitBucket do have limitation of 5 users (aka contributors) for each application's source code. Therefore give a GitHub +1 reason to have. However GitHub's private service demand to be paid per monthly. But we do not need any of private service since our H-Ext is close source and easy to maintaince ourselves. GitHub do have similarilty to Atlassian's Confluence, even Google Code has this too. Also GitHub do have direct compatability and feature (similar with JIRA) with many third-party supports.

Our decision summarize into this expectation. First, the Add-on API's source code is need to be public. Secondly, in case of having more than 5 contributors (if any) to continously update the halo structure and other purposes would be better than 5 or less contributors. Third, we do not need any private service even if it's optional feature for free. Finally, H-Ext is basically provide the interface for the plugins to use whilst staying as barebone system*. So the conclusion would be GitHub.

We have Bug Genie software installed which is pretty much identical to JIRA. Although, the software is quite slower than our Halo's site. The plan is to migrate everything into our site v2 without the necessary to create different accounts for each software we have, more secure security, use only necessary resources to load a page, etc.

Remember, not every provider has your every needs can be hard to find and each do have limitation for free.



*this mean the plugins will be required to be loaded to serve your propose expectation such as role-play commands, extend gametypes, remote access, and so on.