Why this is terrible, programming wise:
- It has no use of OOP, the foundation of all modern, proper programming
- It's as bad as your average source
- It doesn't use Boolean shortcuts
- It lacks the ease of reading a library should have (spaces between var=1 is always a plus >_>)
- It's very repetitive and has nearly no plug and play ability; it's more of a demo, albeit a terrible one
- Some segments use spaces, while others use tabs
- Useless loops in statpanel(); this would produce a good bit of overhead in a game with many players
- Possible extra overhead around istype(src,/mob) (rather than ismob(src))
- Some usr abuse
- Lack of a proper death check proc; it's within the Bump() proc (more repetitiveness)
- Certain things aren't typecasted, which can cause issues (the skills list for example)
- Useless extra checks for stupid things that shouldn't even be where they are
Presentation:
I liked the beam icon, just because it had that gradient-y style. It was still very subpar, though. Also, everything else is rather bad. This is a library/demo, though, so its understandable.
Originality:
There are much better, more well-known beam libraries out there. Check out Evi of au's beam library or Kaioken's beam demo instead (the latter may still need an update to improve a flaw or two, go nag Kaioken!).
Overall:
You could find better crap in a compost pile.