Summerfall Roleplay System (Alpha) - Developer Log

FiveM Server Development Server Bazaar
,
1

Hey! We decided to start a new development: creating a new roleplay server.
But this it not all thing… We creating a very new introduction, in the next 2-3 years of the development.
So, this is our developer log. In here we do these tings:

  • Share our ideas
  • Share the development process
  • Talk about the project
  • Discuss our plans with the community

The development starts in this year december (as we planned before),
and we wants to create a different type of roleplay.

Developing this is exciting, we not want to give up.
First things first, thx for the community all of future help and ideas.

With love, Ben from the Summerfall Interactive Team.

1 Like
2

DevLog #1 - Used ideas

Hey! It’s me again…
Today I asked my devmate, which platform is better? He sayed this: “When we start to learning the ESX?”
So, we decided, using the ESX Legacy first. Because that code is simple to learn, and most of resources work on it. Then, if we learn it, and creating a few resource, changeing to the ESX Reborn version.

We have some ideas now, to start somewhere this development:

  • Creating a fullcom dispatch system
  • Reworking fully the ESX Menu and Dialog
  • Creating a new administration system (with in-game and website functionality)
  • Creating a language switcher system (for different players in one server)

This is our plan firstly. This log is keep updated.
With love, Ben from the Summerfall Interactive Team.

3

DevLog #2 - Starting Notifications

Hello, again!
We created a simple notification system, what uses Bulletin.
This script have a lot of configuration, but yet just a simple standalone script.

Later we want to re-coding to ESX Legacy…

A little sneek peak (not all the code):

-- Normal Notification
RegisterCommand('example', function(source, args)
    if allowedToUse then
        exports.bulletin:SendAdvanced({
            message = table.concat(args, " "),
            title = "EXAMPLE JOB",
            subject = "Notification",
            timeout = 5000,
            theme = 'info',
            icon = 'CHAR_CALL911',
            exitAnim = 'fadeOut'
            })
    else
        exports.bulletin:SendError("ERROR MESSAGE HERE", 5000)
    end
end, false)
-- Pinned notification with UniqueID
RegisterCommand('examplepin', function(source, args)
    if allowedToUse then
        local id = exports.bulletin:SendPinned({
            message = table.concat(args, " "),
            title = "EXAMPLE JOB",
            subject = "Pinned Notification",
            timeout = 5000,
            theme = 'info',
            type = 'advanced',
            icon = 'CHAR_CALL911',
            exitAnim = 'fadeOut'
            })
        if pinnedMessages.EXAMPLEID == nil then
            pinnedMessages.EXAMPLEID = {id}
        else
            table.insert(pinnedMessages.EXAMPLEID, id)
        end    
    else
        exports.bulletin:SendError("ERROR MESSAGE HERE", 5000)
    end
end, false)
RegisterCommand("removeEXAMPLEpin", function(source, args)
    if pinnedMessages.EXAMPLEID ~= nil then
        exports.bulletin:Unpin(pinnedMessages.EXAMPLEID)
    end    
end, false)

Future plans for this code:

  • Creating a configurable message system for ESX Legacy (config.lua)
  • Creating a multilanguage system for this script
  • Creating a modified configuration for all jobs

We prepared for the future…
With love, Ben from Summerfall Interactive Team.