Drgenius a dit :

Also something that would be neat is coloring for each type of argument required (or sent in events), for example, green for string, white for int, blue for float, orange for bool, etc. Just a thought.

That would be quite redundant and is unneeded in my opinion.

Safwanrockz a dit :

Drgenius a dit :VoirMasquer

Also something that would be neat is coloring for each type of argument required (or sent in events), for example, green for string, white for int, blue for float, orange for bool, etc. Just a thought.

That would be quite redundant and is unneeded in my opinion.

^this

also liam could you rearrange the functions in alphabetical order
makes searching easier

Thanks Liam! *-*

Safwanrockz a dit :

Drgenius a dit :VoirMasquer

Also something that would be neat is coloring for each type of argument required (or sent in events), for example, green for string, white for int, blue for float, orange for bool, etc. Just a thought.

That would be quite redundant and is unneeded in my opinion.

I don't understand how it would be redundant. Maybe I should clarify, here's an example:

a dit :

tfm.exec.movePlayer(playerName, xPosition, yPosition, xOffset, xSpeed, ySpeed, yOffset)

There could be a key at the top, something like

a dit :

String
Bool
Integer
Float

It would also be easier to distinguish different arguments, and on the eyes

It's still redundant. I don't want to see a colorful documentation nor do I have to memorize which color is which variable type.

Really, why we ca't using chatMessages on tribes? Also, you may make /slua to disable chatMessages in tribehouses for you.

mengineer a dit :

Really, why we ca't using chatMessages on tribes?

Because it's incredibly abusable?

Haruhitastic a dit :

mengineer a dit :VoirMasquer

Really, why we ca't using chatMessages on tribes?

Because it's incredibly abusable?

This could be dealt with by preceding messages with something like "[~Module]" or limiting text formatting abilities.

^ This. Or Maybe, can't use in for/loops.

There is now only one id for the cannon it's 17 and then you have to rotate it .

that... sucks man ...

Thewav a dit :

There is now only one id for the cannon it's 17 and then you have to rotate it .

Thanks for that update, it seems to have broken other modules that rely on cannons like #domination and #ffarace, hopefully they'll all be fixed today.

If I link an image to a player ( tfm.exec.addImage( link.png, "%Tigrounette", -30, -30) ) and if a new map begins, is the image removed ?
Same question if the player dies and then is respawned.

v Ok thank you :)

Yes and yes.

Added the new shaman object IDs (pokeball, bubble cannon, leafy trampoline and rock anvil).

Very cool. I kinda learned something but I didn't get much..
Really cool though! :-)

Does anyone know how to watch everyone's x and y? I think you use player.x and player.y but it's not working in my code.

By saying "watch" do you mean like continually change the value of a variable with the player's coordinates?

I mean like if a mouse enters an area, then they get killed.

Then you'll have to use eventLoop() that triggers every half a second, so you can continually check the player's coordinates (and pythag() for the circular collision):

ax = 200 - X coord of area
ay = 200 - Y coord of area
ar = 40 - radius of the circular area
function eventLoop()
for i,v in pairs(tfm.get.room.playerList) do
if pythag(v.x, v.y, ax, ay, ar) then
tfm.exec.killPlayer(i)
end
end
end
function pythag(x1,y1,x2,y2,r)
local x=x2-x1
local y=y2-y1
local r=r+r
return x*x+y*y<r*r
end