50p

You need to debug it. outputDebugString or outputChatbox, for everything that may be causing these warnings. If you get "bar argument" for any of these 2 functions, use tostring() function to convert variables to string. As you get "attempt to concatenate number values" it means you try to concatenate number with string, like this: "this is string which wants number: " .. 123 . As I said, debug every variable (output them to chatbox or debug window).

This was made ages ago for DP2.x. In the old days, garages were opened. I was planning to rewrite this for 1.0 with all garages that were used in SP but I'm busy with the Script Editor now. You can fix it yourself, just open file server.lua and add this: addEventHandler( "onResourceStart", getResourceRootElement( getThisResource() ), function( ) setGarageOpen( 15, true ); -- open Wheel Archangels when resource starts end )

It's very simple, just please try to read this step by step, don't go 1,6,7,2... Just because code executed from top to the bottom doesn't mean it goes straight to the chunks/blocks/functions, so follow the steps 1,2,3,... just like Lua engine reads it.

OK, I found out that it happens with every meta.xml that has the following XML Declaration, not the encoding the files was saved in but the declaration: It doesn't happen with: Nor: Try to modify all meta.xml that has 'encoding="utf-16"' (remove the entire line or change it to utf-. If you get different error after you modify the meta.xml please post it here. Sorry to say that but it's raceconv's fault which was probably made with .NET > 2.0.

Could you upload the meta.xml somewhere so I can download it and investigate?

Could you please send me the meta.xml which shows the error message? Not just the content of the file but the file itself. I think it's problem with the file encoding. These meta.xml files were probably made with a map converter and saved in unusual encoding format or a format that .NET 2.0 doesn't support. I think installing it with MTA would be nicer, but again, it's just alpha with patches. I may create an installer when it'll be more stable.

This is important that you know how the script gets executed. Take a look here: https://forum.multitheftauto.com/viewtop ... 00#p289183 I explained there the how scripts work. Follow the steps, 1,2,3,etc. because that's the order in which the code executes. Don't read it like the code goes (1,6,2,3...). After you read this, you should know why you get those warning messages.

Use the debug window to let you know whether there is something wrong. I'm sure you'll get "bad argument" warnings. /debugscript 3 (it's the command to show the debug window which will show you all warnings/errors/info messages)

Did you do what I suggested?

I'll give you a start. function CreateBlip(player) -- first make a blip visible for you only local blip=createBlipAttachedTo(player, 52, 2, 255, 0, 0, 255, 0, 10000, player ) setElementData( player,"omgblip",blip ); outputChatBox("Blip attached to you",player) -- then loop through every player and check if his skin is 211 for i, plr in pairs( getElementsByType( "player" ) ) do if ( getPedSkin( plr ) == 211 ) then -- so one of players is 211 lets make blip visible for him: setElementVisibleTo( blip, plr, true ); end end end addCommandHandler ("taxi",CreateBlip) function DestroyBlip(player) local blip = getElementData( player, "omgblip" ); if ( blip ) then destroyElement( blip ) outputChatBox("fare is being helped",player) end end addCommandHandler ("canceltaxi",DestroyBlip)

Who do you want to see the blips?

What you do, is actually moving the marker to another interior not the player. You move player to the position where the interior is but you don't change his interior. To solve it, just use setElementInterior with player/ped element in the first argument. You shouldn't move the marker at all, because when you enter that marker again it will be moved again to the same location, unless you do some checks. To solve that, simply make another marker instead.

https://wiki.multitheftauto.com/index.php?title=ACL You need to let your resource to use that function.

error is.

That's why it's called "alpha", robhol. Thanks to all who have sent bug reports. From these reports we know that the most common crash is caused by the .NET's XML file handling. I'll dig deeper into that tomorrow. We're trying to create dump files for more accurate debugging and we'll release next build as soon as we're done.

After you getPedOccupiedVehicle(), use outputChatBox or outputDebugString to see what clientVeh is. If it's "userdata" then it's correct. If not, then you're not in vehicle. Then outputChatbox or outputDebugString to see what each color variable is, like: outputChatBox( "colors from client: ".. red ..", ".. green ..", ".. blue );

Don't you get any errors or warnings? Both of your tries are correct but from what I see, you use string in the setVehicleHeadLightColor. Use tonumber() to convert string to number. Also, make sure that your clientCustom event is added server-side.

I don't know anything about Win 7 and why it crashes for you. Also, your bug report doesn't seem to be sent at all.

Sorry, I have no idea if it works on Windows 7. I don't have Windows 7. Have you clicked "Send report"?

I thought about that, but I think I'll add this in the future release. BTW, new screenshot added. Go to the first post. If you do do that, keep it generic - don't assume the groups are called 'admin' and 'moderator' as there's no reason they need to be! Look at how the webadmin does it (and try to simplify it). Yes, of course. EDIT: Updated screenshot in the first post. Now "suggested functions" window supports exported functions.

I thought about that, but I think I'll add this in the future release. BTW, new screenshot added. Go to the first post.

You have to have MTA installed and run a server... https://wiki.multitheftauto.com/index.ph ... ver_Manual

An update. New screenshot.

We don't know what your problem is. Don't set timer outside a function. You may find problems with that. Put it inside onResourceStart event instead.

After pretty long break an update has arrived. Added a window where you can modify your server configuration. I posted screenshot of it in the first post, go and check it out. Remember, if you have any suggestions don't hesitate and post them here.