Page 2 of 7

Re: 22 May Updates - karambwans, potion delay & bugfixes

Posted: Tue May 22, 2018 5:09 pm
by Mike
Respire1337 wrote: Yeah, that's true, took me a while to figure it out. Btw, you can't a karambwan-brew combo, your brew won't be consumed.
You should be able to brew-karambwan though. The order in which you eat/pot matters. As stated in my first post, after eating a karambwan, you need to wait 1.8s before potting or eating. But if you first eat food (or drink a potion), then you should be able to instantly eat a karambwan after. Did you try that?

Re: 22 May Updates - karambwans, potion delay & bugfixes

Posted: Tue May 22, 2018 5:22 pm
by Respire1337
Mike wrote:
Respire1337 wrote: Yeah, that's true, took me a while to figure it out. Btw, you can't a karambwan-brew combo, your brew won't be consumed.
You should be able to brew-karambwan though. The order in which you eat/pot matters. As stated in my first post, after eating a karambwan, you need to wait 1.8s before potting or eating. But if you first eat food (or drink a potion), then you should be able to instantly eat a karambwan after. Did you try that?
Yeah, it's working the way it should(brew-karambwan). I got it wrong there, sorry.

Re: 22 May Updates - karambwans, potion delay & bugfixes

Posted: Tue May 22, 2018 5:36 pm
by Nike007
::map is amazing!! Great update!


Karambwanji fishing is a little slow imo though. Let us catch 1-5 randomly at a time, or buff to be more like osrs. Don't see much of a reason for us to have a significantly worse catch rate.

Re: 22 May Updates - karambwans, potion delay & bugfixes

Posted: Tue May 22, 2018 6:43 pm
by Iron adam
Great stuff. Karambwans should be fun. Map is beautiful.
Almost as beautiful as this guy:
Spoiler: show
Image

Re: 22 May Updates - karambwans, potion delay & bugfixes

Posted: Tue May 22, 2018 6:55 pm
by Andres
I hope you didnt had that map for private access for a longer time.
Could have saved me some work in the past :(

Good updates!
Love the new fish :-)

Re: 22 May Updates - karambwans, potion delay & bugfixes

Posted: Tue May 22, 2018 7:03 pm
by B0rnt0bepeek
Adamthalion wrote:Great stuff. Karambwans should be fun. Map is beautiful.
Almost as beautiful as this guy:
Spoiler: show
Image
If only now, we could make our characters blacker than night.
:#:

Re: 22 May Updates - karambwans, potion delay & bugfixes

Posted: Tue May 22, 2018 9:20 pm
by Isaac
Great updates Mike thankyou. I like the Karambwanji fishing rate as it is, makes it a viable option for skillers cos karambwans won't be everywhere all at once.

Re: 22 May Updates - karambwans, potion delay & bugfixes

Posted: Wed May 23, 2018 12:58 am
by Thearlygamer
Why can't ironmen buy karambwanji from the shops :( Also the fishing spot is south-east of tai bwo wanni village not south-west

Re: 22 May Updates - karambwans, potion delay & bugfixes

Posted: Wed May 23, 2018 2:43 am
by Keiler05
Was this Brew/potion timer increase Polled? Once again another favorite thing of mine about the server gets ruined. It was perfect the way it was and it made pk honor "Unique" in that aspect. I just love PVMING with the brews mechanic... Now it being slower I've come near death at Vene a lot of times...

Any chance of this thing getting polled to be reverted?

Thank you.

Edit: Saw it was polled about adding the karambwans and increasing the potion delay... While I can agree that's a "cool" mechanic for the pkers, it has ruined now one of my favorite and unique aspects about this server for me. Since I'm not a pker then it really doesn't benefit me.

#NerfHonor strikes again. Time for another break.

Re: 22 May Updates - karambwans, potion delay & bugfixes

Posted: Wed May 23, 2018 2:53 am
by Iron adam
Keiler05 wrote:Was this Brew/potion timer increase Polled?
viewtopic.php?f=93&t=72349
Keiler05 wrote:Once again another favorite thing of mine about the server gets ruined. It was perfect the way it was and it made pk honor "Unique" in that aspect. I just love PVMING with the brews mechanic... Now it being slower I've come near death at Vene a lot of times...
It was a bug, not a feature.