Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - .
32
Off-Topic General / Re: Game Recorder
« on June 28th, 2018, 09:24 PM »
Best in the business obsproject.com
33
Community Plugins / Re: SQLite module for Squirrel.
« on June 24th, 2018, 11:32 AM »
  • Updated the plug-in for the new SDK
  • Updated the SQLite library (3.24.0).
  • Included a CMake build system

Binaries are on the repository. Check the first post for more details.
34
Community Plugins / Re: Master-list announce.
« on June 24th, 2018, 11:32 AM »
  • Updated the plug-in for the new SDK
  • Updated the Mongoose library.
  • Included a CMake build system

Binaries are on the repository. Check the first post for more details.
35
Scripting and Server Management / Re: Building Server Plugins
« on June 19th, 2018, 09:38 PM »
Quote from umar4911 on June 13th, 2018, 08:08 AM
There are many function I want to add. One of them is auto-record a video in server-side.
From what source? I mean, what gives(streams?) you the video data to the server. And what are the contents of that video.

Chances are to be possible. But not if you intend what people are already thinking.

Also, encoding video files may not be as easy as `print(GetINIOption("player_password"))`. So be wary of the task you're attempting.
36
Closed Bug Reports / Re: GUILabel bug.
« on June 17th, 2018, 11:24 AM »
Code: [Select]
Property TextColour / TextColor (bound)
Type: Colour

https://forum.vc-mp.org/?topic=2719.0
37
VC:MP Announcements / Re: Permanent new updater URL
« on June 11th, 2018, 03:15 PM »
Quote from rww on June 11th, 2018, 12:37 PM


nice compression
Or maybe the installer doesn't come with the DLLs that are injected into the game. And those will be downloaded individually when you join a server.
38
General Discussion / Re: Fireside chat: the future of VC:MP
« on June 10th, 2018, 05:43 PM »
Quote from vitogta on June 10th, 2018, 04:05 PM
...For example will be official squirrel plugin be supported or SLC will move us to his one? ...
You just assumed I will be a developer on the VC:MP mod. You guys should really not assume these things.
39
Quote from Sebastian on June 5th, 2018, 05:29 PM
About the switch( type.tostring() ) you are right. But don't know what to say about the "break;" thing you also elaborated. Maybe in Squirrel it is not mattering that much ? I've using it like this, without scopes, and didn't face problems :/
And you never will. Because it works like that too. I said, they're usually added after the braces as a separate statement. In fact you can put that break; in any number of nested scopes, and it still throws you out of the switch.

Code: [Select]
switch (x) {
case y: {
{
{
{
{
break;
}
}
}
}
}
}
40
If something fails and you don't know why. Wrap it in a try/catch lock and print the error to chat/console. In fact, all your event functions should be wrapped in something like that. Otherwise, you're forced to look into a text file just like a primitive. And things get even worse if that log file is buffered. Because you have to stop the game to flush the buffer. Although logs are not usually buffered. Otherwise you risk loosing information if there's a crash. But who knows.

Secondly, probably off-topic but that `switch( type.tostring() )` code is welcoming bad practice. Never convert to string. If `type` is not a string. Then make the code complain about it. Just say `hey dude. I know you think you can be versatile here. but one of these days, you're gonna change something in this type and I'm not gonna get "window" in return. and then you shall witness my wrath. *smiley-face*`.

And as a nitpick, that `break;` is usually after the scope. like:
Code: [Select]
switch (x) {
    case y: {
        //...
    } break;
}

Because a case inside a switch can (should? I suppose it depends on the language) only have one statement. And by using curly braces. You turn multiple statements into a single one. And if you declare variables inside that statement you basically forced to use curly braces. Which is why, after the curly braces (which are seen as a single statement) comes the break; which is seen as a separate statement. The switch case acts a bit differently than a loop.
41
General Discussion / Re: Fireside chat: the future of VC:MP
« on June 4th, 2018, 10:48 AM »
@Zurix That was an exaggeration. I don't care about broken text (up to a point). I meant that they just come and request. And then we have to deal with their issues because they can't read documentation either.
42
General Discussion / Re: Fireside chat: the future of VC:MP
« on June 2nd, 2018, 05:12 PM »
@vitogta don't confuse server admins with forum admins. when you do that next time, realize that the server admin is just a another player (like you) that gave himself (themselves?) that "privilege".
43
General Discussion / Re: Fireside chat: the future of VC:MP
« on June 2nd, 2018, 11:06 AM »
Quote from vitogta on June 2nd, 2018, 10:43 AM
he is also inactive.
all people who good in coding also having a job... very unexpected fact.
I am not inactive. I've simply moved to a different community. One where you can actually have a coherent discussion and not just `wAnt scriPTs and CMd. GIvE!!!`. Which has been the case when the developers stopped visiting the forum. We all thought the project was abandoned and there was nothing to be done about.

Yes I do have a job. And while I have that I still fiddle with code whenever I'm home because I simply enjoy it. And it's actually a way for me to release some stress.

I've been asked about the dev thing on Discord. And the answer was yes. But not like old days. More like casual maintenance. Even that would be better than nothing.

Anyway, I guess what I'm trying to say is that I was not inactive but that there was simply nothing to be active about anymore.
44
Scripting and Server Management / Re: Pickup.Remove() Problem
« on April 15th, 2018, 05:35 PM »
Code: [Select]
try {
    FindPickup( text.tointeger() ).Remove();
} catch (e) {
    print("Can't deal with it now!");
}
45
SLC's Squirrel Plugin / Re: Sqmod . ini
« on December 29th, 2017, 04:53 PM »
That's a configuration file used by the plugin. What scripts to load and what debugging options to apply. Among other things.

Example:
Code: [Select]
# Squirrel options
[Squirrel]
# Configure the virtual machine stack size
StackSize=2048
# Enable error handling by the plugin
ErrorHandling=true
# Allow the plug-in to load even if no scripts were loaded
EmptyInit=false

# Logging options
[Log]
ConsoleDebug=true
ConsoleUser=true
ConsoleSuccess=true
ConsoleInfo=true
ConsoleWarning=true
ConsoleError=true
ConsoleFatal=true
LogFileDebug=false
LogFileUser=true
LogFileSuccess=true
LogFileInfo=true
LogFileWarning=true
LogFileError=true
LogFileFatal=true
ConsoleTimestamp=false
LogFileTimestamp=true
#Filename=mymod%Y-%m-%d.log
# How much to output to console at startup
# 0 minimal, 1 show more, 2 show even more, 3 show even more
VerbosityLevel=0

# List of scripts to load
# - Compile=path > Compile the script and execute after all scripts were compiled
# - Execute=path > Compile the script and execute it immediately
# - Section=name > Search for more scripts in a different section
[Scripts]
Execute=bootstrap.nut

# Custom script options
[Options]
MyOption="Hello from config!"