![]() |
[FLHook] Automated Bounty Plugin - Printable Version +- Discovery Gaming Community (https://discoverygc.com/forums) +-- Forum: Discovery Development (https://discoverygc.com/forums/forumdisplay.php?fid=7) +--- Forum: Discovery Developers Forum (https://discoverygc.com/forums/forumdisplay.php?fid=183) +---- Forum: Discovery Unofficial Development (https://discoverygc.com/forums/forumdisplay.php?fid=389) +----- Forum: Discovery Mod FLHook Projects (https://discoverygc.com/forums/forumdisplay.php?fid=266) +----- Thread: [FLHook] Automated Bounty Plugin (/showthread.php?tid=162627) |
[FLHook] Automated Bounty Plugin - Laz - 07-11-2018 So I decided to shamelessly steal Conrad's template to make things some degree of uniform. Automated Bounty Plugin So. What have I made? Well, as the title implies, it's a plugin that allows you to place bounties on people in game. I've created a bunch of default settings for it and I'll explain those below. I actually really pushed myself yesterday to get this out before then, spent literally all day trying to get the demo up and running but set back after set back prevented me from doing so. (See footer notes ^^) I am making this a separate thread from my normal bulk posting due to the nature of it. While being rather simple, it's a big change. I need some feedback! ^^ So What Is It? (<-- Good Joke) Simple Explanation: This plugin enables you to bounty certain characters in game without having to direct people to the forums. I see this as making the entire bounty system more viable as very few people seem to post individual bounties on the forums these days (from what I can tell). With the entire process being easier I aim to see more Freelancers/Bounty Hunters going out and making claims. The processes is simple. Someone makes a '/bounty new' and then people will be informed* about the creation of the bounty and it will be added to the list. From then on things go on as normal, until a hunter comes along to claim it. Then the plugin kicks in and crosschecks the killer with the list of bounties. If the guy had a bounty on him, it checks that his killer was a valid hunter (aka right ID). If both are true it will lower the claimable counter by 1, and give you the payout. What are the rules for these claims? Well there aren't many. There is a minimum and maximum value that can be placed on each target and the bounty placed must be within be placed within that range. You can specify how many times the bounty can be claimed (must be at least once). You must also provide an inRP reason for the bounty as part of the plugin. *see features or demo. Limitations Before we go any further I should go over the limitations I have discovered / created during my time on this plugin. Firstly (the most obvious one), when placing a bounty you are restricted to one name. Say for example we dislike someone, Core|Sexy.Nodviet - So we run "/bounty new Core|Sexy.Nodviet 1 10000000 No one can be more beautiful than me." In this instance we place a bounty on Core|Sexy.Nodviet for 10,000,000 credits, that is claimable once - with the reason of "No one can be more beautiful than me." All fine then? Well what if he then logs Core|Sexy,Nodviet ? There isn't a bounty on a guy with a comma on his ship, only a dot. There isn't really anything we can do about this, the only solution is to put up more bounties. Secondly, due to the way the plugin works, there is an inherently obvious bug. If you rename yourself while there is a bounty on your head you can simply evade it. The game looks for when someone of your name dies, and then checks if the guy that killed them was a valid ID for claiming bounties. However, changing your name skips the first step. I did think of a few solutions to this problem, but rather than implementing them without asking first, I thought I'd put it to the floor and hear you guys thoughts on the matter. Solution 1: Make it against the rules and class it as 5. Cheating/Exploiting - Self-explanatory, but less than optimal. Solution 2: Lock renaming while someone has a bounty on their head - If they can't rename, no bug. Solution 3: Other Suggestions (I'm hope to ideas). Thirdly, this is something I didn't mention in the demo. When going in for the kill the same rule that the event plugin is in effect. This means if you die via suicide (e.g. planet/sun dive) you'll rob someone off the kill. There is nothing that can be done about this, it's Freelancer. If this plugin did get in game, this would no doubt come under 5.6. (While I talk about the event plugin a bit, I didn't even look at the source of it when making this plugin. Go figure.) Bounty Commands
Other Features (If something has the '(optional)' flag, it means that it can be enabled/disabled by Admins)
Plans So where do we go from here? Well The plugin is for all intents and purposes considered finished, and just requires fine tuning and community feedback. I am, however, looking into Discovery API integration to make a forum based stats available. This would also include the things I talked about ages and ages ago, when I get around to it. All I need to do for this is work out how to use JSONBuddy to export the right data from the game and then we can have a live list of all the bounties available, right here integrated into the forums! Video This is a demo for all intents and purposes. Anything is open to change if people have good idea or reasoning. Few notes on the video: - I say "for convenience" and "for testing purposes" or variants more times than I can count.
- Sombra will mostly likely comment on my voice : < - I do make a couple mistakes in the demo, but everything works as intended. As I mention, my memory isn't the best ^^ - I spent 19 hours recording, rendering, and uploading. - I repeat myself. A lot. (30 or so min record, failed attempts, bad software bugs. Rendering caused "MACHINE_CHECK_EXCEPTION" on my PC 11 times during render, think I got hardware failure. Uploading at unstable 100 KB/s took 12 hours.) With all that in mind, I had a lot of fun making it. More fun on the demo than the actual plugin, but Freelancer limitations get in the way. Though, I did write a good 80% of the plugin at once and only had one error during testing! (discounting what you see inside the demo, those are oversights and have since been fixed) I am more than willing to discuss this and find better ~Happy Hunting. RE: [FLHook] Automated Bounty Plugin - SnakThree - 07-11-2018 Preventing suicides not counting could be done via /bounty locktarget or something, that requires legit ID to have selected bountied ship on scanner and his death in X minutes would still go through flhook? RE: [FLHook] Automated Bounty Plugin - Laz - 07-11-2018 That is possible, I suppose. The trouble with that is people could just idle at a battleground and lock someone while others kill. Or multiple people could do the lock. That would leave us with either multiple people claiming the same bounty at once, or only one guy claiming it irregardless whether he got the kill. RE: [FLHook] Automated Bounty Plugin - Jessitrescott - 07-11-2018 is it possible to make "$user has bounty "reason" "from" "amount" when i click the user ingame. this would be better instead of a sirius wide bounty message. a more complicated but fun system would be to make system wide messages depending on the amount of money bountied on them. aka if i bounty a player for 100 million he will show up on a sirius wide chat when he logs in if i bounty a player for 50 million it will show up only for those in the system if i bounty a player for <10 million it will show up only when i click him. RE: [FLHook] Automated Bounty Plugin - Stefan - 07-11-2018 What are you, a hobbit? It's your birthday, you're the one supposed to receive gifts. Nothing screams bade to me, it seems pretty neat overall. All I'd really suggest is that the first page of /bounty list be a digest for easier look, so it's both sexier to be bountied and to look for said bounties. Something simple, like high scores, such as: Code: $amount - targetName0 - bountyPatronName0 - #timesToCollect PS: How rude of me. Thanks! (: RE: [FLHook] Automated Bounty Plugin - Laz - 07-11-2018 (07-11-2018, 09:03 AM)Jessitrescott Wrote: is it possible to make "$user has bounty "reason" "from" "amount" So I just looked into the code in some more detail. This is definitely possible, but the Sirius wide messages would stay regardless, since they can be disabled by the Admins if they so wish. It should also be noted the default maximum bounty is 20 million. It is up to the Admins to change that, should this be implemented. (Minimum is 2 mill, not 500k as I said in the video) You also just gave me an idea @"Sombra Hookier" is going to love if I can pull it off. I think I may have just found a way to make /setinfo to appear in the F9 menu, testing is required though! RE: [FLHook] Automated Bounty Plugin - Laz - 07-11-2018 (07-11-2018, 09:16 AM)Stefan Wrote: Something simple, like high scores, such as: Aaaaaaaaaaaaaaaaaaaaaaaaa reeeeeeeeeeeeeeeeeee STEFAN why. I just remember a part I left out of the initial post! Added "Plans" section to the top! RE: [FLHook] Automated Bounty Plugin - Stefan - 07-11-2018 Always here to probe minds. RE: [FLHook] Automated Bounty Plugin - Sombs - 07-11-2018 I was talking with my consultant and apparently I am going to love this. RE: [FLHook] Automated Bounty Plugin - Kazinsal - 07-11-2018 (07-11-2018, 09:17 AM)Laz Wrote: I think I may have just found a way to make /setinfo to appear in the F9 menu, testing is required though! Neat. Bet we can mangle that into displaying POB infocards as well. Of course we also need to figure out why POB infocards just get everything after 250 characters eaten when the server restarts but y'know. |