Ind

We're re-introducing console input ( hercules renewal'd ), and whats this? it's the ability to type commands into login/char/map server console/terminals, that are then interpreted and acted upon. This feature was once available through a long-deprecated plugin, we're re-introducing it as a built in feature and far more efficient than the previous version. Currently, the old commands are being used, we'll be replacing them in the coming days and adding new ones, besides improving the functionality (so that if you use a gm command through console it wont require you to type gm position more than once, among other stuff).
By the way, typing 'shutdown', 'exit', 'quit' or 'end' will replicate the effect of @mapexit.
It's a optional feature, can be disabled in src/config/core.h by commenting the following line:
#define CONSOLE_INPUT

this is a planned feature to be built in into hercules, should be added soon.

this is a planned feature to be built in into hercules, should be added soon.

this is a planned feature to be built in into hercules, should be added soon.

Starting today we'll be going throughout all of our source code to modify how functions are called. so what?
Benefit
With this new implementation chances to have custom source modifications conflict when you update hercules will be drastically reduced. How? Instead of modifying existing functions users will be able to create a new version of them elsewhere, e.g. in a custom file, and have it replace the original one. How? very simple.
battle->check_target = my_new_check_target_function; PluginsThis change opens the possibility for a new plugin implementation in the future.
Project Vision
We understand this move will conflict with some points in our project vision, we'll be modifying it soon.
More
We want Hercules to stand out, with that in mind we've been planning features exclusive to Hercules, features other projects won't be able to merge. And how is that even possible? features that will integrate with our forum is one example of them. For example a feature capable of automatically looking for new updates in scripts/modifications downloaded from our upcoming downloads section.

Added support in https://github.com/HerculesWS/Hercules/commit/0241d0195558b7e57d2181f2f097cf774a1ef463

Added support in https://github.com/HerculesWS/Hercules/commit/0241d0195558b7e57d2181f2f097cf774a1ef463

Starting today we'll be going throughout all of our source code to modify how functions are called. so what?
Benefit
With this new implementation chances to have custom source modifications conflict when you update hercules will be drastically reduced. How? Instead of modifying existing functions users will be able to create a new version of them elsewhere, e.g. in a custom file, and have it replace the original one. How? very simple.
battle->check_target = my_new_check_target_function; PluginsThis change opens the possibility for a new plugin implementation in the future.
Project Vision
We understand this move will conflict with some points in our project vision, we'll be modifying it soon.
More
We want Hercules to stand out, with that in mind we've been planning features exclusive to Hercules, features other projects won't be able to merge. And how is that even possible? features that will integrate with our forum is one example of them. For example a feature capable of automatically looking for new updates in scripts/modifications downloaded from our upcoming downloads section.

Starting today we'll be going throughout all of our source code to modify how functions are called. so what?
Benefit
With this new implementation chances to have custom source modifications conflict when you update hercules will be drastically reduced. How? Instead of modifying existing functions users will be able to create a new version of them elsewhere, e.g. in a custom file, and have it replace the original one. How? very simple.
battle->check_target = my_new_check_target_function; PluginsThis change opens the possibility for a new plugin implementation in the future.
Project Vision
We understand this move will conflict with some points in our project vision, we'll be modifying it soon.
More
We want Hercules to stand out, with that in mind we've been planning features exclusive to Hercules, features other projects won't be able to merge. And how is that even possible? features that will integrate with our forum is one example of them. For example a feature capable of automatically looking for new updates in scripts/modifications downloaded from our upcoming downloads section.

forgot to update this here. Yes it was applied, thank you very much.

Starting today we'll be going throughout all of our source code to modify how functions are called. so what?
Benefit
With this new implementation chances to have custom source modifications conflict when you update hercules will be drastically reduced. How? Instead of modifying existing functions users will be able to create a new version of them elsewhere, e.g. in a custom file, and have it replace the original one. How? very simple.
battle->check_target = my_new_check_target_function; PluginsThis change opens the possibility for a new plugin implementation in the future.
Project Vision
We understand this move will conflict with some points in our project vision, we'll be modifying it soon.
More
We want Hercules to stand out, with that in mind we've been planning features exclusive to Hercules, features other projects won't be able to merge. And how is that even possible? features that will integrate with our forum is one example of them. For example a feature capable of automatically looking for new updates in scripts/modifications downloaded from our upcoming downloads section.

Starting today we'll be going throughout all of our source code to modify how functions are called. so what?
Benefit
With this new implementation chances to have custom source modifications conflict when you update hercules will be drastically reduced. How? Instead of modifying existing functions users will be able to create a new version of them elsewhere, e.g. in a custom file, and have it replace the original one. How? very simple.
battle->check_target = my_new_check_target_function; PluginsThis change opens the possibility for a new plugin implementation in the future.
Project Vision
We understand this move will conflict with some points in our project vision, we'll be modifying it soon.
More
We want Hercules to stand out, with that in mind we've been planning features exclusive to Hercules, features other projects won't be able to merge. And how is that even possible? features that will integrate with our forum is one example of them. For example a feature capable of automatically looking for new updates in scripts/modifications downloaded from our upcoming downloads section.

