I've looked at that demo plenty of times.
The problem from the beginning was the Overlay, and all this equip system change means nothing except for trimming it down.
Now if anyone has anything useful to the Overlay problem which I do not have (code), step forward NOW!
I've found the cause - the Suffix was it all along. But now I got no ideas if anything is equiped, without trying it out, and if I (ever) wanted cursed weapons I won't tell if its my pure, equiped one or not. Seems silly though.
How can I add the Suffix without bugging the Overlay unequip? | |
The thing is, suffix has NOTHING to do with overlay. src.suffix="Equipped" , src.suffix="". It has NOTHING to do with it.
| |
It is. I couldn't unequip the overlay if that was in.
Now just by taking those 2 lines out, it works like a charm. It weren't my homemade code, HA! | |
RedlineM203 wrote:
I've looked at that demo plenty of times. And yet, apparently learned nothing from it. You said you learn by seeing code, so learn from that. Wizkidd0123 showed you the right way to write an equipment system. The problem from the beginning was the Overlay, and all this equip system change means nothing except for trimming it down. No, it also means fixing the vast problems in the current system, so you'll avoid running into bugs and you can approach this overlay issue from a fresh perspective: correct code. Now if anyone has anything useful to the Overlay problem which I do not have (code), step forward NOW! O seeker of dreams, you'll find no useful answers till you stop ignoring them. Lummox JR | |
Has this problem been fixed yet? If not, try this.
usr.overlays += image(src.icon, icon_state=src.icon_state) // to add Simple as that. | |
Pyro_dragons wrote:
Has this problem been fixed yet? If not, try this. usr.overlays += image(src.icon, icon_state=src.icon_state) // to add Simple as that. Well no, not really, since there are other factors to the overlay (such as layer), and since all that is moot as long as the equipment system itself is half-broken. Profferring a tiny snippet of code isn't going to help here. You've treated the symptoms, not the disease. Lummox JR | |
This has been fixed. But seriously, the Suffix was the exact root of the problem... but now the overlay sticks as (M.. thinge...errr..) someone said, their "Update" don't work either so I'm using a fix overlay code. Like what I suggested for there to be in CC.
(CC = Chao Chatterz) | |
RedlineM203 wrote:
This has been fixed. But seriously, the Suffix was the exact root of the problem... but now the overlay sticks as (M.. thinge...errr..) someone said, their "Update" don't work either so I'm using a fix overlay code. Like what I suggested for there to be in CC. The suffix was only related to this particular problem. The larger problem that you're using a bad equipment system is not resolved. It's better that you fix that now than later, when it can bite you in the butt. Lummox JR | |
RedlineM203 wrote:
Thanks a lot. You turned my game into a dump. I'm taking no more advice from you... Now look, rewriting your code to use correct procedure should in no way destroy it. If your game fell apart in the process, you did something very wrong. Rewriting that equipment system at this stage of development (or any stage, really) should be a very simple fix and doesn't need a lot of work beyond easy stuff. If you're having problems, you made a mistake, but that's easy enough to address if you'd just post where the trouble is. Lummox JR | |
Its not because it don't fit in, its because I'm getting major problems...
And no, don't offer me advice. I mean that. | |
That's a stupid thing to say, especially to the person who probably has the most knowledge with DM. Lummox Jr is the most helpful person I know with this. You shouldn't ignore him just because you can't fix one problem. BTW, he's right, that is a really crappy equipment system.
| |
RedlineM203 wrote:
Its not because it don't fit in, its because I'm getting major problems... Like I said, you could only be having major problems if you did something wrong. Best to confront those problems now and avoid worse ones in the future. Right now your biggest problem seems to be that you want to copy code verbatim rather than 1) figure out why it works or doesn't work, 2) determine whether the author knows what they're doing, or 3) pay attention to anything that is not a block of spoon-fed code. And no, don't offer me advice. I mean that. If you don't want advice, stop posting under Code Problems. This is where people post who need help with their code, and just because the advice you get doesn't immediately solve the problem you came to ask about, doesn't mean you should just totally ignore it. Fix the obvious problems first, and then you have a shot at debugging the less obvious problems such as the one you came to ask about. Lummox JR | |
RedlineM203 wrote:
Some admin lock this topic... it takes a god damn page and I get useless crap. You've been given loads of good advice you refuse to actually use. How do you expect to fix your problems if you won't fix your problems? The one you brought up in this thread is secondary, at best, to the bigger problem that your system is poised to fall apart on a moment's notice. If you didn't want this thread to balloon as it has, all you had to do was learn something from it. Alas you seem uninterested in that. As I said, if you have no desire to receive real help, then don't ask for it here. What you seem to want is a quick-fix infusion of code to stitch up something that's fundamentally flawed. Well, there are no quick fixes, and even though you think this problem is solved, it's not; this code is going to come back to haunt you later. Carping that somebody tried to do more than spoon-feed you a bogus patch isn't going to make that go away. Lummox JR | |
Exactly. People aren't just going to give you code. they will give you advice or examples on how to fix it, and it's your decision on whether or not you want to listen. All you're doing is asking for someone to give you the code, which very few, if anyon,e will actually do.
And, as Lummox said, that code is very likey to fail faster than you can say wtf. There are easier and faster ways to make an equipment code, so try to figure one out. Just to give an example, I've made one that handles 9 different types of equipment, and its smaller than what you've got there. It's not that hard once you get it. Just listen to what over people say and you'll get it soon enough. Don't say that the info people give you is useless, because 99% it's not. | |
See, here's your problem. You're copying from bogus demos. Either learn from good ones, or take what good advice has been given you and build your own from that.
I've told you twice now to go check out Wizkidd0123's demo, which does not suck. He actually knows what he's doing.
Lummox JR