Perhaps there's a way to reduce the randomness by reducing the blocktime and make 1 game turn every X blocks (e.g. block time 20 seconds, 1 game turn every 3 blocks)

In a RPG, 3d20 damage is also more uniform than 1d60...



If a sha256 block comes shortly after a scrypt block, then the scrypt block is likely to get orphaned, because in Huntercoin, both add to the total chain work according to a constant ratio sha256 diff/scrypt diff, and in practice this is in favor of the sha256 block

It could be a pool switching from mining BTC + some merge-minable coins to mining other non-merge-minable coins based on realtime exchange rates, but not sure how realistic such a scenario is.

Unity client (with Huntercore) will have abilities like autograbbing nearby coins while avoiding enemies, but not sure how soon.

I also still keep updating the old Qt (binary release from tomorrow can auto-correct player errors like in the above example in real-time which is a huge difference and feels now like you command smart veteran hunters)



..and the shiny new All-features-in-Huntercore-Qt will probably be a byproduct of these surprises

Example of a tactical situation:


Current block height is T+0.
For transactions sent right now, they can confirm at T+1, T+2 (most likely) or T+3.

v1 would be a mistake for blue because if his tx confirms at T+1, and tx from green confirms at T+2, blue would die for being too fast.
This can't happen with v2.

On most days 9 or 10 connections but today only 7. If you do port forwarding and never get more than 8, then the limit of 8 without port forwarding was saved somewhere, this would be fixed when the node is started with maxconnections=32 at least once. (the old client behaved that way)

It's always on block xxxx500 and on block xxx1000 (when all the ghost coin return to normal), next would be block 1557000

If the new guys (or all hunters) cant attack in spawn area then we would perhaps see campers on tiles adjacent to the spawn strip, and they could kill the new hunters when they (the new guys) start moving.

The life-steal system works in the way that only attackable hunters are eligible to get drained life (first all drained life goes to the gamefund and some hunters die, then it's distributed to some of the surviving attackable hunters)

Imho it's pretty well balanced as it is, the camper (or unlucky passer-by) dies but there is also no incentive to try killing hunters in that way. And the passer-by can defend normally against attacks of newly spawned hunters.

If you mean the "Pay transaction fee" in setting menu of the old Qt client, a line in the config file like "paytxfee=0.01" should do the same.

Huntercore setting menu is just a 1:1 clone of Bitcoin's, probably, and doesn't have "Pay transaction fee".

Also, the fee per KB calculation in Huntercore *may* be a bit different than in the old nodes. (and some miners use Huntercore, some use the old daemon)

I think almost no game tx (if sent with old Qt) pays more than 0.018 HUC, so paytxfee=0.018 would be a safe setting for Huntercore.

Playing Huntercoin shouldn't be stressful but it is if you have to harvest single coins while the usual campers probably have a more advanced setup. (not sure what they really use)

I think the client(s) need to be able to do some coin grabbing, perhaps regular solo players can make more hunters, and play more often, and can better focus on the fights.

Also important imo: players shouldn't need redundant (or at least very stable) internet connection to play with several hunters, the client can make sure that the path always ends on a banking tile.
(Unless you order the hunter to go elsewhere)

pics taken with betterQt built from latest source on github (need to be more reliable and configurable but kinda fun to play with)

mergemining.com listing HUC is pretty cool (didn't know that)

The main thread for Huntercoin is this one: https://bitcointalk.org/index.php?topic=435170.0

So, not dead

And if the hunter is refunded (after 15 blocks as spectator, or just after standing on bank tile) it takes another 120 blocks for the coins from refund to mature and become available. They are treated like freshly mined coins in this regard.


Also, when creating a hunter during the last 10 blocks of "coin ghosting", i.e. the last 10 blocks of full 500 blocks from xxxx490 to xxxx500, or from xxxx990 to xxxx000, the "invulnerable for 5 blocks" counter will not begin to tick until after the coin ghosting is finished.

Having up to 15 minutes to plan ahead is really useful for creating several hunters.

This forum thread is perhaps the place to collect rules/instructions that need to be in the manual (but aren't anywhere written down). One would be the following:

When a block is processed, then combat is done first, and movement second after some hunters are already dead.
e.g. if you have a blue hunter 2 tiles away from a red hunter (both are standing still)
then sending "destruct" and a straight move towards the enemy (diagonally) is not a good idea. It's better to attack with a 2 waypoints move (horizontally+vertically)

If a newbie doesn't know this it would look like clear case of cheating to them.

The v1.4 Windows release has "GameRules.txt".

https://github.com/wiggi/huntercoin/blob/betterQt-timesave6/GameLogicChanges.txt
is now the same text (with Basic Game Rules, Life-Steal Fork, and Timesave fork rules)

Yay, new Huntercoin era


Not sure if this is about the same thing but during the messy transition period (first 20 blocks after 1521500) when time was running backwards a few times,
some hunters (and all their transactions) were wiped out so that they never existed, and the 101HUC for them was never paid etc.

This issue was fixed in the latest "All in One - Huntercore v0.13 + Unity3d + Pruned Chain".

I have updated the Windows build for "Old version Huntercoin (with game tab)": https://mega.nz/#!rNNBAZRT!Jdbqy2SJjzc0ILRsE-XMlOgovsVFVOP01t6OM6Gi6as

- standard v1.4, and betterQt safemode + advanced mode (both with quickstart guide)

- description of game rules updated from old GameLogicChanges.txt that is not in the All-in-One-Installer (yet)

- hit+run system is now fork ready, won't walk right into trap of newly spawned invulnerable guy (who can do 1 or 2 destructs while still invulnerable)

- edited visual map in center a bit to make the spawn strip less obscured by palisades (the south gate can't be opened because it's blocked by that rock

More to getblocktemplate, probably

If this is the Huntercore blockchain, add "prune=550" in huntercoin.conf. But then you can't rescan anymore, or bring in an old wallet (because client would want to do a (full or partial) rescan.

Especially if you don't have lots of download bandwidth, don't prune. Keep (and backup if not out of disk space) the unpruned chains of both old Huntercoin (which can't be pruned) and Huntercore, if you have them already.

It's possible to know (from the version numbers of the block) if this miner has updated for the fork.

huntercoin.info shows this too, e.g. https://www.huntercoin.info/blockExplorer/block/02a3ec4c4348e1dabebbebd565de0d7a0d527a6ecb5fffd6d91017c2c5a8f219 (Version: 393474) was mined with v1.4 (even number). Odd numbers would mean not updated (v1.3), divisible by 4 is Huntercore.

About 70% of blocks are mined with v1.4 now, up from ~50% over the weekend. Watching this also gives a guesstimate about the number of miners/pools.

Hopefully the new game rules put any bot system at a disadvantage.

When you start playing and spawn 15 or 20 hunters, which is cheap now, there are good chances to get a pair placed strategically left and right of some other guy. If it's a bot, he *may* be able to flee and log out using relatively simple logic, but it depends on the actual positions of the 3 hunters.

This being said, betterQt can grab coins, and can control the exact timing of sending destruct, so that the player can go afk for a few minutes, in most situations, without facing certain death. (this all was made for the pre-fork game rules)


And when you suddenly lose connection... a bank tile of some sort is now always nearby, and it makes sense to let the path of all hunters end on one, and accidental logouts cost only 1 HUC, but perhaps players would want a helper function for this (to let a bored hunter always hang around a bank tile, with path ending on it)