![]() |
Inventory Script
PHP Code:
Even though I have already done these things, I would like to implent a new cleaner version into this item system. -Admin Item Generator (via GUI with no scripting involved) -Drop System -Bag Support (the item bag (Astram/Tools; Toad/Blah)) Enjoy this while you can, while I will be working on another :cool: |
Show us some screenshots?
|
Please don't release scripts like this into the code gallery. I really do appreciate your effort and that you're trying to help others, but releasing broken model scripts isn't the way to do it.
A couple things to work on:
Again, thanks for trying to help :). Let me know if anything I said doesn't make sense. |
Quote:
PHP Code:
|
Quote:
I don't know what beautifier you used, but it didn't work very well. You should be indenting and styling as you script anyway. The timer may work perfectly, but that doesn't mean it's correct. The smallest timeout possible is 0.05 seconds—there's no reason to make it look like you're using a smaller one. clientWidth and clientHeight are just the width and height of the element (excluding the border width/height). Set them like ordinary variables. |
I do like how astram has posted this, to me it demonstrates that gs2 is alot more powerful then gs1 when scanning for player attributes so basically efficiency wise.... Thanks astram for trying to help although I do tend to agree with chris's point about not being code gallery worthy. Your still in your learning days, yes?
|
Quote:
I don't think it's good to be too stingy about what qualifies for a "Code Gallery" script. If someone makes a script to their best effort and releases it, I think it's fine to post it here. If it isn't up to scruff, someone will hopefully give a breakdown of why, the script will be updated. Both the original scripter and future observers will learn something from the critique. My reasoning for this is that a discussion board will easily devolve into situation where an in-group is deciding on what is good or bad and leading the discussion entirely. In-groups are not always right (in fact, often wrong), and they create some weird sensation of a faux hierarchy which you need to climb to be respected, when you are actually just meeting fairly arbitrary restrictions. I believe it is best to instead always be critical, and give in-depth explanations of decisions. This way, there is less arbitrary and more precise. Precise is easy to follow, and precise is not easy to bull. This post is definitely not aimed at Chris. He's usually the one giving the in-depth explanations himself :p. It's rather just a preemptive strike against anything ugly happening in the section. Hopefully most agree. Though. I do value the fact there should be a place to release very polished scripts, ready-to-roll scripts. I don't think a forum is a good place for that. Something like a package system with voting might be appropriate. Maybe this is something Graal can get in the near future. |
Quote:
I don't see any reason the same level of help can't be given outside of the Code Gallery. Perhaps less-established scripters could post a script they plan on releasing, get critique, make changes, and then post the polished version in the gallery. I agree with you, though—I don't mean to make it seem like new scripters shouldn't be allowed to post code in here, or that you have to be a member of some in-group, I'm just trying to keep the code gallery clean of flawed scripts so others trying to learn aren't confused by them. Sorry if it came out wrong. |
All times are GMT +2. The time now is 07:27 PM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, vBulletin Solutions Inc.
Copyright (C) 1998-2019 Toonslab All Rights Reserved.