Starting today we'll be going throughout all of our source code to modify how functions are called. so what?
Benefit
With this new implementation chances to have custom source modifications conflict when you update hercules will be drastically reduced. How? Instead of modifying existing functions users will be able to create a new version of them elsewhere, e.g. in a custom file, and have it replace the original one. How? very simple.
battle->check_target = my_new_check_target_function; PluginsThis change opens the possibility for a new plugin implementation in the future.
Project Vision
We understand this move will conflict with some points in our project vision, we'll be modifying it soon.
More
We want Hercules to stand out, with that in mind we've been planning features exclusive to Hercules, features other projects won't be able to merge. And how is that even possible? features that will integrate with our forum is one example of them. For example a feature capable of automatically looking for new updates in scripts/modifications downloaded from our upcoming downloads section.

Starting today we'll be going throughout all of our source code to modify how functions are called. so what?
Benefit
With this new implementation chances to have custom source modifications conflict when you update hercules will be drastically reduced. How? Instead of modifying existing functions users will be able to create a new version of them elsewhere, e.g. in a custom file, and have it replace the original one. How? very simple.
battle->check_target = my_new_check_target_function; PluginsThis change opens the possibility for a new plugin implementation in the future.
Project Vision
We understand this move will conflict with some points in our project vision, we'll be modifying it soon.
More
We want Hercules to stand out, with that in mind we've been planning features exclusive to Hercules, features other projects won't be able to merge. And how is that even possible? features that will integrate with our forum is one example of them. For example a feature capable of automatically looking for new updates in scripts/modifications downloaded from our upcoming downloads section.

Starting today we'll be going throughout all of our source code to modify how functions are called. so what?
Benefit
With this new implementation chances to have custom source modifications conflict when you update hercules will be drastically reduced. How? Instead of modifying existing functions users will be able to create a new version of them elsewhere, e.g. in a custom file, and have it replace the original one. How? very simple.
battle->check_target = my_new_check_target_function; PluginsThis change opens the possibility for a new plugin implementation in the future.
Project Vision
We understand this move will conflict with some points in our project vision, we'll be modifying it soon.
More
We want Hercules to stand out, with that in mind we've been planning features exclusive to Hercules, features other projects won't be able to merge. And how is that even possible? features that will integrate with our forum is one example of them. For example a feature capable of automatically looking for new updates in scripts/modifications downloaded from our upcoming downloads section.

Starting today we'll be going throughout all of our source code to modify how functions are called. so what?
Benefit
With this new implementation chances to have custom source modifications conflict when you update hercules will be drastically reduced. How? Instead of modifying existing functions users will be able to create a new version of them elsewhere, e.g. in a custom file, and have it replace the original one. How? very simple.
battle->check_target = my_new_check_target_function; PluginsThis change opens the possibility for a new plugin implementation in the future.
Project Vision
We understand this move will conflict with some points in our project vision, we'll be modifying it soon.
More
We want Hercules to stand out, with that in mind we've been planning features exclusive to Hercules, features other projects won't be able to merge. And how is that even possible? features that will integrate with our forum is one example of them. For example a feature capable of automatically looking for new updates in scripts/modifications downloaded from our upcoming downloads section.

Starting today we'll be going throughout all of our source code to modify how functions are called. so what?
Benefit
With this new implementation chances to have custom source modifications conflict when you update hercules will be drastically reduced. How? Instead of modifying existing functions users will be able to create a new version of them elsewhere, e.g. in a custom file, and have it replace the original one. How? very simple.
battle->check_target = my_new_check_target_function; PluginsThis change opens the possibility for a new plugin implementation in the future.
Project Vision
We understand this move will conflict with some points in our project vision, we'll be modifying it soon.
More
We want Hercules to stand out, with that in mind we've been planning features exclusive to Hercules, features other projects won't be able to merge. And how is that even possible? features that will integrate with our forum is one example of them. For example a feature capable of automatically looking for new updates in scripts/modifications downloaded from our upcoming downloads section.

