Mr_Moose

guiSetVisible ( GUIEditor.window[1], false )

That's why I told FlorjanMTARP to use debugscript In my first reply I only read the code so I guess this became a human error from my side.

You're right, it is missing. Strange that it didn't returned any errors then, did you checked /debugscript 3? That's a good way to find this kind of errors.

I don't think anyone will do that for free, why don't you just read a simple beginners guide to scripting guide so you know how to use that piece of code instead.

Can't really find anything that seems wrong in your script but there are two things you might want to try after all: Don't name your marker variable "marker" since it's also a class name, use something else instead. And don't forget the event handlers. You might also add the second argument to the hit and leave functions which is matching dimension: https://wiki.multitheftauto.com/wiki/OnClientMarkerHit

That means "getElementData(source, "deaths")" isn't defined, you need to handle the special case when it's nil: (getElementData(source, "deaths") or 0)

You forgot the end of your function, see this sample function for correct syntax: function sampleFunction(args) -- ... end

MTA Lua and programming is NOT the same thing. C/C++/x86 assembly and programming aren't the same things either. Not a single programming language or scripting engine is the same thing as "programming". Why are you even discussing this? You do programming when you write a program and you do scripting when you write a script, two different words that means kind of the same thing in practical terms. You write the code/script and you execute it or let another application execute it for you, still pretty much the same. I'm pretty sure LinKin's point was the logical thinking which is required in both cases, no need to get upset over a small language mistake.

Download just the 1.4 server and let those files overwrite your old 1.3.* server. I tried that method on Linux but there is a small risk of failure so make a backup of your current server and try on that one to verify that it works before overwriting important files.

You may also try letting the 1.4 server files overwrite the old ones, make sure you remove log files and resources from the 1.4 server to make sure that stuff won't be overwritten, make a backup and try on that one to make sure it's safe. Large scale servers will always deal with this type of issues so copying everything and try in small scale first is often the best solution. Databases can easy be viewed and managed with applications like this one: http://sourceforge.net/projects/sqlitebrowser/?source=recommended

That should work theoretically but don't forget to take a backup, just in case it fails.

Have you tried this? http://code.albonius.com/?action=download&id=6da85f73be5914342a14abed0e7921a5

It's fully depending on your own scripting skills, you need be able to understand eventual errors, if you do then it's easy to install. Most stuff in this works out of the box as well and other stuff are easy to reuse if you want to make a new system but not from scratch.

You never added thePlayer as an argument to the payout function, check the timer that calls the function robTimer and make sure you set the first function argument (argument 4 in the timer function) to the player variable like this: setTimer ( robTimer, 30000, 1, player ) on line 61. Also change line 59 so it can receive the player element, that chatbox output on line 60 is visible to all currently and will also be fixed by the next step. Now edit line 59 to this: function seconds30(player) That will let the function receive the player so it can be used within it. And finally, at line 56 which needs the player element, change line 56 to this: setTimer ( seconds30, 30000, 1, hitPlayer ) And that should solve everything related to missing player pointers as well as payments.

exitMarker and robMarker is never created, you added them into a function which is never called and then you assign their event handlers as soon the resource is started. Move the event handlers to a place below where you defined the markers and add another event handler for onResourceStart to trigger the function.

Probably to advanced for you to understand , but in all seriousness, it is a complete wanted level system with police job and many other useful features. A full CnR system in beta state. If you only want the actual wanted level you should probably write something yourself like this: addEventHandler( "onPlayerWasted", getRootElement( ), function(ammu, attacker, weapon, bodypart) setPlayerWantedLevel(attacker, getPlayerWantedLevel(attacker) or 6) end )

Leave blank, the server will find that info automatically in most cases. Secondly you need to port forward your server from your router. See this: http://portforward.com/

I see, you where looking for a way to disable calls to fadeCamera from a compiled resource, next time you might describe that in the main post to get the help you're looking for.

That would be even worse, it's also incorrect according to the syntax. Try just running this: fadeCamera ( false, 10, 0, 0, 0 ) And observe the result from within your server.

It's a bad idea, fadeCamera has it's own rendering system, you already specify details such as time to fade, what color to fade to and in/out in the function arguments. Putting it in onClientRender would be like calling a timer from another infinite timer, a huge waste of performance and your server might crash due to stack overflow in worst case scenario.

You could try cloudflare which has free DDoS protection, not sure how good that is but it seems reliable at least.

Never heard of a resource like that but it's simple to make however, see this: https://wiki.multitheftauto.com/wiki/Textdisplay, as soon "onPlayerJoin" is triggered you create a text element server side which will be displayed while downloading, not sure if you can show images while downloading thought.

You're getting a stack overflow there. The timer will do it's work forever due to argument three which you set to '0' and each time the function is called you're starting a new timer that continues forever, the result is an infinite amount of timers that spam this function. Most compilers or frameworks has protection against this, i.e know already from the start that everything will fail, the shutdown is a security process to prevent more serious issues like a full system crash like BSOD on Windows.

If you want help then don't ask people to "shut up", calm down for a while, read a beginners guide to scripting to understand the basics like this maybe. Then you can ask for help.

ac-police is available here: http://code.albonius.com/?action=download&id=8523e282173778cc46739ae4405d3784, you may also remove the exported calls to the resource ac-police and replace them with your own wanted level system or put the value '0' in there to disable checking of wanted level when spawning a vehicle. I should have published them both in the community I guess. Use CTRL + F in your script editor to find the exports within the script to handle them in a proper way.