New Eggy RPG Bug

[Cam]

Hi,

I encountered a new bug with playing Eggy RPG over on my forum:



It is generating server errors:

• XF\Db\Exception: MySQL statement prepare error [1054]: Unknown column 'reward_claimed' in 'field list'
• src/XF/Db/AbstractStatement.php:225
• Generated by: Cam
• Sep 18, 2026 at 1:28 PM

Stack trace​

INSERT INTO xf_eggy_rpg_event_participation(event_id,user_id,progress_value,kills,contribution_score,reward_claimed,last_update_date) VALUES(?,?,1,1,1,0,?) ON DUPLICATE KEY UPDATE progress_value=progress_value+1,kills=kills+1,contribution_score=contribution_score+1,last_update_date=VALUES(last_update_date)
------------

#0 src/XF/Db/Mysqli/Statement.php(207): XF\Db\AbstractStatement->getException('MySQL statement...', 1054, '42S22')
#1 src/XF/Db/Mysqli/Statement.php(43): XF\Db\Mysqli\Statement->getException('MySQL statement...', 1054, '42S22')
#2 src/XF/Db/Mysqli/Statement.php(61): XF\Db\Mysqli\Statement->prepare()
#3 src/XF/Db/AbstractAdapter.php(96): XF\Db\Mysqli\Statement->execute()
#4 src/addons/Eggy/Rpg/Repository/Production.php(1168): XF\Db\AbstractAdapter->query('INSERT INTO xf_...', Array)
#5 src/addons/Eggy/Rpg/Repository/RpgRepository.php(3044): Eggy\Rpg\Repository\Production->recordCombatVictory(468, 13, 146, 418)
#6 src/addons/Eggy/Rpg/Repository/RpgRepository.php(2905): Eggy\Rpg\Repository\RpgRepository->completeVictory(Array, Array, 55, 37)
#7 src/addons/Eggy/Rpg/Pub/Controller/RpgController.php(483): Eggy\Rpg\Repository\RpgRepository->performCombatAction(468, 'skill', 9)
#8 src/XF/Mvc/Dispatcher.php(364): Eggy\Rpg\Pub\Controller\RpgController->actionCombat(Object(XF\Mvc\ParameterBag))
#9 src/XF/Mvc/Dispatcher.php(266): XF\Mvc\Dispatcher->dispatchClass('Eggy\\Rpg:Rpg', 'Combat', Object(XF\Mvc\RouteMatch), Object(Eggy\RpgGuestMode\Eggy\Rpg\Pub\Controller\RpgController), NULL)
#10 src/XF/Mvc/Dispatcher.php(121): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(Eggy\RpgGuestMode\Eggy\Rpg\Pub\Controller\RpgController), NULL)
#11 src/XF/Mvc/Dispatcher.php(63): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#12 src/XF/App.php(2840): XF\Mvc\Dispatcher->run()
#13 src/XF.php(850): XF\App->run()
#14 index.php(23): XF::runApp('XF\\Pub\\App')
#15 {main}

Request state​

array(4) {
["url"] => string(13) "/wober/combat"
["referrer"] => string(27) "https://offtopix.com/wober/"
["_GET"] => array(0) {
}
["_POST"] => array(3) {
["_xfToken"] => string(8) "********"
["expected_round"] => string(1) "9"
["combat_action"] => string(5) "skill"
}
}

 

[Cam]

I'm getting the error in game when trying to finish beating this Ancient Treant, which I believe would be the first time beating it. Running 1.7.4 Commercial Release on XF 2.3.13.

 

[Eggy]

I'm getting the error in game when trying to finish beating this Ancient Treant, which I believe would be the first time beating it. Running 1.7.4 Commercial Release on XF 2.3.13.

Hello there and sorry for the delayed reply. I'll investigate this soon and provide a resolution to this issue by tomorrow at the latest. Thank you very much for the detailed description of the error!

 

[Eggy]

Thanks for reporting this. There were only a few minor fixes needed and 1.7.5 is now available to download.

The error was being caused by an older database table on upgraded installations not having the reward_claimed field that the current RPG code expects when recording event participation after combat. That is why it was throwing the MySQL error when you were finishing the Ancient Treant fight.

1.7.5 now checks and repairs that database field automatically during the upgrade, so there should be no need to make any manual database changes.

Please download and install 1.7.5 and then retry the fight. If the upgrade process gives you any trouble, please temporarily disable the third party add on you mentioned before upgrading, then re enable it afterwards.

 

[Eggy]

Just a quick follow up while I’m looking at the RPG side of things.

I also noticed the image generation prompt where you asked it to improve an existing logo from a URL.

The current setup I'm using is Cloudflare’s free AI API. With that provider, generation is text to image. It does not actively fetch an image from a URL, inspect it and then improve or edit that image. If you include an image URL in the prompt, the model only receives that URL as part of the text, so it cannot actually see the logo you’re referring to.

That is why a prompt such as “improve this logo” followed by a URL can produce a completely different interpretation rather than an improved version of the original image.

The free Cloudflare API is simply the API Eggy currently uses to demonstrate that the generator is functioning. It should not be taken as a reflection of the best image quality or generation capability AI Image Gallery can produce.

AI Image Gallery supports several other provider options, including OpenAI, AUTOMATIC1111/Forge, ComfyUI and custom OpenAI-compatible endpoints. You can configure your own API key or endpoint and use more capable models where available. Depending on the provider and model, these can offer much better image quality, stronger prompt understanding and more advanced generation capabilities than the free Cloudflare setup.

With the current Cloudflare configuration, prompts should describe the image you want created rather than asking it to fetch and modify an existing image from a link. For more advanced or higher-quality generation, one of the other supported providers would be the better option.