Starting today we'll be going throughout all of our source code to modify how functions are called. so what?
Benefit
With this new implementation chances to have custom source modifications conflict when you update hercules will be drastically reduced. How? Instead of modifying existing functions users will be able to create a new version of them elsewhere, e.g. in a custom file, and have it replace the original one. How? very simple.
battle->check_target = my_new_check_target_function; PluginsThis change opens the possibility for a new plugin implementation in the future.
Project Vision
We understand this move will conflict with some points in our project vision, we'll be modifying it soon.
More
We want Hercules to stand out, with that in mind we've been planning features exclusive to Hercules, features other projects won't be able to merge. And how is that even possible? features that will integrate with our forum is one example of them. For example a feature capable of automatically looking for new updates in scripts/modifications downloaded from our upcoming downloads section.

We at Hercules want to provide our users with as many international communities as we can, however in order to create a international community we first need someone to oversee it.
Do you speak a language other than English that we don't have a community for?
Be the first, join our team
Do you speak a language other than English that we have a community for?
Help us moderate it, join our team
 
Notice however that our guidelines for wannabe moderators applies

this could be done in src easily..
 
MVP killed -> save to db left respawn time
Server restarted or npc reloaded -> server fetch respawn time from db then parse then load to its ticking process before respawn
 
this will only work if the MVP mob dies after server initial start...
 
ATM just an idea and the codes are still in my brain..if I have time I'll do it..
 

Git Troubleshooting
Please, commit your changes or stash them before you can merge.Aborting.Git doesn't update modified files even if they don't conflict unless they're properly "committed" in your local working copy, to do so is simple and advantageous (it will keep a log of your changes for yourself; so you can always go back and check what was changed and when)
- On Unixgit commit -am "your log message, anything at all" - On Windows
1. Right click your folder -> Git Commit -> "master"
2. (optional) type the log message
3. Hit 'OK'

Obtaining Hercules through Git on Windows
Downloads
Download and Install MSysGit Download the latest TortoiseGit

  Installation
Alright, first go through MSysGit installer and just set it up (its used as a base for TortoiseGit). then once you install MSysGit, launch the installer you just downloaded for TortoiseGit, you'll be prompted by a window similar to the following


The next window is "Choose SSH Client", select "TortoisePLink", hit Next.


The next window is "Custom Setup", do not change anything unless you know what you're doing, hit Next.


We're done with the installation, that was easy, wasn't it?


Obtaining Hercules
Go to the folder where you want Hercules to be placed, right click and select "Git Clone..."


in the URL field, type the following:
https://github.com/HerculesWS/Hercules.git ensure the 'Directory' field is as desired, and hit 'OK'


Now Hercules is being downloaded


Just wait for it to complete the download of your working copy and you'll be good to go.

Updating Hercules
Right-Click the folder where you downloaded your working copy and within the TortoiseGit menu, select "Pull..." as shown below


On the following window just hit 'OK', and your working copy will update.

Obtaining Hercules
Hercules is available through GitHub, a web-based hosting service for software development projects that use the Git revision control system.
Obtaining Hercules through Git on Windows Obtaining Hercules through Git on Linux Git Troubleshooting

  Support
Looking for assistance on getting Git to work? Post here

Alternatively...
GitHub also provides a SVN Mirror. We won't officially work to support many branches or repository-features in SVN, but it should remain in-sync with the latest stable release, based on master branch in git.
Windows
You need to download TortoiseGit The address is http://github.com/HerculesWS/Hercules  
Linux
Typing the following creates a working copy of hercules at your home directory svn checkout http://github.com/HerculesWS/Hercules ~/Hercules  
 
 

Obtaining Hercules through Git on Windows
Downloads
Download and Install MSysGit Download the latest TortoiseGit

  Installation
Alright, first go through MSysGit installer and just set it up (its used as a base for TortoiseGit). then once you install MSysGit, launch the installer you just downloaded for TortoiseGit, you'll be prompted by a window similar to the following


The next window is "Choose SSH Client", select "TortoisePLink", hit Next.


The next window is "Custom Setup", do not change anything unless you know what you're doing, hit Next.


We're done with the installation, that was easy, wasn't it?


Obtaining Hercules
Go to the folder where you want Hercules to be placed, right click and select "Git Clone..."


in the URL field, type the following:
https://github.com/HerculesWS/Hercules.git ensure the 'Directory' field is as desired, and hit 'OK'


Now Hercules is being downloaded


Just wait for it to complete the download of your working copy and you'll be good to go.

Updating Hercules
Right-Click the folder where you downloaded your working copy and within the TortoiseGit menu, select "Pull..." as shown below


On the following window just hit 'OK', and your working copy will update.

Git Troubleshooting
Please, commit your changes or stash them before you can merge.Aborting.Git doesn't update modified files even if they don't conflict unless they're properly "committed" in your local working copy, to do so is simple and advantageous (it will keep a log of your changes for yourself; so you can always go back and check what was changed and when)
- On Unixgit commit -am "your log message, anything at all" - On Windows
1. Right click your folder -> Git Commit -> "master"
2. (optional) type the log message
3. Hit 'OK'