Jump to content

goigle

Members
  • Content Count

    184
  • Joined

  • Last visited


Reputation Activity

  1. Like
    goigle got a reaction from fireboy6117 in [WIP][REL] Federal Callouts   
    Yes, I still have big plans. I kind of disappeared from the GTA V scene due to a big course load for a bit but I am back.
    I hope to have a trailer for the new version released soon, I'm trying to overhaul the existing callouts and features to make a more fine tuned experience.
  2. Like
    goigle got a reaction from Kal74 in [WIP][REL] Federal Callouts   
    What I'm working on right now:
    Awareness system for suspects. You can now hide behind cover to prevent the AI from noticing you. Interactive menu to call for a federal surveillance chopper / federal backup / otherwise interact with the callouts Overhauling kidnapping & bomb sting callouts
  3. Like
    goigle reacted to LukeD in API Development Hub - Information, Resources & Guides   
    This thread will remain pinned and locked and used by moderation and management staff to maintain the API forum section. Please try to avoid pinning too many threads. Instead edit this hub thread with any information you deem relevant. If information is critical (i.e some things Cyan posts) it can be pinned, and added to the hub. Then unpinned later when it is no longer critical. The hub thread will then maintain the link to that thread.
    Welcome to the API Development Forums
    "Hello fellow developers. Welcome to our brand new LSPDFR API Development forum. Great to see you made it here! This is the place to ask questions about working with the API, as well as requesting features. More examples and proper documentation will follow soon as we focus on the mod itself currently. If you have any feedback regarding the very early API implementation though, feel free to share." - LMS
     
    API Changes & Important Information
    Download Centre API - Cyan
     - Documentation post for the newly introduced download centre API for update and version comparison and beta authorization.
    New API Functions in LSPDFR 0.2a - Sam
     - Information regarding new API functionality provided by 0.2a
    Keeping Users Safe - Cyan
     - Update information regarding the upload of plugins which contact personal servers or use .EXE programs
     
    Resources
    GitHub Repository (This link directs you to GitHub.com)
     - Link to the github repository. Here you can find developer resources such as custom classes to help you with development
    Vector3Extension Class (This link directs you to pastebin.com)
     - Link to the C# code that was removed from public access in LSPDFR code, simply add this class to your own plugin to make use of functions like Around(start, radius) and DistanceTo(start, end)
    API Quick Start Guide & Example Project
     - A quick start pdf guide and zip file containing a basic LSPDFR plugin solution, for use in Visual Studio
    RagePluginHook Documentation (This link directs you straight to the RPH online documentation)
     - Online documentation for the Rage Plugin Hook
    GTA V Prop List (This link directs you to a prop list, hosted on GitHub.com)
     - A list of all known GTA V prop model names
    GTA V Natives Database (This link directs you to the GTA V Natives DB, hosted on dev-c.com)
     - GTA V Natives database created by Alexander Blade.
    GTA Animations List (This link directs you to the ls-multiplayer website)
     - A larger list of all known animations in GTA V (It contains more than the RPH Documentation)
    CoordSaverV - LtFlash
     - Downloadable tool that helps the process of manually collecting callout spawn points
    Guides & Other Useful Topics
    Standardisation of API Plugin Colours - AlconH
     - Thread detailing a universal colour scheme for text and blips for API developers to use when writing plugins
    Guide to using the LSPDFR API & Documentation - Albo1125
     - A nice guide to making use of the LSPDFR API
    Guide to Creating a Callouts Plugin - ToastinYou
     - A nice guide with images on how to create a callouts plugin with the LSPDFR API and RagePluginHook
    LSPDFR Developers Discord Server - Stealth22 (This link directs to the Discord website, directly to the chat room)
     - A free chat client for LSPDFR developers to make use of for general chat, help and guidance.
    This discord server uses a bot which requires the user to verify themselves as a developer in order to prevent general "my game is broke help" requests. 
    Tips For Developers - Stealth22
     - A general thread of useful tips for all developers, whether you're new to programming or not.
     
    General Guidelines For Using This Forum
    Please adhere to these where possible, as they will help to keep the forum clean and useable. Remember that your posts act as information sources to users as well, not just means to get help.
    •  Make use of title tags: [Solved] [Resource] [Guide] [Request] etc (I would recommend putting these at the start of your title)
    •  Make sure your titles are crystal clear, not single words. Remember users may search for similar issues, you wouldn't search Google for "help" and hope one of the 4,890,000,000 results is the one you need.
    •   Always put your log files either as an attachment or copied into a spoiler, similarly code snippets should be placed inside the code tags
     
    Suggesting Content For This Hub Thread
    If you have any suggestions for threads, resources or useful links that you think deserve to be highlighted in this thread please PM myself (LukeD) with your suggestion. Make sure you title your PM "API Dev Forum Idea" or similar so I can keep track of them. Alternatively you can direct message or tag me on the discord server mentioned above, please note I only respond to this on desktop however, so replies may be slow.
    If you want to send me resources, be considerate of user safety and concerns regarding links.
    •  Don't post advertising or shortened URL's, I want a full link to the resource that I can read.
    •  Do give me a brief description of what you're sending, not just "hey this is useful".
    •  Do provide reasons for why you think it's needed in the hub thread. The more you justify it the better.
    In cases where you link a post or thread to me, I will parse that post for direct links. If I can avoid bouncing users around the forum I will. For example the discord server link above was taken out of Stealth22's post. Posts may then be subject to removal if necessary.
    I will credit all links where applicable, all I'm doing is concatenating the information into one thread, credits are deserved for those providing the resources or guides.
     
    This hub thread is an attempt at cutting down the increasing number of pinned threads. Please don't ask for threads to be pinned in this forum section. Only critical, need to know information will be pinned. After a while it will then be moved to this hub when it is no longer critical, but still useful.
     
    This forum section is subject to moderation as per usual. Any thread that is linked in this hub however, will be exempt from the necro posting rules. As they will be acting as pinned threads (which are already exempt).
  4. Like
    goigle reacted to Stealth22 in [CALLING ALL DEVS] Police Computer Integration   
    Its actually in the works for the future, haha. If you're interested in helping out let me know.
  5. Like
    goigle got a reaction from Kal74 in [CALLING ALL DEVS] Police Computer Integration   
    also, slightly related, I've been working on a "priors" system for federal callouts that I think would work well with this
    basically if a suspect gets away (officer down or eludes in a pursuit), their persona's name has a running list of crimes committed that is persistent between game launches (or not, if the user decides) and there's a chance you'll see them on the streets again
    it would mesh extremely well with this as the computer could display said priors, etc
    It'd be nice if callouts could override this, I know you said it is for another time but I just wanted to add my $0.02 while I was thinking about it
    at my store, when we're processing detained people and the police arrive they'll bring in their laptop and occasionally give us information
  6. Like
    goigle reacted to Stealth22 in [CALLING ALL DEVS] Police Computer Integration   
    Yikes! Stay safe!
  7. Like
    goigle got a reaction from Stealth22 in [CALLING ALL DEVS] Police Computer Integration   
    Dope, I'll try and get an update out soon, work is busy though because I do security in Orlando and we're on high alert
  8. Like
    goigle got a reaction from Stealth22 in [CALLING ALL DEVS] Police Computer Integration   
    Dope, I'll try and get an update out soon, work is busy though because I do security in Orlando and we're on high alert
  9. Like
    goigle got a reaction from Stealth22 in [CALLING ALL DEVS] Police Computer Integration   
    Dope, I'll try and get an update out soon, work is busy though because I do security in Orlando and we're on high alert
  10. Like
    goigle reacted to Darkmyre in User defined callout probability   
    One callout to rule them all...
  11. Like
    goigle reacted to LMS in User defined callout probability   
    You can register a dummy callout with Always as probability and then in your code decide whether or not to start that callout. You could also use the dummy to launch other callouts to have more control.
  12. Like
    goigle got a reaction from Kal74 in [WIP][REL] Federal Callouts   
    What I'm working on right now:
    Awareness system for suspects. You can now hide behind cover to prevent the AI from noticing you. Interactive menu to call for a federal surveillance chopper / federal backup / otherwise interact with the callouts Overhauling kidnapping & bomb sting callouts
  13. Like
    goigle got a reaction from Kal74 in [WIP][REL] Federal Callouts   
    What I'm working on right now:
    Awareness system for suspects. You can now hide behind cover to prevent the AI from noticing you. Interactive menu to call for a federal surveillance chopper / federal backup / otherwise interact with the callouts Overhauling kidnapping & bomb sting callouts
  14. Like
    goigle got a reaction from Kal74 in [WIP][REL] Federal Callouts   
    Great idea :D
  15. Like
    goigle reacted to Kal74 in [WIP][REL] Federal Callouts   
    Suggestion for an interactive Menu like the 2 found in this video..Repeat Offenders and Solicitation Callouts.. All of the credit goes to Albo1125 and FinKone, I'm just suggesting, not passing it off as my idea.. I think adding something this in your future Callouts will greatly enhance them...
     
     
  16. Like
    goigle got a reaction from Fiskey111 in wip Plugin tool   
    github eta will be closer to this weekend because fuck discrete math
  17. Like
    goigle reacted to TheAlgerian in [WIP][REL] Federal Callouts   
    Car repair is something the LSPDFR needed desperatly.
    It's so annoying to always have to find a new car when yours is a bit damaged.
     
    Great mod.
    I'm really looking forward to the jurisdiction feature.
  18. Like
    goigle got a reaction from Kal74 in [WIP][REL] Federal Callouts   
    0.45 is out, Bomb Sting / other callouts that are WIP and being beta tested are still being developed but will likely make it onto 0.46,
    I was watching a stream in the background today and I heard him mention a feature that he would want that I thought was really cool (and am honestly surprised it has not been done already). I added a simple repair system to federal callouts. As with everything else, you can turn it off in the ini. You basically pull up to the repair waypoint and your car is repaired for you.
  19. Like
    goigle got a reaction from Stealth22 in [CALLING ALL DEVS] Standardisation of API Plugin Colors   
    I'm just using Color.Yellow for the routes, looks close enough to the GTA V ones if you ask me.
    @Stealth22 - I'll switch my callouts to use LightBlue instead of blue. I agree, Blue is too blue.
    I'll change the ped size scale too.
  20. Like
    goigle got a reaction from AlconH in [CALLING ALL DEVS] Standardisation of API Plugin Colors   
    I agree with @LukeD. I use a color scheme that is fairly close to Vanilla GTA V. I use green in my subtitles for general, important info (like a hotkey) and red for other information (like specifying a hostile target or a committed crime).
    I am all for standardizing colors though - it will make all plugins look a lot more professional. If I am correct, Federal Callouts should already be abiding by these standards. Blue for security guards/backup, red for enemies / targeted suspects. The only exception is the drug deal which marks the seller as "green" currently when the player should not move in, and then "red" when he should. I'll change it to yellow now as it's not a big deal.
    As for routes, I personally prefer keeping them as yellow.
     
     
    What if we created a library with a bunch of default stuff, like colors and such, maybe some commonly used extensions & methods. I feel like I am a library salesman and I realize it's kind of an unpopular idea due to users having trouble with installing libraries and yadda yadda but you can just put the library in your library,
    I don't remember what the proper term is in .NET but you can merge assemblies together (they have to be the same .NET version which shouldn't be a problem)
    So,
    PublicLSPDFRExtensions.dll
    YourCallouts.dll
     
    becomes
    YourCallouts.dll
     
  21. Like
    goigle reacted to LukeD in [CALLING ALL DEVS] Standardisation of API Plugin Colors   
    A nice idea, but generally speaking there are a few rules that GTA follows, and I personally try to stick as close to GTA blips and LSPDFR blips as possible. Perhaps incorporate this into your list.
    Yellow
    • GTA - Primary objectives, search areas and route guidance.
    • LSPDFR - Primary search areas (prior to accepting a callout)
    Red
    • GTA - Enemies or targets. (they use size to depict vehicles or peds)
    • LSPDFR - Pursuit suspects. (combined with blue for flashing search area of pursuits (I think))
    I wouldn't bother with multiple route guidance colours. Stick with yellow if going to a callout, it's cleaner to match GTA imo.
    Also seeing as we're discussing colours and how they should be used....
    Additional advice on the use of colours (this may be my personal taste here, take with a pinch of salt)
    • Strip notifications of too much colour, highlighting a cop unit number or name is fine but the rest should be the same colour. I recommend using colour to highlight key info. eg. "Dispatch any units available for...?", "Paramedics We're on route standby!" etc. Especially if it's your callout start notification, they should be standardised with LSPDFR's.
    • Try not to go overboard with colours in text overlays either (the subtitles for example). Again use them to highlight key info eg. "Ped", "Witness", "Cop", search the "area" for...
    • Make sure blips correspond with colours used in any text. Eg. "look for the suspect at the place" in which the word suspect would match the blip he has. (this was common from LCPDFR)
     
    And yes, I will be adopting the changes that come about from this thread when I have plenty of time to actively develop my plugins. Damn university sucks the life out of coding and gaming these days :/
  22. Like
    goigle got a reaction from Albo1125 in Last Ditch Effort to Save Callouts...   
    Also, while not required, I split all of my callouts into separate files for organization and testing. It's a lot easier to read that way too.
  23. Like
    goigle reacted to Fiskey111 in Last Ditch Effort to Save Callouts...   
    There is no crash- it just seems like for some reason my callouts like take over the control of the AI and don't hand it back to LSPDFR.
     
    Thanks for that!  Good to know!  I'll make sure to do that from now on!
    I didn't try that yet.  My goal is to stay up all Thursday night and basically doing that.  I'll set each call to always and only enable one at a time and test them over and over.  Hopefully that'll tell me whether it's all of them or just one callout doing it.  I just wasn't sure if there was something I missed in the update to 0.3 that caused this to happen.
     
    Thanks guys!  Hopefully I'll be able to figure out this.  I won't be able to for a bit, I'm super busy the next couple days.
  24. Like
    goigle got a reaction from Kal74 in [WIP][REL] Federal Callouts   
    I don't remember if I mentioned the name of the callout I'm working on but it's basically going to be human trafficking. I'll make it so you can do it from the ground or the air. My custom backup menu will help with that - it will let you send the units in so you don't have to land!
     
    I'll also try and get another surveillance callout that can be done from the air created as well. I don't really know why but I feel really inspired to do this right now lol
  25. Like
    goigle got a reaction from Darkmyre in wip Plugin tool   
    OK, so ignore my previous thread which is a different (but in the same realm) idea. It was full of other now irrelevant information as well but I cannot delete it :^)
    Anyway, I'm going to preface this by saying I am making this tool anyway for Federal Callouts (and whatever other plugins I make, when work decides part time < 40 hours)
    It's going to be similar in some aspects to Albo's troubleshooter but a bit different in terms of functionality.
    It's probably going to to be FOSS (as long as there aren't any issues with using third party libraries like RPH and LSPDFR which I am pretty sure there aren't, someone mentioned it though). I want it to be FOSS so that if another author wants to use it then they can just bundle a working version of it in their plugin and not worry about license / attribution / etc.
    The goal is to create a tool that can be bundled with plugins that help users make sure they're installed correctly but also help us, the developers, in helping the users more quickly and efficiently.
    Here's what I want it to do:
    Dynamically load plugin specification XML files that contain plugin name, (maybe version), ID, and the files the plugin has. These specification files will be automatically generated (except for name & ID, and when I get to it a dependency field [with library version number]). Make sure all files are in the right location & exist Check for updates of plugins (this will be done outside of the game) Make sure LSPDFR is installed correctly (this is a maybe - albo's tool already does this so it's not high on the priority list) Provide the user with a GUI for editing ini files with minor input sanitation to make sure they don't put words inside integer values or integers in booleans etc (this is medium priority, it'll probably be specified in the plugin specification XML but will not be mandatory) If the user still has trouble, they can automatically generate a debug html file that will have their RPH version, their RPH.log, LSPDFR version, game version, OS, and will log all plugins. They can then simply attach the HTML and the developer can open it for easy viewing. Be completely dynamic so support for other plugins can be added by the plugin without needing to recompile the tool Maintain backwards compatibility as best as possible. Ex. a plugin that doesn't get updated but has an older version bundled (and the user accidentally overwrites the newer version) will still work with newer specification files as best as possible. I'm hoping to upload it to GitHub Tuesday night but it might end up being closer to Friday.
    It's going to be written with WPF as of right now
    The idea right now seems OK but I am looking for ideas on how to make it better. I also need a cool hip name for it (other than "Configuration Tool" lmao) :~)
    edit:
    oh yeah the point of this thread was to see if there was any interest in people contributing / using, if not I won't bother with github
×