Yeah. You are right. We should add some Social buttons here too =)kali wrote:Where's the like button?
Openkore community, we need to talk.
Moderator: Moderators
Re: Openkore community, we need to talk.
-
- Developers
- Posts: 1798
- Joined: 05 Dec 2008, 05:42
- Noob?: Yes
Re: Openkore community, we need to talk.
Why?kLabMouse wrote:I'm do not leting C/C++ coders to our code base...
Re: Openkore community, we need to talk.
Because there is noone skilled to do the tasks for XS part.EternalHarvest wrote:Why?kLabMouse wrote:I'm do not leting C/C++ coders to our code base...
XS is not C or C++ but only have something in common.
-
- Spam Generator
- Posts: 499
- Joined: 04 Apr 2008, 09:30
- Noob?: No
- Location: Melbourne, City of beer and awful sushis
Re: Openkore community, we need to talk.
Think he is asking why aren't you letting C/C++ coders make changes to the perl side of the code base.kLabMouse wrote:Because there is noone skilled to do the tasks for XS part.EternalHarvest wrote:Why?kLabMouse wrote:I'm do not leting C/C++ coders to our code base...
XS is not C or C++ but only have something in common.
Make Openkore Awesome. Join the team.
Re: Openkore community, we need to talk.
Oh... Because most of them Came here without any knowledge of "Perl".Cozzie wrote:Think he is asking why aren't you letting C/C++ coders make changes to the perl side of the code base.kLabMouse wrote:Because there is noone skilled to do the tasks for XS part.EternalHarvest wrote: Why?
XS is not C or C++ but only have something in common.
When I ask them to simple recompile or make some little changes to non XS part (C/C++ one) of XSTools, they never give any answer back. So from that it could be decided whatever they know it or not.
Other are welcome, unless they at least try to make changes.
-
- Noob
- Posts: 7
- Joined: 14 Sep 2008, 18:06
- Noob?: Yes
Re: Openkore community, we need to talk.
If there was a wiki about Openkore source, I'm sure that many more people would've contributed useful plugins/updates.
I have tried to work on plugins..perhaps i wasn't determined enough, but I felt that I had nowhere to look up the various variables and functions that I can use to write plugins. Macros are the obvious choice as they work with mostly console commands. Which are very well documented.
I'm sure the community will contribute a lot more if a guide were made and posted regarding the core components of Kore.
By core components, i mean something like which function returns
I have tried to work on plugins..perhaps i wasn't determined enough, but I felt that I had nowhere to look up the various variables and functions that I can use to write plugins. Macros are the obvious choice as they work with mostly console commands. Which are very well documented.
I'm sure the community will contribute a lot more if a guide were made and posted regarding the core components of Kore.
By core components, i mean something like which function returns
- monsters in view
players in view
items
how to handle AI queue (if this is manually permitted)
-
- Developers
- Posts: 1798
- Joined: 05 Dec 2008, 05:42
- Noob?: Yes
Re: Openkore community, we need to talk.
We have source documentation, but it's currently isn't hosted anywhere afaik (accessible locally in openkore). And it misses a lot.
-
- Super Moderators
- Posts: 801
- Joined: 06 May 2008, 12:47
- Noob?: No
Re: Openkore community, we need to talk.
Well tbh, I came here without any knowledge about perl and svn as well...kLabMouse wrote: Oh... Because most of them Came here without any knowledge of "Perl".
When I ask them to simple recompile or make some little changes to non XS part (C/C++ one) of XSTools, they never give any answer back. So from that it could be decided whatever they know it or not.
Other are welcome, unless they at least try to make changes.
A few patches later, svn access.
Postel wrote:Postel's Law: "be conservative in what you do, be liberal in what you accept from others" (often reworded as "be conservative in what you send, liberal in what you accept").
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
Re: Openkore community, we need to talk.
[quote="Technology"
Well tbh, I came here without any knowledge about perl and svn as well...
A few patches later, svn access.
[/quote]
Same story here, and other active developers/supporters.
But most of them. Just ask for write access without giving something back.
Well tbh, I came here without any knowledge about perl and svn as well...
A few patches later, svn access.
[/quote]
Same story here, and other active developers/supporters.
But most of them. Just ask for write access without giving something back.
- itsrachelfish
- Developers
- Posts: 50
- Joined: 27 Feb 2012, 12:50
- Noob?: No
Re: Openkore community, we need to talk.
I submitted patches to kLab and Harvest on IRC before getting an account on SVN. It's fair to require examples when giving someone access.
Learning perl to help with the source is great, but even writing your own plugins can be a lot of fun. If it wasn't for my experience with OpenKore I wouldn't have the job I have now. :D Looking back on the patches I've submitted, almost all of them were related to bugs I discovered while working on plugins. Working in your own microcosm can help uncover bigger problems.
A lot of kore's basic functionality is years old, and things like UseSkill haven't changed to reflect differences added in renewal. This might be a bit of a grandiose suggestion, but has anyone considered moving kore's AI to a more modular plugins system? Imagine if kore's base functionality was to handle networking and basic functions for interacting with the game, leaving AI, attack skills, item usage, etc. to plugins?
Just a thought.
Learning perl to help with the source is great, but even writing your own plugins can be a lot of fun. If it wasn't for my experience with OpenKore I wouldn't have the job I have now. :D Looking back on the patches I've submitted, almost all of them were related to bugs I discovered while working on plugins. Working in your own microcosm can help uncover bigger problems.
A lot of kore's basic functionality is years old, and things like UseSkill haven't changed to reflect differences added in renewal. This might be a bit of a grandiose suggestion, but has anyone considered moving kore's AI to a more modular plugins system? Imagine if kore's base functionality was to handle networking and basic functions for interacting with the game, leaving AI, attack skills, item usage, etc. to plugins?
Just a thought.
Tired of waiting for answers on the forums?
Want to talk to OpenKore experts?
Hang out on the #OpenKore IRC!
Want to talk to OpenKore experts?
Hang out on the #OpenKore IRC!