[FilterScript] sampctrl - Show your server's changelog easily (/updates)
#1

What is this?

It's an /updates command! Yes. That's all for now.


Like me, many of you update your server. But it's just so annoying to keep repeating yourself. This filterscript aims to pretty much eliminate the effort of answering:



Now, many people I know who run servers probably manually code this in or have a tedious system to showing changes. Literally, stuff that and use this. It will save you time, especially when it comes to thinking about what you added...

/updates

This command shows the most RECENTLY published changelog by your project on RevCTRL and shows it in a dialog. As you code your features, add revisions to your project and then publish the changelog when you update.

The web server handles all the beauty. You can grab the .php script and modify it.



Setup

You must edit two things in the pawn file and compile it! That is:
  1. Define PROJECT_ID with your project ID on RevCTRL. You can find this in your project's about page.
  2. Define USER_PROJECT with your Username/Codename (ex. IrresistibleDev/SF-CNR)
There are examples in the .pwn of how it should look and what not.

ADVANCED: If you don't want to rely on my website URL, download the .php script into your web server and change the URL specified in the filterscript. Should be good from thereon.

Download

Github: https://github.com/zeelorenc/sampctrl

Download revctrl.pwn
Download revctrl.php

My server uses the filterscript so there will be updates/implementations when required.

Most recent changelog



Write below if you have any questions or PM me! I use the filterscript personally and will actively develop it probably over time. It's kept as simple as possible that way integration is simple.

Bugs etc, report here or on the project's revctrl page (click here)

RevCTRL itself is a changelog management system, you can read more about it on the site itself. Use a temporary email if you're fussy about registration and are interested.
Reply
#2

Nice
Reply
#3

Amazing, +rep
Reply
#4

Very Useful +REP
Reply
#5

God Joob!
Reply
#6

The one thing I have noticed is you don't check that the project is valid.
You can simply check if the returned data string is {"status_code":404,"message":"Project not found."} and if it is the project is invalid.
Reply
#7

Quote:
Originally Posted by Abagail
Посмотреть сообщение
The one thing I have noticed is you don't check that the project is valid.
You can simply check if the returned data string is {"status_code":404,"message":"Project not found."} and if it is the project is invalid.
You mean on my URL or the .php script? It should return nothing if the project is invalid - I made it behave like that intentionally.

Код:
if ($jsonData) {
That part does it all. I would assume that users of this are automatically putting a valid project ID anyway

Cheers
Reply
#8

But it still seems to show the dialog if the response code is 200, thus rendering a blank text. I have made a pull request on GitHub if you want to take a look.
Reply
#9

Seems very nice, congrats, +6
Reply
#10

Quote:
Originally Posted by Abagail
Посмотреть сообщение
But it still seems to show the dialog if the response code is 200, thus rendering a blank text. I have made a pull request on GitHub if you want to take a look.
Yep I see what you mean, good pickup. Anyhow, I still can't manage to see your pull request. I do see that you've forked it however.

I probably might do it myself tomorrow: force a 404 not found with the PHP script if nothing could be determined.
Reply
#11

how do i use this?
Reply
#12

Actually looks pretty decent, shame my Laptops broke otherwise I'd of tested it.
Reply
#13

Quote:
Originally Posted by PowerF
View Post
how do i use this?
https://github.com/zeelorenc/sampctr...er/revctrl.pwn

1. Grab that code, paste it into your filterscripts section
2. Modify PROJECT_ID with your RevCTRL project ID.
3. Modify USER_PROJECT with your "Username/Projectname"
4. Compile, load it onto the server

Let me know if you're having issues.

Cheers for comments once again
Reply
#14

This is nice and useful, simplistic but the concept is there.
Reply
#15

Nice work +rep
Reply
#16

Very nice!
I have an ideea for the next update. Make a DIALOG_STYLE_LIST with all versions.
Reply
#17

Looks great, good work Lorenc!
Reply
#18

Good Job
Reply
#19

good job bro
Reply
#20

Quote:
Originally Posted by ExTaZZ69
View Post
Very nice!
I have an ideea for the next update. Make a DIALOG_STYLE_LIST with all versions.
Yes I will make that, maybe this week if I have time!

Thanks for the comments
Reply


Forum Jump:


Users browsing this thread: 4 Guest(s)