CS2D General CS2D Bug Reports
LUA ERROR: attempt to call a nil value
Mami Tomoe: I think that error message gives sufficient amount of information to be able to pinpoint the problem. The "Attempt to call a ... value" is also used for other types that are not nil. Mami Tomoe: You have to prevent those errors yourself by writing proper Lua. Don't try to access values/methods which don't exist.
Mami Tomoe hat geschrieben Quattro: you need to use the image's direct link (https://i.imgur.com/F6y2beL.jpg) between the [img] tags for it to display. 
Mami Tomoe: The second parameter of the timer must be a string and the string must contain the name of a global function to run, otherwise it will throw that error. Perhaps there should be a check in the timer function to throw a more acceptable error message. Quattro: there are only 50 HUD IDs from 0-49 as far as I know. But you can recycle the old one if you want. Unless you absolutely want more, not many script need to display over 50 lines of HUD text on the scene at the same time. Maybe create a table to keep track of unused HUD ID and use them when needed. Or group some of them together if they are on the same y coordinate. FishyFinThing: No, the limit has been raised with the last update. Quattro: That bug has already been reported and also fixed for the next update. It has just not been released yet. Hajt: Repeating bugs which already have been reported does not make me fix them faster. So please don't repeat reports. I'm aware of this issue but it is not trivial to fix. Therefore I can't tell you if/when it will be fixed. Mami Tomoe: That's something different. I wasn't aware of it. Most of this (except for air strike explosion speed) sounds like an "edge case" though as these situations should not occur in normal game play unless you decide to give players insane amounts of these items (which you shouldn't as it makes the game basically unplayable as EVERYTHING simply explodes). Will check. Note that there's a projectile limit of 255 per player. If you exceed it bad things may happen. Can't tell what exactly without checking the source. Hajt is talking about is simply a sync error with the projectile movement (most likely to happen when wall collisions are involved) mrc: What? 
This sounds horrible. I have never seen such things and can't think of a reason why this might happen. A way to reproduce these issues would be required in order to find the reason / a way to fix it. 
CS2D Bug Reports
Offline