IIYAMA

This might be your problem: http://www.lotrointerface.com/forums/sh ... php?t=3502

When I am busy with important stuff, I can't help you right away. Not that you think, I gave up on helping you... don't judge too soon.

Hazard lights are simply recreated with vehicle lights why use custom lights? Hazard lights: Because it gives a nice effect when doing that.

https://wiki.multitheftauto.com/wiki/CreateLight

This is the Part When i Call the outputMessage In Server Side (My Mod) So it might be not "outputMessage" , maybe it's "player:outputMessage" just like in the "business" mod server side The code from the screenshot does not have the same structure as: call(getResourceFromName("business"), "outputMessage", source, "the message bla bla bla...", 0, 245, 33) Take a closer look, it is messed up.

I see this:

Well, use the feedback I gave you on those. Because their structure are still not the same, as you said you did: call(getResourceFromName("business"), "outputMessage", source, "Server Side Message Check", 255, 0, 255)

I just want to see your Server.lua File.

https://wiki.multitheftauto.com/wiki/On ... ayerDamage element attacker, int weapon, int bodypart [, float loss ] local newHealth = getElementHealth(localPlayer)+loss-5 if newHealth > 0 then setElementHealth(localPlayer, newHealth) else setElementHealth(localPlayer, 0) -- or triggerServerSide + killPed end

if weapon ~= 23 and weapon ~= 3 then -- add wanted end https://wiki.multitheftauto.com/wiki/OnPlayerDamage

It all depends how you make them wanted. You have to prevent it from happening in the code that is responsible for it.

RED or GREEN if attacker and getElementType(attacker) == "player" and weapon == 23 or weapon == 3 and wanted > 0 then How to solve: (weapon == 23 or weapon == 3) if attacker and getElementType(attacker) == "player" and (weapon == 23 or weapon == 3) and wanted > 0 then

and from where are you testing that code? Because it seems that, that code doesn't provide a valid source element.

1: Are there errors/warnings? 2: >if (settings.info_messages_type == "dx") then< is info_messages_type in the meta.xml set to dx?

Show your edited code.

Yes, that is correct.

There is no server communication needed, since the position of the players is already synced. You need to check it per player. And use another table structure. Something like this would do: local linePoint = { [player thePlayer] = { {float x, float y, float z}, {float x, float y, float z}, {float x, float y, float z}, {float x, float y, float z} } }

call(getResourceFromName("business"), "outputMessage", source, "the message bla bla bla...", 0, 245, 33) The source in this event is the player element.

The problem is with the export from resource you are exporting from. The player element you use in your export isn't valid. I recommend you to post your own code.

When you remove row 6, row 7 moves down to row 6. So when you start with 7 and count down to 4, you don't have that problem. guiGridListRemoveRow ( tGrid, row7 ) guiGridListRemoveRow ( tGrid, row6 ) guiGridListRemoveRow ( tGrid, row5 ) guiGridListRemoveRow ( tGrid, row4 )

fill in >"r", 'g', 'b'< in with a value between 0 and 255. 255, 0, 0 = red color 0, 255, 0 = green color 0, 0, 255 = blue color Or mix the color channels until you have the color you want. And you are ready to go.

Tables would be a better solution, but you seems not to use them. So... local VIP = getElementData(localPlayer, "VIP") if VIP == "Bronze" then if button == "1" then elseif button == "2" then elseif button == "3" then end elseif VIP == "Silver" then if button == "1" then elseif button == "2" then elseif button == "3" then elseif button == "4" then end elseif VIP == "Gold" then -- .................. else -- not VIP or unknown kind. if button == "1" then elseif button == "2" then end end

Because it uses less memory. I prefer to use only the lua memory and not the MTA event system. Anyway, an event would be fine too.

Make dxOutputMessage an export function and you can call it from other resources. call

Sure, but that doesn't mean you don't have to add debug lines.