KaMi

Members
  • Content Count

    152
  • Joined

  • Last visited

  • Days Won

    1

KaMi last won the day on April 6 2019

KaMi had the most liked content!

Community Reputation

28 Good

7 Followers

About KaMi

  • Rank
    Busta

Details

  • Gang
    grouv 4 laif
  • Location
    Argentina
  • Occupation
    Noob Scripter y noob mapper
  • Interests
    Hago esto porque me gusta.

Recent Profile Visitors

2,387 profile views
  1. KaMi

    [REL] The Red Zone

    SOLVED. Thank you for reply
  2. KaMi

    [REL] The Red Zone

    well, I realized the gamemode has a little bug so I decided to fix it and put some new things: Settings: <settings> <setting name="*RoundTime" value="[10]" /> <!-- Round Time ( Default: 10 mins ) --> <setting name="*Zombies" value="true" /> <!-- Enable Zombies? ( Default: true ) --> <setting name="*MinPlayers" value="[0]" /> <!-- Minimum players to play. If the value is 0, bots will spawn ( can cause some lag ) ( Default: 4 ) --> </settings> If the value of 'MinPlayers' is 0, Bot soldiers will spawn and the 'single player' mode will start. Bots: Bloodtox bomb ( a powerful toxin that can cause a great health loss in the prototype ) Double Impulse ( 'W' two times ):
  3. Hello ! i'm back again with my first gamemode based on [PROTOTYPE] and [PROTOTYPE2] games. The context is simple. A secret government agency ( called Black Watch ) has to fight against a guy with superhuman skills in a post-apocalyptic place called 'The Red Zone'. The Black Watch Team has three ranks: Trooper - Commander - Pilot. Each rank has its own skills and respective vehicles as the black watch team, the superhuman (Prototype) has a wide variety of skills, attacks and transformations Also during the course of the gamemode, certain events occur such as: Super Soldiers Airstrikes & Others. Note: this gm needs at least 4 players to run ( or you can also change it cause is an Open Source script ) Thx for your time ❤️. Download the resource here
  4. KaMi

    [REL] Misterix Mod V1

    Resource special update. Look description.
  5. Intentá esto --CLIENT addEventHandler("onClientRender", root, function() -- Con esta función se tomará el interior del jugador constantemente. local int = getElementInterior(localPlayer) -- Se toma el interior del jugador. setElementData( localPlayer, "Interior", int ) -- El dato "Interior" guarda en que interior se encuentra el jugador. end ) addEventHandler("onClientElementDataChange", root, function(key,oV,nV)-- Esta función se iniciara cuando se detecte un cambio de interior por el jugador. if key == "Interior" then -- Detecta si el dato que cambia es "Interior". triggerServerEvent( "onPlayerInteriorWarped", source, oV, nV ) -- Inicia un evento enviado al lado del servidor donde source es el jugador que cambió de interior, oV es el antiguo interior y nV es el nuevo interior. end end ) --SERVER addEvent("onPlayerInteriorWarped", true) -- Añade el evento 'onPlayerInteriorWarped' al lado del servidor. addEventHandler("onPlayerInteriorWarped", root, function(oldInterior,newInterior) -- Tu función. if oldInterior == 0 then toggleControl( source, "fire", false ) elseif newInterior == 0 then toggleControl( source, "fire", true ) end end ) Si no funciona es porque capaz tenés algo mal en el meta porque el que te pasaron estaba perfecto.
  6. Amigo, tu código no tiene mucho sentido... Te daré una pequeña ayuda con este y después lo continuarás tú para que puedas aprender. --CLIENT addEventHandler("onClientRender", root, function() -- Con esta función se tomara el interior del jugador constantemente. local int = getElementInterior(localPlayer) -- Se toma el interior del jugador. setElementData( localPlayer, "Interior", int ) -- El dato "Interior" guarda en que interior se encuentra el jugador. end ) addEventHandler("onClientElementDataChange", root, function(key,oV,nV)-- Esta función se iniciara cuando se detecte un cambio de interior por el jugador. if key == "Interior" then -- Detecta si el dato que cambia es "Interior". triggerServerEvent( "onPlayerInteriorWarped", source, oV, nV ) -- Inicia un evento enviado al lado del servidor donde source es el jugador que cambió de interior, oV es el antiguo interior y nV es el nuevo interior. end end ) --SERVER SIDE addEvent("onPlayerInteriorWarped", true) -- Añade el evento 'onPlayerInteriorWarped' al lado del servidor. addEventHandler("onPlayerInteriorWarped", root, function(oldInterior,newInterior) -- Tu función. --TU CODIGO end ) Te aviso que no probé el script así que, si hay un error, dime. Mucha suerte
  7. ¿ Creaste la función que inicia el evento "onPlayerInteriorWarped" ? ¿ Si es así, podrías pasarlo ?
  8. In Game -> Admin Panel -> Resources -> Manage ACL -> Click on Admin -> Click on Add object in group -> Type "resource.resourceName" Example: resource.loginPanel
  9. They work... you must give admin rights to the resource.
  10. use: onClientPlayerDamage setElementData setTimer Example: --Not tested local timeEffect = 10000 addEventHandler("onClientPlayerDamage", getLocalPlayer(), function() if ( getElementData( source, "antiEscape" ) == false ) then setElementData( source, "antiEscape", true ) setTimer( setElementData, timeEffect, 1, source, "antiEscape", false ) end end ) --Your teleport code addCommandHandler("teleport", function() if ( getElementData( localPlayer, "antiEscape" ) == false ) then --teleport code else outputChatBox("You can't escape !" ) end end )
  11. KaMi

    object collision

    triggerClientEvent -> SERVER SIDE ( Pass the player variable and the object ). setElementCollidableWith -> CLIENT SIDE.
  12. KaMi

    Fast sprint script

    hmm i think you can use bindKey and setGameSpeed
  13. You can try this but i think there can be other forms. addEventHandler("onPlayerWeaponFire", root, function( weapon ) if weapon == 34 then --detect if weapon is sniper ( id 34 ). giveWeapon( source, 34, 1 ) -- faster weapon reload. end end )
  14. Scoreboard it's a default resource. You can stop it typing /stop scoreboard.